Re: Visualisation applications and Octave.

[Teemu Ikonen]

On 08/06/04 23:13, Ole Jacob Hagen wrote:
> We are still using oset, oget, oplot, oline, osurf,oimage,opatch and so 
> on, but we would really want to use set, get, plot, line, surf, patch 
> instead.
> This would mean that m-files to the application, which we cannot mention 
> here can also be used within Octave.
> So, John...Is it possible to remove the builtin set-command?

Hi,

A few months ago I posted a patch to the maintainers list which allows for
removing all the gnuplot-related code from core Octave, while the interface
remains at least 90% compatible. I promised John to work on the patch a
little more (I had some strange bugs with gnuplot 4.0), but haven't had the
time and interest lately.

See http://www.octave.org/mailing-lists/octave-maintainers/2004/197 for the
posting.

I might have time to hack on it some more in two to three weeks, but can't
make any promises. Of course, you're free to improve it yourself, if you are
desperate. I have to warn you though, the whole patch is a big kludge. :)

Another approach which you could use in the short term is to just rename
the builtin functions in the symbol table. An example on how to do this can
be found on the Grace plotting code in octave-forge
(extra/graceplot/__grcmd__.cc, function __grinit__).

Good to see that someone's working on the octave graphics,

Teemu