Hello,

It seems that many GUI toolkits are slowly starting to move to wayland (http://wayland.freedesktop.org/), that moved to v1.0 Is there anyone who currently working on binding for it for FPC ?

Ido

It might be better to ask this on the Lazarus list as Wayland support seems to require more than just the API binding (at least as far as I have understood it).

Regards,
Sven

I'm not sure why, because as far as I know, it replaces the X11 protocol, not gdk, Qt etc...
It also provide compositing window manager based support - that is to create window managers (such as kwin).

But I'll ask there as well :)

ik wrote

I'm not sure why, because as far as I know, it replaces the X11 protocol, not gdk, Qt etc...

That is how I understood it too.

A while back I thought of starting the API bindings for fpGUI's Wayland backend. But I was told that the Wayland API is still in flux. Unlike Qt or GTK, I don't have so much resources to spend on a moving target. So without having to rework bindings that are constantly being broken, I decided to hold off for a while and see when the API stabilizes.

Now that 1.0 is out... does that mean the API will be stable for a while?

Regards,
- Graeme -

In our previous episode, Graeme Geldenhuys said:

Afaik it would also support at least the core parts of X11. It would be declared legacy, and not part of the perpetually supported Wayland set, but I think it is safe to say it will be supported for quite a while.

IOW, I wouldn't desperately try to support Wayland native at this point.

That can be done if the native api turns out to be stable, Wayland truely takes over X11, and all distros package it.

Now it is just asking for pain IMHO.

If you use GTK or Qt you won't of course have any problem, but if you want to create a true Wayland client (like for example a LCL-Customdrawn-Wayland) you need to provide a memory buffer in which you need to render your GUI widgets so only the API alone won't make a GUI application ;)

Regards,
Sven

At least the developers said (with the prerelease versions already) that they won't do incompatible changes anymore (at least not in the v1 series ;) ).

Regards,
Sven

+1
That's exactly how I feel. There has been too many attempts to displace X11 - and they all tanked. Wayland does seems to have more backing than its predecessors though.

Bottom line, existing X11 apps will apparently continue to run on Wayland. So we have time…

Regards,
- Graeme -

Qt5 afaik, does not support X11 anymore, only wayland, and that's the main path most Linux toolkits takes today.
v1.0 suppose to provide stable API afaik, that's what opendesktop looked at the API headers, and it looks very simple +-, but I'm not going to bind it at this time.

afaik, Qt5 DOES support X11.

zeljko

Most of Wayland's developers are also X developers, so it looks quite promising. Qt 5 support for Wayland is pretty complete, afaik, so widgetsets are taking it seriously.

Henry

In our previous episode, Graeme Geldenhuys said:

I think for you with your pure X11 it is less of a problem.

If there are problems, I'd expect them from Wayland based QT/GTK users that need to do a few calls to X11 for some special purposes.

ik wrote

Qt5 afaik, does not support X11 anymore, only wayland, and that's the main path most Linux toolkits takes today.

As far as I know, they are simply moving more to XCB (the replacement libary for XLib). Saying that, all (big five at least) Linux distros already have XCB libraries shipped as standard. So Qt5 should continue to run as normal.

v1.0 suppose to provide stable API afaik, that's what opendesktop to know, thanks.

Regards,
- Graeme -