Apologies for first getting back to this e-mail now..
2012/4/29 Alison Chaiken <[email protected]>:
> I'm question impressed by Carsten's diagram. His productivity and
> energy are an example to us all!
>
> Two comments:
>
> 1. Power is not mentioned anywhere in the diagrams. Assuredly upower
> and its integration with D-Bus is as important to capture as that of
> pulsedaudio and connman?
Power management/energy management is a bit hard to group from
entirely Core point of view, since it's theoretically on the hardware
adaptation side - a STB needs very different kinds of power management
than for example a mobile handset. The important thing is however to
provide similar interfaces for querying hardware state and perhaps
signalling poweroff/suspend/etc. So this would be represented with
D-Bus interfaces / adaptation interfaces over time.
>
> 2. As I understand it, Qt5 will be architected significantly different
> that Qt4, and the blank part of the outline appears to reflect Qt4.
> I don't know what the plan for Qt migration within Mer is, but that
> plan should will be a subject of curiosity in its own right, so the
> documentation perhaps should reflect that.
I'm trying to figure out how to exactly relay that in practice in
documentation, as Mer can be put together in many different ways - I
think chances are we'll do some 'typical stack documentation' for a
couple of tested configurations (Mer+Qt5+DirectFB, Mer+Qt4+X11, etc).
That's one of the reasons why we have this kind of non-full view
architecture documentation - as to make people able to picture by
themselves how to piece together the architectural blocks..
>
> Best wishes,
> Alison
>
> --
> Alison Chaiken
> (650) 279-5600 (cell) {she-devel.com,
> exerciseforthereader.org}
> "A compass is better than a map." -- Joichi Ito, Where 2.0 2012
>
>
