|
From: <je...@fo...> - 2023-07-18 17:14:17
|
On 2023-07-18 12:02, Enno Rehling wrote:
> I can't speak for Joeron, but if I were in his shoes, my thinking
> qould go like this:
>
> I wouldn't expect it to mean much for Fox. X11 still works pretty much
> everywhere that Wayland exists, via XWayland, so support for Wayland
> does not broaden the range of machines that a Fox application will run
> on, it only adds complexity and support overhead with another backend.
>
> And no, you can't drop X11 and replace it with Wayland. X11 is still
> the only way to get a Fox application to run on macOS, and nobody
> wants to add native Mac Cocoa support for the same reason: mo'
> backends, mo' problems.
Then there is the thing that, AFAIK, Wayland is not a drawing API
but a compositor. So I'd still need a drawing API.
I am pondering XCB as an alternative to X11. It would fix some issues.
XCB should work as well as X11 since wire-protocol is the same.
XCB has much fewer header files and much less complicated API, plus
it may be incrementally introduced; it could be a bit faster as well.
I'm open to other ideas, but keep in mind that there's a lot to rewrite
if underlying concepts change a lot.
-- JVZ
|