Hi Andrew, 

As I know, the panel architecture has some changes from Moblin 2.1 to MeeGo 1.0.
The panels are more modularized from main panel and running as a separated 
process. 


Simply speaking, main panel (codes in mutter-moblin) is a server and the sub 
panels are clients. 
Sub panel needs to register the itself to main panel (the icon, tooltip, 
execute file) and when user clicks panel icon on the main panel, D-Bus will 
launch the corresponding process to show the real contents. 
Specific to Network Panel, considering network may need to be checked and 
connected after boot up. The panel process will be launched by default.


For more details, you can go to http://meego.gitorious.com/meego-netbook-ux and 
check out codes of *mutter-meego* and *meego-panel-networks* for reference. 


Thanks, 
Lei Y
MeeGo Netbook QA team


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Andrew Wafaa
Sent: Friday, July 30, 2010 2:34 AM
To: [email protected]
Subject: Re: [MeeGo-dev] Issues getting Network Panel to display properly with 
NM

On Thu, 2010-07-29 at 10:49 -0700, Arjan van de Ven wrote:


My issue still remains, could someone advise on what has changed from Moblin 
2.1 to MeeGo 1.0 that would render what used to work inoperable?
Is it an API change or is there something else?  There appears to be a major 
attitude change along with the code/version change, almost one of exclusivity 
and not inclusion - shame.

I also appreciate the compliance issue as Rob has already pointed that out to 
me on IRC.  I am not calling my work MeeGo but am giving credit where it is 
due, and I want to work with MeeGo to ensure as wide an audience as possible 
can drink from the cup of yummy shininess.  I most certainly wouldn't want a 
certain distro to get all the netbook glory now ;-)

Regards,

Andy

--
Andrew Wafaa
IRC: FunkyPenguin.
GPG: 0x3A36312F
openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to