Re: Embedding Octave

[Ian Reinhart Geiser]

John W. Eaton said:
> On  7-Oct-2004, Ian Reinhart Geiser <address@hidden> wrote:
>
> | So how would we attack this?  The immediate ones that I can see are
> plot()
> | and input().  I would be willing to create a patch, but I am still
> trying
> | to get my head around the code.  With some direction I could probably do
> | it.
>
> I'm still not sure precisely what you want to be able to do, so I
> can't say for sure where the calls to hook functions should happen, or
> what data should be passed to them.
Basicly this:
http://www.geiseri.com/kdevelop/embedded_input.png

Currently I am just adding my own builtin binding for input() in my
application.  This way if you run it from console, you get stdin/out, but
from my GUI you get the number picker dialog.

I guess my question is what is the better way to go.  It seems that I can
override the built in behavior pretty easy, but like you said, I then have
to remain in sync with octave's features.

This is not a horrible issue with input(...), but it could become annoying
for things like plot(...) and help(...) because I would like to provide
GUI versions of those functions.

Cheers
   -ian reinhart geiser

--