Changes

Jump to navigation Jump to search
376 bytes removed ,  19:20, 14 April 2013
→‎Octave to do list: update todo list
Line 67: Line 67:       −
== Octave to do list ==
+
= 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 <nowiki>~~~~</nowiki>
 
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 <nowiki>~~~~</nowiki>
   −
=== wiki to do list ===
+
== wiki to do list ===
   −
=== octave code to write ===
+
== octave code to write ===
 
* make unimplemented check for packages as well
 
* make unimplemented check for packages as well
* implement {{Codeline:@inputParser/StructExpand}} property on general package
+
* rewrite inputParser using classdef
* implement strel object for image package
+
** implement {{Codeline:@inputParser/StructExpand}} property on general package
* implement nlinfit as wrapper to leasqr once inputParser is finished
+
* implement nlinfit as wrapper to leasqr (using inputParser)
 
* make test and demo deal with tests and demos in .cc packages
 
* 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?</pre>
 
: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?</pre>
Line 82: Line 82:  
* port omero toolbox
 
* port omero toolbox
 
* use post_install to move oct into private directory?
 
* use post_install to move oct into private directory?
 +
 
* import to octave from octave-forge
 
* import to octave from octave-forge
** condeig (linear-algebra)
  −
** ellipj (specfun)
  −
** ellipke (specfun)
   
** exifread <-- readexif (image) but should probably be implemented in C++ using [http://www.graphicsmagick.org/Magick++/Image.html GraphicsMagick]. Actually maybe we shouldn't even bother. Matlab is deprecating it in favour of imfinfo.
 
** exifread <-- readexif (image) but should probably be implemented in C++ using [http://www.graphicsmagick.org/Magick++/Image.html GraphicsMagick]. Actually maybe we shouldn't even bother. Matlab is deprecating it in favour of imfinfo.
** expint (specfun)
  −
** funm (linear-algebra)
  −
** gsvd (linear-algebra)
  −
** inputdlg (java)
  −
** listdlg (java)
  −
** publish (miscellaneous)
  −
** resample (signal)
     −
=== octave-forge to do ===
+
== octave-forge to do ===
 
* finish iptcheckinput
 
* finish iptcheckinput
 
* get an octave-forge logo (falar com o Duarte)
 
* get an octave-forge logo (falar com o Duarte)
* finish zenity package once inputParser is finished
+
* finish zenity package
 
** for scale see https://savannah.gnu.org/bugs/?33330
 
** for scale see https://savannah.gnu.org/bugs/?33330
 
* get hough transform function in image package compatible
 
* get hough transform function in image package compatible
Line 107: Line 98:  
** Getopt::Long
 
** Getopt::Long
 
* port ReadImageJROI
 
* port ReadImageJROI
* make better normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html Jordi metioned this paper]] and
+
* make compatible normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html Jordi metioned this paper]] and
* fix warnings on C++ code of xml functions moved to IO package
   
* fix on optim package
 
* fix on optim package
 
** move test scripts into function test blocks
 
** move test scripts into function test blocks
 
** move example scripts into demo blocks
 
** move example scripts into demo blocks
* turn __bwdist into bwdist (image package)
     −
=== other octave related todo ===
+
== other octave related todo ===
 
* update gtksourceview octave lang file
 
* update gtksourceview octave lang file
 
* make gtksourceview highlight octave help text as texinfo
 
* make gtksourceview highlight octave help text as texinfo
 
* make gtksourceview highlight test and demo as octave and not comment
 
* make gtksourceview highlight test and demo as octave and not comment

Navigation menu