JAMin

Jan,

Op zondag 27 juli 2003 19:38, schreef Jan Depner:
> Do we want to hardwire the defaults in the code or provide them as part
> of the distro - default.jam (this includes six scenes after Steve mods
> the save/load XML stuff)?  This could be modified by the user but if
> they screw it up they can always download it again.

To followup on my last message, make a /etc/jamin directory, put there the 
default system wide stuff in.

Then create a dir $HOME/.jamin and put there initial copies in from the /etc 
directory and work from there. If a user screws one of the files, it can 
simply be deleted.

This may also be a good place to store and load saved sessions by default, so 
when the file selection browser is activated, it starts from there.

Just another 2 cts.

-- 

	Greetings, Michiel Broek

mbroek@...  or  Fidonet 2:280/2802 to Michiel Broek.

m=E5ndagen den 28 juli 2003 19.23 skrev Michiel Broek:
> Jan,
>
> Op zondag 27 juli 2003 19:38, schreef Jan Depner:
> > Do we want to hardwire the defaults in the code or provide them as part
> > of the distro - default.jam (this includes six scenes after Steve mods
> > the save/load XML stuff)?  This could be modified by the user but if
> > they screw it up they can always download it again.
>
> To followup on my last message, make a /etc/jamin directory, put there the
> default system wide stuff in.

Hi,

I'm no expert, but I don't think it's standard-procedure to put global=20
application configurations under /etc.

Instead they should be put under /<systemspecificpath>/share/jamin. Where I=
=20
think you already are putting files ?

/Robert

>
> Then create a dir $HOME/.jamin and put there initial copies in from the
> /etc directory and work from there. If a user screws one of the files, it
> can simply be deleted.
>
> This may also be a good place to store and load saved sessions by default,
> so when the file selection browser is activated, it starts from there.
>
> Just another 2 cts.