Re: using a push parser to connect Octave to a GUI

[Jacob Dawid]

Although we have put a lot of work into making octave work with a pty/Windows console, I think what JWE proposes is the more sustainable solution. I always thought of this, but I thought it was never considered an option. The best thing to have is a simple API in octave for a GUI, similar to the API that we use to ask for variables, history and such:

void (cli_ready*)();

void (receive_line*)(const char* line); 

void send_line(const char* line);

This would speed up development drastically.

Am 29. Januar 2012 13:18 schrieb Michael Goffioul <address@hidden>:

On Sun, Jan 29, 2012 at 3:28 AM, John W. Eaton <address@hidden> wrote:
> I see this approach as a possibility for solving the GUI problem
> without requiring a terminal widget that can connect to Octave with a
> pty interface, which seems to be a difficulty for Windows systems.

This problem is more or less solved with the QConsole widget I
implemented. It's not as elegant as a real UNIX-like PTY, but it's
working and seems to be the only reasonable solution for an embedded
terminal under Windows. Now, nothing prevents from trying alternate
solutions, but keep in mind the getting rid of the PTY will have
impact on other components that expect a terminal to work properly:
for instance the "ls" command in octave (when run in a PTY, "ls"
executable uses the terminal full width for formatting), or the
"less"-based pager.

Michael.

--
„Alle sagten: Das geht nicht. Da kam einer, der wusste das nicht und hat's gemacht.“ - Unbekannt