[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GUI integration
From: |
John W. Eaton |
Subject: |
Re: GUI integration |
Date: |
Sat, 11 Aug 2012 15:49:58 -0400 |
On 11-Aug-2012, Jacob Dawid wrote:
| What files need to be found? Can the locations be specified by
| command-line arguments or environment variables? If not, that should
| probably be allowed anyway.
|
|
| at startup, the GUI checks whether a configuration file exists and - if not -
| copies the default configuration file into the home directory of the user. But
| I think, instead of doing that, I can just define default settings hardcoded
in
| a function and write that to a file, so the need for a default configuration
| file gets eliminated.
I think it would be better to have the defaults in a file. That way
someone could customize the defaults for new users without having to
recompile.
| PS: What about the GUI flag for octave, so octave can determine whether a GUI
| is available or not? It should not be a big deal to add the code to launch the
| texinfo browser in the GUI, we just need to agree upon a flag name.
How about a "window_system" function that would return "Qt" or "none"?
jwe
- GUI integration, John W. Eaton, 2012/08/10
- GUI integration, John W. Eaton, 2012/08/11
- Re: GUI integration, Jacob Dawid, 2012/08/11
- Re: GUI integration, Michael Goffioul, 2012/08/11
- Re: GUI integration, John W. Eaton, 2012/08/11
- Re: GUI integration, Jacob Dawid, 2012/08/11
- Re: GUI integration,
John W. Eaton <=
- Re: GUI integration, John W. Eaton, 2012/08/11
- Re: GUI integration, Mike Miller, 2012/08/11
- Re: GUI integration, John W. Eaton, 2012/08/11
- Re: GUI integration, Mike Miller, 2012/08/11
- Re: GUI integration, Mike Miller, 2012/08/11
- Re: GUI integration, Jacob Dawid, 2012/08/12
- Re: GUI integration, Mike Miller, 2012/08/12
- Re: GUI integration, John W. Eaton, 2012/08/12
- Re: GUI integration, Mike Miller, 2012/08/12