Re: Release plans for the GUI

[Júlio Hoffimann]

Hi all,

I would like to share my modest opinion on Octave GUI development. It's amazing to have an official GUI, we hope this way Octave can reach more people, particularly undergraduate courses.

What i think:

1) 90% Octave users are Linux users. (please correct me if i'm wrong)

2) Canonical made easy for every student to have a GNU/Linux operating system installed and working in dual boot.

3) Octave works on Windows, a GUI is not strictly necessary.

1+2+3 => To implement a feature in a way is not good just to reach other platforms is not a good paradigm, if there aren't experienced Windows developers working in Octave, we can't waste time by making this to work ourselves. It's so much easy for a end-user to install Ubuntu in dual boot and download Octave GUI from repositories than make it to work well on Windows.

If people is caring about a GUI, they can install Linux. If not, they just still running their scripts on the console. Seems radical, maybe it is, it's just my pragmatic(superficial) vision on the project.

Regards,

Júlio.

P.S.: Jacob is nice to see you again. :-)

2011/9/9 Jacob Dawid <address@hidden>

If you go back and look at my original sources for the octave server in the OctaveDe project (which Jacob improved a lot, but also cut out a big chunk of functionality), there was functionality for requesting individuals variables and their contents and manipulating/interacting with debugging information.
http://octavede.svn.sourceforge.net/viewvc/octavede/branches/OctaveDE_QT/src/server.cpp?revision=91&view=markup

I'm sure this can be added back into the newest incarnation of the class that communicated with Octave quite easily, I just don't think anyone has done it yet.

John Swensen

This is possible and will definately happen.

I don't agree with what Michael says, but I am not disputing over personal preferences. If he is able to offer a working terminal solution on both Windows and Linux in whatever way he does it, I am with him, though I have spent lots of time going a different direction. For now I have halted development on the terminal integration to await his answer.

--
Software Development == Church Development
Step 1. Build it.
Step 2. Pray.

Whitespace - the most ink saving programming language: http://compsoc.dur.ac.uk/whitespace/index.php .