[Meego-architecture] MCE or MCE-like component in 1.3, Re: [meego-packaging] why does meegotouch-compositor rely on mce?

[fathi.boudra at nokia.com]

wrt to m-compositor, it relies on mce (not optional atm) and is used in power saving feature,
for example not displaying updates on the screen when the display is dimmed or screen lock is on.

Fathi
________________________________________
From: carsten.munk at gmail.com [carsten.munk at gmail.com] on behalf of ext Carsten Munk [carsten at maemo.org]
Sent: Monday, March 21, 2011 10:53 AM
To: Arjan van de Ven
Cc: Boudra Fathi (Nokia-MS/Helsinki); meego-architecture at meego.com
Subject: Re: MCE or MCE-like component in 1.3, Re: [meego-packaging] why does meegotouch-compositor rely on mce?

2011/3/18 Arjan van de Ven <arjan at linux.intel.com>:
> On 3/17/2011 11:17 PM, Carsten Munk wrote:
>>
>> Hi,
>>
>> Just forking this discussion into an architecture discussion on mce's
>> role in 1.3 or if we need to design a new component for this that is
>> more architecture independent. And less of a kitchen sink.
>
> I would actually like to say that even for 1.2 we need something else
> (more to come on more of the details settle).
>
> you'll see us remove MCE and a few similarly "oddly designed" components
> from the core OS soon (the package will still be in OBS/etc just no longer
> in the mandatory set, and not used by various images)

Do you have a list of those for good measure? Just to keep the N900
image in loop which may still have use for some of those (we have
pretty good QA rates right now and it'd be a shame to loose them when
the package group changes come in)

>> Now, how do you architects see these functions handled in 1.3?
>
> for 1.2 (never mind 1.3) the session parts are going to be handled in the
> meego-ui-daemon process, which will run inside the session
> (similar to the role that gnome-settings-daemon has in a gnome UI stack).
>
> for the remaining items we'll need to find a good home.... if the use case
> of these components is still relevant, and not some legacy Nokia requirement
> that isn't actually valid anymore.

To prepare a bit, can you tell a bit about how meego-ui-daemon is
structured/what roles it fullfills?

BR
Carsten Munk