[MeeGo-dev] Wayland effort in 1.3 - planning, discussion, activities, etc
carsten at maemo.org
Fri Jun 17 11:08:34 PDT 2011
2011/6/17 Thiago Macieira <thiago at kde.org>:
> Em Friday, 17 de June de 2011, às 17:31:12, Carsten Munk escreveu:
>> - It's derived from Qt's PVRQWSWSEGL and licensed accordingily
> There's such a thing in Qt with such a horrible name or are you just pulling
> our legs? :-)
Wish I was kidding, but:
> Anyway, we flew Kristian Høgsberg in to the Qt Contributor Summit here in
> Berlin and he's been busy discussing with the other Qt devs and contributors.
> I've seen many Lighthouse and Wayland sessions listed, including one today
> "Input methods in Wayland and Qt 5".
> Notes should be published by the participants soon (probably after they get
> back home).
Will look forward to those notes.
> As for the Qt 5 discussion we had in San Francisco, it was basically focussing
> on getting Wayland running and, the bulk of the discussion, Scene Graph.
> The state of things right now is that Qt 4.8 brings the Lighthouse project
> (the QPA platform), which has a Wayland plugin backend. So getting Wayland to
> run on Qt 4.8 is definitely possible. We know that the plugin API in Qt 4.8 is
> lacking some things -- for example, it's lacking a way to do an
> indicators/system tray integration. Those are being dealt with, but only for
> Qt 5.0.
> However, from the discussions in SF, it became clear that the biggest win can
> be achieved only if we couple Wayland with the Scene Graph and the Qt Quick
> 2.0 stack. That's a technology that was never intended to be released inside
> Qt 4.8 (we only said "same time as 4.8"). It does work right now and the
> preliminary results are very good.
Makes sense, so I'm guessing this is like qtquick2-integration branch
that I've been playing with.
> So we agreed that we need to keep two branches being tested: a Qt 4.8 with
> Scene Graph backport and Qt 5. By late August, we need to make a choice which
> one we'll use for MeeGo 1.3 and productise that. That Qt version will be used
> only for specific programs that have been tested to work with it -- the rest
> should use a standard X11 architecture, reducing the platform risk.
I think some discussion on how best to structure pkgconfig's in that
scenario and such like that would be good. First thing I ran into was
everyone using dependancies for pkgconfig(QtCore) (as an example)
causing choices between qt4 and qt5 :)
Could be good to have both in Trunk.
More information about the MeeGo-dev