From octave-maintainers-request at bevo dot che dot wisc dot edu Mon Nov 10 22:34:51 2003
Subject: Re: Octave GUI  (was: Shared memory interface to Octave)
From: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
To: Octave Maintainer <octave-maintainers at bevo dot che dot wisc dot edu>
Date: Mon, 10 Nov 2003 22:34:43 -0600


Why all this discussion about shared memory or pipes or named pipes or
sockets?

Why not build something that can be linked directly with Octave?

Preferably, something that would allow most of the GUI to be written
directly in Octave's own scripting language, instead of in C/C++/etc.

If done right, I think it would be possible to swap one GUI toolkit
for another internally without having to rewrite all the code that
makes up the GUI (since much of that would be done in Octave's
scripting language).

Yes, this might mean that it will be necessary to make Octave thread
safe, but that would be useful anyway.

jwe