Em Thursday, 30 de June de 2011, às 14:08:37, Tiago Vignatti escreveu: > 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? :)
It doesn't. I was going to ask steven what reasons he had for using the qt
compositor. It's just a sample compositor, showing what is possible to do if
you integrate the wayland libraries into a QML-based application. I've seen
other experiments doing the same, some of which would definitely never qualify
for a product.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
