User:Carandraug

Somehow I got involved with GNU octave even though I don't actually need it for work anymore. I used it for 6 months during my PhD to write the FRAPINATOR.

Octave to do list

You can add stuff to my todo list (I may however move it back to your todo list on your userpage). Don't forget to sign each item with ~~~~

wiki to do list

• octavify the Templates Documentation. Right now, they are only copy paste from Gentoo.
  • [Template:Infobox] (this one I have no idea what it does, it was created by joannac
  • [Template:Key]
  • [Template:Path]
  • [Template:Warning]
• maybe change color of Template:File. Red looks as if it's something important. Maybe blue (a file is more official/important/leader/etc...)? Or Green to be like Template:Code

octave code to write

• add inputParser to miscellaneous package
  • write documentation for inputParser
  • implement @inputParser/AddSwitch
• implement strel object for image package
• implement nlinfit as wrapper to leasqr once inputParser is finished
• write normxcorr
• make test and demo deal with tests and demos in .cc packages

I don't like the first option. It's ugly and further pollutes the user namespace. And even if we have some Makefile that copies the .cc file at pkg install time, users won't know they have to make the call to test and demo differently. I guess demo and test functions would have to be modifed for that. I say just place the demos and tests on the .cc file. Later we can change pkg to copy the .cc file, and then change demo and test to look for those files if the function is .oct file. Tests are mainly used in development so users won't need them. Demos... well in the case of ellipj, it has not been working for a very long time so my guess is that people haven't been using it that much. What do you think?

octave-forge to do

• find copyright holder of gcvsplf.f after death of Herman Woltring
• fix imhist
• fix tiff_tag_reader
• finish iptcheckinput
• new release of specfun
  • fix demos of ellipj.m KaKiLa 11:55, 7 December 2011 (PST)
• get an octave-forge logo (falar com o Duarte)
• finish zenity package once inputParser is finished
• get kmeans from Søren and make it a little compatible with matlab for the stats package
• get hough transform function in image package compatible
• look into [SIP] and [sivp]

other octave related todo

• update gtksourceview octave lang file
• make gtksourceview highlight octave help text as texinfo
• make gtksourceview highlight test and demo as octave and not comment