The experience we have had for the last couple of weeks with using
mcompositor for meego-ux based images is making me rethink my earlier
stance that we should use the same mcompositor package for all user
experiences (where today there is the original MeeGo Touch based handset
UI and then the meego-ux which is being use for tablet and and some
other verticals are experimenting with it.)
The problem lies in the tight integration with the interaction model of
the UX. Examples include window transition effects and the use of
decorators but I'm sure there is more. Over time I'm sure all of these
things could be controlled via runtime configuration options, but I'm
not so sure it's worth the trouble since in my mind mcompositor is just
something to use till we can move to a wayland based solution.
how about we just make this simple and create a new meego-ux'ish
compositor package, and back out all the meego-ux inspired patches to
meegotouch-compositor? I can find a victim to maintain new package, so
not a problem there.
--rusty
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
