octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Integrating Quint into the Octave sources


From: Ben Abbott
Subject: Re: Integrating Quint into the Octave sources
Date: Tue, 19 Apr 2011 15:08:35 -0400

On Apr 19, 2011, at 1:21 PM, Michael D Godfrey wrote:

> On 04/19/2011 09:59 AM, James Cloos wrote:
>> Wouldn't it be easier to make --gui the option and cli the default?
>> 
>> That avoids incompatible changes.  And most users who might want a gui
>> be default probably start octave via a .desktop file or other menu item;
>> those file can use a --gui option easier than existing scripts can add
>> a --no-gui option.
>> 
>> -JimC
>> 
> I much prefer this solution.  Particularly, if people use Octave on various
> machines it is not so simple to create a new .octaverc in order to avoid
> the unwanted GUI startup.  Currently, many users (in my experience)
> do not have a startup script and they expect the cli startup.  Explaining
> how to avoid the GUI is just overhead.  
> 
> People who do want the GUI will likely also want to tailor it for their
> preferences, so they will need to learn about startup scripts. 
> 
> Michael

It seems more natural to me that Octave would, by default, launch as a command 
line app when run from the command line.

I assume that this would not be a problem as most gui apps are launched from a 
graphical interface (MacOS, Windows, KDE, Gnome, etc).

Ben



reply via email to

[Prev in Thread] Current Thread [Next in Thread]