Re: GtkApplication and argc/arv
- From: Tristan Van Berkom <tvb gnome org>
- To: "jose aliste gmail com" <jose aliste gmail com>
- Cc: gtk-devel-list gnome org, Murray Cumming <murrayc murrayc com>
- Subject: Re: GtkApplication and argc/arv
- Date: Fri, 25 Feb 2011 08:52:21 +0900
On Fri, Feb 25, 2011 at 8:25 AM, jose aliste gmail com
<jose aliste gmail com> wrote:
> On Tue, Feb 22, 2011 at 6:45 AM, Murray Cumming <murrayc murrayc com> wrote:
>> On Mon, 2011-02-21 at 21:57 +0100, Murray Cumming wrote:
>>> I'm trying to wrap GtkApplication for gtkmm but I can't really do that
>>> until I understand how it's meant to be used.
>>> In general, I find the documentation lacks overview and advice, partly
>>> because it's spread between GApplication and GtkApplication and mentions
>>> some concepts without explaining them first. So I have some questions.
>>> Are we still meant to call gtk_init(&argc, &argv) when using
>>> GtkApplication, which takes argc/argv again via g_application_run(). Or
>>> is gtk_init() then superfluous?
>>> Mathias mentioned that gtk_init(NULL, NULL) is best anyway, though I
>>> don't understand why:
>>> How should we use GOptionContext to parse command line arguments from
>>> argc/argv when using GtkApplication. Is this the ideal way, using the
>>> command-line signal?
>>> It seems a little long-winded.
>> And more simply:
>> 3. Will we recommend that all GTK+ applications generally use
>> 4. Do we believe that all (GTK+) applications should be single-instance
> Just to point out an example, Evince does not use GtkApplication and
> it's not single instanced (there is one process per each document you
> see) and I don't think there are plans to make it single instanced.
however as I mentioned it would not hurt evince if it was a single
instance, we would save on memory and gain in startup time for every
document that evince is invoked for, without harming evince in any way.
Furthermore using GtkApplication everywhere "opens up the door" for
more sophisticated integration that could hypothetically happen
in the future.
- it would allow for system watchdogs to be implemented without any explicit
cooperation on the part of the application for one,
- it could serve to provide some basic system messaging for the
desktop and applications, like updating the input method for all
running applications, or even changing the desktop locale and
retranslating messages (albeit runtime translation switching would
of course require more api, but GtkLabel for instance could be
given a translatable format and retranslate itself automatically whenever
the desktop language changes...).
I'm not saying that everybody should hurry up and do extra work they dont
need to... however I do think having a unified GtkApplication api with as many
apps using it as possible seems to be a step in the right direction (whether
its the GNOME Shell that communicates with the GtkApplication, or
MyCustomHandPhoneShell that uses it... having a well defined/unified
api for this stuff seems like a good thing to have).
] [Thread Prev