Re: `program_invocation_name' bug =?=> `gnomelib_init' API change
- From: Felix Bellaby <felix pooh u-net com>
- To: Martin Baulig <martin home-of-linux org>
- Cc: "Felix Bellaby <felix pooh u-net com> Raja R Harinath" <harinath cs umn edu>, gnome-list gnome org
- Subject: Re: `program_invocation_name' bug =?=> `gnomelib_init' API change
- Date: Mon, 23 Nov 1998 04:48:40 +0000 (GMT)
Martin Baulig writes:
> > OK, I'm missing something then :) Why can't we use "app_id" instead of
> > "program_invocation_name"?
>
> I agree. If "program_invocation_name" is not set, I think we can really
> use "app_id" instead - perhaps convert it to lowercase letters first.
I do not like the idea of using different conventions on glibc systems
and non glibc systems.
BTW, why is gnome using so many different ways to refer to the program ?
Preferences are currently saved in files based on:
app->prefix : gnome-app.c
gnome_app_id : gnome-entry.c
program_invocation_name : gnome-client.c
plus whatever prefixes the programmer chooses to push herself.
99% of the time these values are all identical.
I can see that programs with mulitple app windows might need to save
multiple GnomeApp configurations but why not put those configurations
into distinct sections of a single file ?
Why not use gnome_app_id as the default prefix basis for all the
preferences ?
It might help if gnomelib_init were to push this as a config
prefix as well so that it would take a conscious effort to create
multiple config files rather than the reverse.
The program_invocation_name is fine within command line executables
as a way of overloading their meaning (pidof == killall, etc) but
it is pretty crazy way of doing it within a GUI. Why is it playing
any role in gnome at all ?
Felix
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]