ubuntu-phone team mailing list archive

[Thomas Voß <thomas.voss@xxxxxxxxxxxxx>]

On Fri, Feb 28, 2014 at 11:19 AM, Alberto Mardegan
<alberto.mardegan@xxxxxxxxxxxxx> wrote:
> On 02/28/2014 11:37 AM, Thomas Voß wrote:
>> On Fri, Feb 28, 2014 at 9:48 AM, Alberto Mardegan
>> <alberto.mardegan@xxxxxxxxxxxxx> wrote:
>>>
>>> I hope to be proved wrong, but I've the feeling that this can be racy:
>>> we need to make sure that the trusted helper manages to start the
>>> trusted session before the participating apps have shown their windows,
>>> or you won't be able to see the correct transitions.
>>
>> Why not? The designs explicitly take into account the case when an app
>> is already running.
>
> I'm thinking of the case where the application is *not* running. In a
> typical session you have:
>
>   App1 -> TrustedHelper -> App2
>
> Initially, only App1 is running. When it invokes the trusted helper, the
> trusted helper will create the trusted session and add itself and App1
> into it, and then start the session. So far, so good.
> The problem comes when App2 needs to be started: App2 needs to be added
> to the trusted session after it's started (if my understanding of the
> API is correct, an application is added by its PID), but before it gets
> a chance to show its window. How can we achieve this?
>

The trick is that we can add by PID (for already running applications)
or by AppId (for not yet running apps).
Unity8 then takes care of starting the application instance to ensure
seamless transitions.

So yes, fully agreed, if we could only add by PID, we would likely
encounter graphical glitches due to the application startup race.

Cheers,

  Thomas

> Ciao,
>   Alberto
>
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp