Le mardi 4 janvier 2022 à 20:12:52 UTC+1, Albrecht Schlosser a écrit :
On 1/4/22 5:07 PM Manolo wrote:
I'd like to invite fellow FLTK developers to vote about
adding a Wayland platform to the FLTK library.
I'm basically +1 on adding Wayland but I'd like to test before I can
make my final vote.
I fully understand some time is necessary before the vote.
I see a conflict with changes I'm currently doing to consolidate
timeout functions. I'm going to check the implications.
*
Some platform-related code is identical for the Wayland and X11
platforms.
Timeout support is in that case.
The new code defines a new class, Fl_Nix_System_Driver, where all
such code is located.
After inclusion of the Wayland branch, the X11-platform code will
also use
class Fl_Nix_System_Driver.
This is an area where your and my changes conflict. I need to
evaluate the changes...
OK. Let me know if I could help by any change within the Wayland code.
BTW, for curiosity: what does Fl_*Nix*_System_Driver mean, is
there something we can use to describe it? Does it have to do with
Unix, Posix, or something like this?
The goal here is to name a class that would be used by the X11 and Wayland platforms
to contain code useful to both. This means, used on Unix and Linux but not on macOS.
'Posix' is already used to name a class shared by the X11 and macOS platforms (+ Wayland, eventually).
The net result is this class hierarchy :
Fl_System_driver
++++ Fl_Posix_System_driver
++++++++ Fl_Nix_System_driver
++++++++++++ Fl_X11_System_driver
++++++++++++ Fl_Wayland_System_driver
++++++++ Fl_Darwin_System_driver
++++ Fl_WinAPI_System_driver
I've proposed Fl_Nix_System_driver following the practivce to name *Nix the Unix+Linux OS collection.
Aternative name suggestions are very welcome.
