Re: Release plans for the GUI

[Mark Everitt]

I've been avoiding that debate too, but here I go...

This really depends on what the goal is. If the goal is to win over a lot of
users, then we need to address Windows. In fact the tools are so good on
Linux already that, barring my plot rant above, perhaps we should focus
attention exclusively on Windows. Linux users, and to a certain extent Mac
users, are comfortable using a command line and editors that aren't joined
at the hip.

I'm not sure about bundling all this together though. Having Octave as it is
is very nice. It has dependencies, but these aren't too difficult to work
with. Keeping the GUI separate makes it an option, and I think that many
current users will be happy to do without it, at least for a while. For
Windows, this could be thrown together as a single application, in keeping
with the platform.

How about a well documented API and a simple referece GUI that uses it? In
the short term this could be used as the "official" GUI, and in the long
term we may see people code platform specific GUIs of their own accord. I
think this is the Python approach and it's working out well for them!

Mark

--
View this message in context: 
http://octave.1599824.n4.nabble.com/Release-plans-for-the-GUI-tp3790414p3858107.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.