> freeamp -uitheme.ui -uilcdproc.ui blah.mp3
> or this could be written
> freeamp -ui[theme.ui lcdproc.ui] blah.mp3
Hmm.
freeamp --ui=theme,lcdproc blah.mp3
As I know the most POSIX-like is that we hawe "-X"-ish one letter
switches, orr "--WORD"-ish long arguments. Also POSIX sais, that
"-u them
I just noticed that the GNU glibc has a gthread library.
Would it be possible to use this instead of pthread ? It
may be more portable ?
Just an idea.
Steve
--
NetTek Ltd tel +44-(0)20 7483 1169 fax +44-(0)20 7483 2455
Flat 2, 43 Howitt Road, Belsize Park, London NW3 4LU
Epage [EMAIL
On 4 Oct, Gabor Fleischer wrote:
>> freeamp -uitheme.ui -uilcdproc.ui blah.mp3
>> or this could be written
>> freeamp -ui[theme.ui lcdproc.ui] blah.mp3
> Hmm.
> freeamp --ui=theme,lcdproc blah.mp3
>
> As I know the most POSIX-like is that we hawe "-X"-ish one letter
> switches, orr "--WORD"-ish
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
clo
POSIX would be a plus but we still have to make sure that there are no
spaces between args and their parameters so that we can distinguish what
params are ours and what params are a random component.
elrod
[EMAIL PROTECTED] wrote:
> On 4 Oct, Gabor Fleischer wrote:
> >> freeamp -uitheme.ui -ui
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
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 Mes
On Mon, Oct 04, 1999 at 10:57:31AM -0700, Mark B. Elrod wrote:
> 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?
Themes c
heh... ok so if we do that how hard would it be for us to add a theme browser to
the prefs? something that scaled down the bitmap fot the main window and blitted
it?
elrod
Mayhem & Chaos Coordinator wrote:
> Well, if we make it so that the user needs to 'import' a theme then the user
> would ne
Checkout cvs now... I've got it defining HAVE_GTK when it's compiling with
gtk+.. Does that fix stuff for you?
Isaac
On 03-Oct-99 Hiromasa Kato wrote:
> Is there any appropriate preprocessor symbol that I can use to tell
> if I'm compiling for gtk+ theme ui?
Not hard, but given the sheer number of other things that need to get
done -- unlikely. :-(
--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]>
How bout when we decompress it, we store the timestamp of the compressed thingie
in one of our spiffy databases, or just stick an empty file in the
decompressed dir with its name being the timestamp. Then we compare to the
compressed one on startup.. work?
Isaac
On 04-Oct-99 Mark B. Elrod wro
12 matches
Mail list logo