Well, if we make it so that the user needs to 'import' a theme then the user
would need to import the updated theme, before it became active.


--ruaok         Freezerburn! All else is only icing. -- Soul Coughing

Robert Kaye -- [EMAIL PROTECTED]  http://moon.eorbit.net/~robert
----- Original Message -----
From: Mark B. Elrod <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, October 04, 1999 10:57 AM
Subject: Re: where to install theme files to?


> i like option 2 as well. the only downside is that if a user gets an
updated
> theme with the same name we might not recognize it unless they know to
delete
> the folder it has been expanded to. how can we get around that?
>
> elrod
>
> Mayhem & Chaos Coordinator wrote:
>
> > Sounds good to me.
> >
> > I've got a follow up question to that: When and where to theme files get
> > decompressed to? I see two reasonable options here:
> >
> > 1) When FreeAmp starts, it figures out what theme it needs and
decompresses
> > it into /tmp/freeamp-$pid/theme (or X:\windows\temp\theme). When FreeAmp
> > closes the files get cleaned up. Pro: Less wasted disk space Con: Slower
> > startup time
> > 2) When the user selects a new theme the theme is decompressed into
> > ~/.freeamp/theme (or X:\Program Files\FreeAmp\themes\<themename> and it
run
> > from there. The themes are never cleaned from the drive unless the user
> > requests it. Pro: Faster startup Con: Wasted disk space
> >
> > I think I prefer option #2.
> >
> > --ruaok         Freezerburn! All else is only icing. -- Soul Coughing
> >
> > Robert Kaye -- [EMAIL PROTECTED]  http://moon.eorbit.net/~robert
> > ----- Original Message -----
> > From: Isaac Richards <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Saturday, October 02, 1999 7:13 PM
> > Subject: where to install theme files to?
> >
> > > So, I was thinking we need to install our default theme somewhere..
> > Anything
> > > wrong with $prefix/share/freeamp/themes/default?  Any better
alternatives?
> > >
> > > Isaac
> > >
>

Reply via email to