On 06/30/2011 12:43 PM, steven wrote:
how about qt-compositor?
Because we don't need that much.
In principle, we are happy with a single compositor that contains only a
very thin layer for MeeGo. Besides, pushing the effort of building a
compositor Qt-independent would ease the adoption for other toolkits.
For instance, why the whole code inside
qt-compositor/hardware_integration has to be inside a *qt* module?
In other words: why it always has to be Qt centric? :)
Tiago
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
