Carandraug

Joined 17 November 2011
231 bytes removed ,  17 November 2015
→‎octave code to write: update list with things already done
(→‎Bugs: follow one more bug)
(→‎octave code to write: update list with things already done)
Line 32: Line 32:


== octave code to write ==
== octave code to write ==
* make unimplemented check for packages as well
* implement {{Codeline:inputParser.StructExpand}}
* rewrite inputParser using classdef
** implement {{Codeline:@inputParser/StructExpand}} property on general package
* 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>
* replacement for [http://www.mmorph.com/ morphology toolbox]
* replacement for [http://www.mmorph.com/ morphology toolbox]
* port omero toolbox
* port omero toolbox
* use post_install to move oct into private directory?


== octave-forge to do ==
== octave-forge to do ==