[prev in list] [next in list] [prev in thread] [next in thread] 

List:       moblin-dev
Subject:    [Moblin Dev] a way to speed "media app" launch time
From:       bob.spencer () intel ! com (Spencer, Bob)
Date:       2007-11-20 9:52:28
Message-ID: 102A51607473A4449F0D3E2EF6FFCAD602B7827D () orsmsx416 ! amr ! corp ! intel ! com
[Download RAW message or body]

Agree -- the UI should appear as fast as it takes to draw.  Then process
the loading of the content discover in the background.  

As to why dbus takes so long, we should find out the real problem.  A
temporary fix is fine, but don't consider the tast finished until we
find out what is going on.

Bob

Bill Filler wrote:
> Donald,
> I don't know the specifics of the media app code, but think that in
> general it would be a good idea to have the GUI come up immediately,
> then do the dbus connection (and whatever other non-ui related  
> initialization) in a background thread. The GUI actions that rely on
> the dbus connection could be disabled until the connection is
> established. This way, the app should launch very quickly even if it
> might not be entirely functional for a few seconds.   
> 
> Bill
> 
> 
> On Nov 19, 2007, at 4:42 AM, Wei, Donald wrote:
> 
>> I am investigating why "media" take time to launch. And found the
>> dbus connect operation takes about 1/3 of the launch time. It is
>> strange. So I write a sample application just contains the dbus
>> connection operation code. It doesn't cost time. This suggested me
>> that move the dbus connection operation to the beginning of the
>> _init_ function. I have do some basic test, seems it can work.
>> 
>> I still can't explain why it works this way? Please let me know if
>> you have the answer:-) 
>> 
>> 
>> 
>> Please tell me if you have concern to move the code ahead?
>> 
>> 
>> 
>> Thanks,
>> 
>> Donald
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> dev mailing list
>> dev@moblin.org
>> https://www.moblin.org/mailman/listinfo/dev
> 
> _______________________________________________
> dev mailing list
> dev@moblin.org
> https://www.moblin.org/mailman/listinfo/dev

[prev in list] [next in list] [prev in thread] [next in thread]