[Development] Is Xlib a hard requirement for Qt5 xcb?
thiago.macieira at intel.com
Tue Jul 30 17:37:41 CEST 2013
On terça-feira, 30 de julho de 2013 10:14:33, Oswald Buddenhagen wrote:
> On Tue, Jul 30, 2013 at 12:17:30AM -0700, Thiago Macieira wrote:
> > On terça-feira, 30 de julho de 2013 08:31:55, Friedemann Kleint wrote:
> > > For the system tray, I have been working on
> > > https://codereview.qt-project.org/#change,61046 which would remove
> > > QtWidget's dependency on Xlib.
> > > Very ideally, the system tray would be completely implemented within the
> > > platform plugin, but that is not possible since it needs menus and
> > > tooltip handling.
> > Drop the old protocol and implement only the new D-Bus-based status
> > notifier protocol.
> you are being a tad optimistic here ... qt isn't exactly in a position
> to dictate the platform to the end users of qt-based applications. the
> timeframe for universal adoption of the new system tray protocol is 5-10
> more years.
Right. But we hope that X will be falling into irrelevance by then :-)
> not to mention that i (and probably some others as well)
> think it is inherently broken to detach the systray's protocol layer
> from the windowing system ...
I even agree. But that is not relevant. The protocol exists and we should
support it, however broken it is (because the older protocol is broken in
other and more serious ways).
Anyway, whoever is fixing the systray issue should figure an API for the
platform plugin that works with both the current classes and a future QML- and
QWindow-based implementation. So the plugin shouldn't draw menus and tooltips,
but it should provide information necessary for the lib to implement them.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 190 bytes
Desc: This is a digitally signed message part.
More information about the Development