To ensure cross-platform each toolkit has its own low-level API for drawing widgets. In search of another bike I wanted to write a Toolkit, but after I came to the conclusion that the low-level API for primitives will be the same as those of wayland. And I thought: what if the layer responsible for the platform, slipping a little lower? Wayland Protocol will be ported to all platforms (including microsoft windows) that greatly facilitate the writing of new cross-platform Toolkit. The only problem when porting wayland, in my opinion, will be the file descriptor when you create wl_pool. However, applications must have their own abstractions for shared memory. If wayland will be a single API on all operating systems, you'll be sure to native composers, which will render the primitives wayland applications. What do you think about this?
This is out of scope for us. There is a huge, huge, huge, huge, huge amount of code that you need to write in order to have reasonably good native apps, and the window system is just a very small part of that.
(In reply to Daniel Stone from comment #1) > This is out of scope for us. There is a huge, huge, huge, huge, huge amount > of code that you need to write in order to have reasonably good native apps, > and the window system is just a very small part of that. The main pledge for the future. Is it possible to port the wayland library on Microsoft Windows without break API?
I mean the wayland-client.
Not in any meaningful way, no. Even if you could, the code you would save from reusing Wayland is absolutely trivial, compared to the code you need to write to run under Windows anyway. It's absolutely huge.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.