Loading Status Feedback

[Jasper Huijsmans]

Erik Harrison schreef:
> On 1/10/06, Andrew Conkling <andrew.conkling at gmail.com> wrote:
>> On 1/10/06, Erik Harrison <erikharrison at gmail.com> wrote:
>>> On 1/10/06, Andrew Conkling <andrew.conkling at gmail.com> wrote:
>>>> Not to hijack this thread, but that reminds me of a question I've had
>>>> for a while: why make this an option for each launcher?  You've mostly
>>>> answered it here, but it begs another: is there any drawback in
>>>> "trying" to support startup notification in an app that doesn't
>>>> support it?  I didn't know about some apps not supporting it, and I've
>>>> put it on every launcher and menu item I've ever created without
>>>> noticeable problem.  I think I'd like to request that on bugzilla,
>>>> since just having the global option seems sufficient, but since we're
>>>> talking about it here....
>>> I mentioned that once. I think the only objection is that the way it
>>> works is the app alerts the window manager when the app is done
>>> "Starting". With this in place, turning it on for all launchers would
>>> cause the alert that the app is starting to run until the window
>>> manager time out. (30 seconds I believe)
>> Ah, this makes more sense.  I have seen that before where the
>> indicator just keeps on spinning (given my choice in cursor) even
>> after the app has started.  Is there any way to check for the presence
>> of startup notification, something like "If we get a signal from this
>> app, we'll show the busy cursor, otherwise not at all"?  (Honestly, I
>> confess I don't know much about how this works, even though I've
>> worked in GTK+ 2.6.)  Of course, I understand that even if it were
>> possible to support something like that, it may just support outdated
>> software, and if that's the case, I'm with you, Olivier!
> 
> I think there is a solution to it now. Assuming a launcher is built
> from a .desktop file (in the case of using the appfinder widget from
> the panel), then the .desktop file declares support for SN or not.
> 
> Beyond that, I don't believe it is possible to check. Basically, the
> protocol doesn't allow the app to startup and say "Yo! Doing the
> startup thing" (thus letting us know it supports SN). The rationale is
> the app is starting up, thus there could be a potentially significant
> delay in the message which tells us startup is beginning. Thus
> delaying the startup alert, killing the whole point.
> 
> Jasper, thoughts?

Many. But not necessarily on this subject ;-)

Hmm, how about turning it on by default? That might be an acceptable 
intermediate solution?

	Jasper