FLTK logo

Re: [fltk.coredev] Exploration: FLTK platform compatible with both Wayland and X11

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.coredev  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: Exploration: FLTK platform compatible with both Wayland and X11 Albrecht Schlosser Mar 22, 2022  
 
On 3/22/22 12:48 'melcher....@googlemail.com' via fltk.coredev wrote:
As for Fluid, I can offer to change Fluid, so it compiles as a pure command line app as well as a GUI app. It already avoids calling any graphics calls, but if it helps the cause, I would implement a pure .fl to .cpp translator.

Sorry, no, that's not the point. There's no reason to do that.

All FLTK GUI apps should behave like Gtk apps do today: if the Wayland compositor is available they should use it, otherwise they fall back to using old X11. On Wayland systems the latter is enabled by running the X server XWayland under Wayland.

Since *users* have the choice to use X11-only login sessions (e.g. on Debian: "Gnome/Xorg") or use a login session with Wayland and X server (KDE/plasma or Gnome/Wayland) the applications should be able do decide what to use on the fly for better desktop integration (for instance using the desktop specific window decorations).

If we didn't supply a "hybrid" FLTK library the (Linux) distributor would have to build the X11-only FLTK lib and all dependent applications would have to use it and thus all FLTK applications would be X11 only. This would also concern users that build their own applications with the distro's FLTK package.

Alternatively the Linux distro could build two different FLTK libraries for apps that support Wayland or those that don't but that qould likey be a maintenance nightmare for the disto managers and I'm afraid they wouldn't want to do that.

The fact that I mentioned fluid was only an example. Building another command-line fluid executable would not help for the interactive (GUI) fluid, would it?

And there are, of course (!), other FLTK applications in the Linux distro and their GUI executables would need such hybrid support.

Examples on a Debian-like Linux distro:

aconnectgui
Depends: libasound2 (>= 1.0.16), libc6 (>= 2.4), libfltk1.1 (>= 1.1.6-6), libgcc-s1 (>= 3.0), libstdc++6 (>= 5)

alsa-tools-gui
Depends: libasound2 (>= 1.0.24.1), libc6 (>= 2.29), libfltk1.1 (>= 1.1.6), libglib2.0-0 (>= 2.35.9), libgtk-3-0 (>= 3.0.0), libgtk2.0-0 (>= 2.8.0), libstdc++6 (>= 5.2)

alsamixergui
Depends: libasound2 (>= 1.0.16), libc6 (>= 2.14), libfltk1.1 (>= 1.1.6-6), libgcc-s1 (>= 3.0), libstdc++6 (>= 5), alsa-utils

ax25-xtools
Depends: libc6 (>= 2.14), libfltk1.3 (>= 1.3.1), libgcc-s1 (>= 3.0), libstdc++6 (>= 5), libx11-6

... (stopped list at letter 'b')

Not to mention packages fltk1.1-games and fltk1.3-games, and pinentry-fltk. ;-)


Side note: as you can see, Debian still supports FLTK 1.1 and 1.3.

--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/478ef7f4-2644-9e13-9612-9d7c3deb85dc%40online.de.
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.