Recent Features
| |||||||||||||
You betray your ignorance of waylandYou betray your ignorance of waylandPosted May 28, 2012 15:59 UTC (Mon) by butlerm (subscriber, #13312)In reply to: You betray your ignorance of wayland by raven667 Parent article: Announcing printerd
>The existing robust X backends aren't just going to evaporate, the toolkits are already multi-platform and Wayland is just an additional backend.
My question here is basically can the toolkit switch dynamically so that the same application binary be run in both X mode or Wayland mode, depending on the runtime environment?
If so, that would be outstanding, if not that could put a major impediment in the deployment of such applications until some form of remote operation is working. I can't see a server distribution standardizing on applications that can't be accessed remotely.
(Log in to post comments)
You betray your ignorance of wayland Posted May 28, 2012 16:19 UTC (Mon) by raven667 (subscriber, #5198) [Link]
I thought the way this was being implemented in the toolkits was to check for environment variables to know which output to use.
You betray your ignorance of wayland Posted May 28, 2012 17:40 UTC (Mon) by Jonno (subscriber, #49613) [Link]
I don't know about GTK+, but Qt 4.8 and 5.0 autodetects backend at runtime, which can be overridden by a command line argument to the application (i.e. if you have both Wayland and X11 running).
NB: For Qt 4.8 you need to explicitly configure Qt with -qpa to get the new modular backends, the default is X11 only. In Qt 5.0 the hard-coded X11 port will be gone and replaced with a modular xcb backend.
You betray your ignorance of wayland Posted May 29, 2012 7:51 UTC (Tue) by butlerm (subscriber, #13312) [Link]
Thanks, that is excellent news. Perhaps a little more work than running everything through a generalized version of the XCB API, but accomplishing the same thing nonetheless, and probably more flexible too.
You betray your ignorance of wayland Posted May 29, 2012 21:53 UTC (Tue) by nix (subscriber, #2304) [Link]
Yeah. If Gtk does that too, most objections to Wayland basically fall away: nobody's likely to implement Wayland-only programs (just as people don't write against raw Xlib these days), and if the toolkits can switch based on an env var or something, the user can choose with whatever granularity is desired between insane blazing performance and remotability (which means I can turn remotability on and forget about Wayland completely).
You betray your ignorance of wayland Posted May 30, 2012 5:47 UTC (Wed) by aquasync (subscriber, #26654) [Link]
I would expect so, using the GDK_BACKEND environment variable (see the gtk broadway demos).
|
|||||||||||||