User:Carandraug: Difference between revisions

From Octave
Jump to navigation Jump to search
(→‎octave-forge to do: remove old todo and add new ones)
Line 33: Line 33:
** Getopt::Long
** Getopt::Long
* port ReadImageJROI
* port ReadImageJROI
* <del>Generalize administration scripts to [http://octave.svn.sf.net/viewvc/octave/trunk/octave-forge/admin/add_copyR_header?view=log add] or [http://octave.svn.sf.net/viewvc/octave/trunk/octave-forge/admin/replace_copyR_header?view=log replace] copyright headers. [[User:KaKiLa|KaKiLa]] 12:35, 21 December 2011 (PST)</del>
* make better normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html Jordi metioned this paper]] and
* make better normxcorr2: [[http://www.idiom.com/~zilla/Papers/nvisionInterface/nip.html Jordi metioned this paper]] and
* new release of miscellaneous package
* new release of miscellaneous package
** <del> must fix map so it no lnger depends on apply first. [[User:KaKiLa|KaKiLa]] 00:55, 9 March 2012 (PST) </del>
** decide what to do with server.cc
*** what excatly is copyright of stringmatch??
* fix warnings on C++ code of xml functions moved to IO package


=== other octave related todo ===
=== other octave related todo ===

Revision as of 10:56, 13 March 2012

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

octave code to write

  • add inputParser to general package
  • implement strel object for image package
  • implement nlinfit as wrapper to leasqr once inputParser is finished
  • 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
  • get an octave-forge logo (falar com o Duarte)
  • finish zenity package once inputParser is finished
  • get hough transform function in image package compatible
  • look into [SIP] and [sivp]
  • from Perl
    • File::Temp
    • check for revision numbers
    • Getopt::Long
  • port ReadImageJROI
  • make better normxcorr2: [Jordi metioned this paper] and
  • new release of miscellaneous package
    • decide what to do with server.cc
      • what excatly is copyright of stringmatch??
  • fix warnings on C++ code of xml functions moved to IO package

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