On Thu, Sep 02, 2004 at 07:27:45AM +0930, Samps wrote:
> A small 'stub' of the settings file, residing next to the executable,
> should contain information about where to find the 'real' settings file,
> thus making it possible to have a global, non-pilferable, central
> server-based standard configuration that adheres to all clients in our
> school network.
> An 'override' possibility (a la 'user.js' in the Mozilla suite) could
> reside in the inidvidual users' profile, enabling them to have
> personalised settings, without screwing it up for the next person to log on.
>
> hope this makes sense
We're _kinda_ doing this already, at least under Linux, using
"/etc/tuxpaint/tuxpaint.conf", which is read first, then followed by
".tuxpaintrc". (Then, any commandline "--" options override any of those.)
This is why we have pairs of config options, like "nograb" which goes with
"grab", and "windowed", which goes with "fullscreen"... to 'unset' the
prior options, if we wish to... ("Tux Paint Config" doesn't really
handle these yet, but it's really going to be a beta release when it first
comes out. Once we get feedback from real-world users, we can start
tweaking it :^) )
PS - the command-line option "--nosysconfig" can override reading the
global config file.
I don't believe there's any global config file in other OSes.
I do like the idea of a stub. Like an "include" option in the user
config file. For example, if there's a lab of computers, and one has
difficulty showing Tux Paint in fullscreen, but the rest work fine, their
local config file can look like this:
include=Z:\Programs\Tux Paint\tuxpaint.cfg
fullscreen=no
Neat idea! :)
-bill!
[EMAIL PROTECTED] Man, some trip this turned out to be.
http://www.newbreedsoftware.com/ All we caught is a tire, a boot,
New Breed Software a tin can and this book of cliches.
_______________________________________________
Tuxpaint-dev mailing list
[EMAIL PROTECTED]
http://tux4kids.net/mailman/listinfo/tuxpaint-dev
