ons, 01 10 2008 kl. 11:41 +0200, skrev David Bateman: > As the last octave-forge release was nominally considered as the last > 3.0.x release, I just imported the control, quaternion and finance > packages that were removed from Octave 3.1. This won't cause an issue > for 3.0.x releases, but once we start making 3.1. specific changes to > octave-forge it will (eg removing imread, etc from octave-forge as they > are in Octave 3.1).
As a follow-up, I've removed imread and imwrite from the image package. I've bumped its requirement to octave 3.1.51 or later. The 'image' package still contains I/O functions for jpeg and png that are using libjpeg and libpng directly. Do we still need these functions? They can still be of use to people that doesn't have GraphicsMagick, so they have some value. But my question is: do they have enough value to justify keeping them? Does anybody actually use these functions? Søren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
