On Thu, Jun 30, 2011 at 5:54 PM, Thiago Macieira <[email protected]> wrote:
> Em Thursday, 30 de June de 2011, às 17:22:48, Ville M. Vainio escreveu: >> If you don't get worse performance with Qt Compositor, is there a good >> reason not to use it (as a starting point again, since it's not a >> "product" in itself)? > > This is a question to be asked to the guys who are doing the compositor. If > they feel more comfortable with another codebase, they can do that. Already got a pretty definitive answer from Kristian ;-). > I'm not sure how much modification of the compositor is expected though. In > any > case, if you really want to modify, you can use the Qt Compositor in your own > product... Part of the power of wayland is the fact that rolling your own compositor is doable. I'm sure some OEM's will want to add something "extra" for their products by altering how compositor works. Having something you plan to hack on as the default starting makes getting started easier, but I don't know how significant the effort is in practice, compared to just swithing to all new composer. It may be a non-issue in the end. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
