User: Password:
|
|
Subscribe / Log in / New account

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 11, 2013 15:45 UTC (Tue) by drago01 (subscriber, #50715)
In reply to: The Wayland Situation: Facts About X vs. Wayland (Phoronix) by butlerm
Parent article: The Wayland Situation: Facts About X vs. Wayland (Phoronix)

GTK does the same. You can select the backend using an ENV var. It only works for apps that do not directly use xlib / xcb calls though.


(Log in to post comments)

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 12, 2013 1:08 UTC (Wed) by butlerm (guest, #13312) [Link]

> It only works for apps that do not directly use xlib / xcb calls though.

Out of curiosity, what deficiencies of GTK/GDK would motivate a developer to do such a thing?

The Wayland Situation: Facts About X vs. Wayland (Phoronix)

Posted Jun 12, 2013 1:49 UTC (Wed) by neilbrown (subscriber, #359) [Link]

It need not be deficiencies that would motivate such behaviour.

Suppose I wanted to write a soft keyboard. Drawing the keyboard responding to events could all be handled by GTK/GDK. But to actually send the keystroke events to the window with the focus, direct xlib/xcb calls would be needed.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds