If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Really, SDL 1 will also be able to run on Wayland? Does that mean that UT2004 will run natively on Wayland, too?

I don't see why not, if it doesn't depend on any X stuff. I just checked the original UT, no X stuff in sight! This could be good news, getting it to run on modern systems is a bit hit and miss at the moment.

Comment

A question if i may ...............
GTK+ has been built with Wayland and X11 support. Wayland has xwayland for say running older GTK X11 apps. So my question is will folk now using GTK+ have to choose between wayland and X when building apps with the GTK+ toolkit ? will an app built today with GTK/wayland still work on distros sticking with X ? How does that part work?

Comment

A question if i may ...............
GTK+ has been built with Wayland and X11 support. Wayland has xwayland for say running older GTK X11 apps. So my question is will folk now using GTK+ have to choose between wayland and X when building apps with the GTK+ toolkit ? will an app built today with GTK/wayland still work on distros sticking with X ? How does that part work?

Afaik the backend can be changed with an env var:

Originally posted by Arch Wiki

When both Wayland and X backends are enabled, GTK+ will default to the X11 backend, but this can be overridden by modifying an environment variable: GDK_BACKEND=wayland

Comment

I don't see why not, if it doesn't depend on any X stuff. I just checked the original UT, no X stuff in sight! This could be good news, getting it to run on modern systems is a bit hit and miss at the moment.

Comment

Quite right. Only the latest toolkits (GTK+3, Qt5, EFL) will be ported to Wayland. Old toolkits, which many programs still depend on (GTK+2, Qt4, and such) will have to run via XWayland. Exception is SDL which will probably gain Wayland support in both SDL and SDL2.

Programs that do not use the Wayland-native toolkits will have to be either ported to another toolkit, or run on XWayland. The difficulties are for programs that use no toolkits at all and speak directly to X11, which have to be rewritten to speak the Wayland protocol instead.

Comment

It does, although it's far less complete than what's being built into Qt5. So while it's possible, people should really port their apps if possible. Luckily, porting to Qt4 from Qt5 is usually just a matter of building against the new version, no major code changes needed. This isn't the case for many GTK 2 programs that are still active development. So people will want to seriously consider porting their apps to newer toolkits, anyway, to get the full benefits of Wayland.

Honestly, GTK 2 apps are the only real sore area I see in this migration, aside from FLTK and other barely-known, barely-used toolkits. Many people stick to using GTK 2 apps just to keep using old themes, not even for any technical reason. Once someone actual ports their desktop over, so people don't need to use Weston to enjoy Wayland, I think people will stop assuming this situation is so difficult to adapt to.

Comment

Honestly, GTK 2 apps are the only real sore area I see in this migration, aside from FLTK and other barely-known, barely-used toolkits. Many people stick to using GTK 2 apps just to keep using old themes, not even for any technical reason. Once someone actual ports their desktop over, so people don't need to use Weston to enjoy Wayland, I think people will stop assuming this situation is so difficult to adapt to.

=O That's actually me lol... I haven't been able to find a correct GTK3 port of the Xfce Dusk theme (it just looks soooo much better in GTK2). That's also the reason I haven't upgraded many of my apps to use GTK3 instead of 2..