Re: GUI integration

[John W. Eaton]

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