Wayland

[andrewd207]

I revived the Wayland backend locally and with some help from claude it looks amazing. On wayland there is not always a window decorator and that makes the app/toolkit responsible for providing that. That's where I got stuck last time. There are extensions for wayland where those are provided. KDE provides that but Gnome/mutter doesn't.

Anyway now if on gnome it looks up what the theme is and draws a frame that looks and acts native. It also can just draw whatever it wants. there's a macos window frame built in with the three colored buttons.

Apart from that everything seems to "just work." Windows, menu's dialogs etc. It all looks the same. The one quirk I noticed but haven't looked into yet is mouse scrolling goes way to fast but I'm sure it's a quick fix.

I re-used my older bindings that link to libwayland client, but also in the meantime I've written a pure pascal versions that works directly to the Wayland file handle. It implements the wayland protocol from scratch. The one downside of that is that libwayland provides a nice way to load mouse theme's so that would also need to be re-written. Maybe I'll look at that today. The fpgui backend is still using the libwayland-client library - to be clear.

The performance is great too at least equal to x11.

Screencast.from.2026-06-18.09-58-45.mp4

The window border and the find dialog border is completely drawn with fpgui.

I'd love if it could be included in fpgui again. But also I think it would be great if at runtime it could choose x11 or wayland as the backend. That requires a proxy layer I imagine because currently TfpwWindow(not form) has TfpgX11Window as the ancestor class and you can't just switch an ancestor.

One wayland downside. For security reasons(?) wayland does not allow a client to set it's x/y position. You can position windows you own relative to each other.

[graemeg]

Amazing work Andrew!

No reflection on your code: Wayland itself, is so weird. I honestly don't think it's an improvement over X11. They have dropped so many x11 features. From what I understand (not much) it looks like only per-desktop dpi [correction - per monitor dpi] was good.

As for the TfpgWindow problem. There is a design pattern that might solve the problem. I'll have to hit my Gang-of-Four book to find it.

[fredvs]

@andrewd207 : WOW.

But like Graeme, even though IBM-Red Hat mandates it, I'm not a fan of Wayland.

Furthermore, the restriction on form positioning is a minor inconvenience: it's impossible to share the clipboard with other applications (a security issue!), there's no Wine, no remote desktop, no Inkscape… and XLibre already offers Wayland's advanced features (Xnamespace, HDR resolution, etc.).

But congratulations on being able to adapt it for fpGUI (and I would be very grateful if I could get some help to potentially do the same for MSEgui).

From what I understand (not much) it looks like only per-desktop dpi was good.

XLibre does it (by a modif in xrandr)

For security reasons(?) wayland does not allow a client to set it's x/y position.

What is surprising is that Wayland includes XWayland, the X11 application converter which allows the positioning of forms on a Wayland session.

[andrewd207]

@fredvs I'm working on getting the wayland specific code in a state ok to share :) hopefully today. And it will need some examples.

[fredvs]

Great, do you have plan to update https://github.com/graemeg/fpGUI/tree/wayland ?

[graemeg]

😆 Oh wow, I totally forgot that branch was even there. Well done Andrew for bringing it back to life.

[andrewd207]

I'm in the process of converting it to use my pure pascal Wayland protocol implementation. So after that I'll update it locally. Something pretty cool is it's possible to use dma instead of shm and that speeds up every render path. Currently shm renders are each invisibly turned into a texture and transferred to the gpu memory.

[andrewd207]

😆 Oh wow, I totally forgot that branch was even there. Well done Andrew for bringing it back to life.

I had a moment where I thought it was gone forever 🤣 because I knew I had written it but I didn't know where it went. I found it on my github also in a different branch. Locally I had wiped my checkout and re-cloned your repo after you made the structural changes.

[andrewd207]

That's the goal. At a minimum I can put it on my github until it's possible for graeme to merge it if he want's.

[andrewd207]

@fredvs I just pushed my pascal only version https://github.com/andrewd207/wayland-pascal next I need to convert my local fpgui to use that and then I'll push it to my github.

[andrewd207]

And https://github.com/andrewd207/fpGUI/tree/wayland

You have to pasbuild install the wayland-pascal project above. Then from this fpgui root dir run pasbuild wayland-units it copies the installed ppu's into framework/target/units.

Then pasbuild compile -p wayland

If you run pasbuild clean you will have to run the plugin again.

[fredvs]

Hello Andrew, I did try to follow your instructions to compile fpGUI for Wayland but I fail.

First I installed fpc 3.3.1 on my system.
Then in /wayland-pascal-main

$ pasbuild install

It seems ok but few errors (i suppose not important, it is about the demos):

... No errors till here:
[INFO] Building wayland-demo [13/13]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] No resources directory found (src/main/resources), skipping
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Found 1 source file(s)
[INFO] Build successful (see target/pasbuild-status/compile/compiler.log for details)
[INFO] Executing goal: install
[INFO] Installing to local repository...
[ERROR] No compiled units (.ppu) found in: target/units
[ERROR] Goal failed: install
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE [  0.190 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] wayland-client ............. SKIPPED
[INFO] wayland-rt ................. SUCCESS [  0.320 s]
[INFO] wayland-stable ............. SUCCESS [  0.289 s]
[INFO] wayland-unstable ........... SUCCESS [  0.382 s]
[INFO] wayland-staging ............ SUCCESS [  0.371 s]
[INFO] wayland-classes ............ SUCCESS [  0.301 s]
[INFO] wayland-server ............. SKIPPED
[INFO] wayland-server-rt .......... SUCCESS [  0.295 s]
[INFO] wayland-server-stable ...... SUCCESS [  0.267 s]
[INFO] wayland-server-unstable .... SUCCESS [  0.383 s]
[INFO] wayland-server-staging ..... SUCCESS [  0.411 s]
[INFO] wayland-server-classes ..... SUCCESS [  0.207 s]
[INFO] wayland-demo ............... FAILURE [  0.190 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3.417 s
[INFO] ------------------------------------------------------------------------
[ERROR] Goal failed: reactor-install

Then in /fpGUI-wayland/plugins/, seems ok:

$ bash ./pasbuild-wayland-units

[wayland-units] wayland-rt 0.1.0  <-  /home/fred/.pasbuild/repository/wayland-rt/0.1.0/x86_64-linux-3.3.1/units
[wayland-units] wayland-stable 0.1.0  <-  /home/fred/.pasbuild/repository/wayland-stable/0.1.0/x86_64-linux-3.3.1/units
[wayland-units] wayland-unstable 0.1.0  <-  /home/fred/.pasbuild/repository/wayland-unstable/0.1.0/x86_64-linux-3.3.1/units
[wayland-units] wayland-staging 0.1.0  <-  /home/fred/.pasbuild/repository/wayland-staging/0.1.0/x86_64-linux-3.3.1/units
[wayland-units] wayland-classes 0.1.0  <-  /home/fred/.pasbuild/repository/wayland-classes/0.1.0/x86_64-linux-3.3.1/units
[wayland-units] copied 148 unit files into /home/fred/Downloads/fpGUI-wayland/plugins/framework/target/units

And finally in /fpGUI-wayland/

$ pasbuild compile -p wayland

But I get this, what did I miss?

[INFO] PasBuild 1.9.0 — Born 2026-06-15. Raised by Graeme Geldenhuys.
[INFO] Compiler: FPC (fpc)
[INFO] Executing goal: reactor-compile
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] fpgui-svg2hvif
[INFO] fpgui-framework
[INFO] fpgui-ide
[INFO] fpgui-docview
[INFO] fpgui-uidesigner
[INFO] fpgui-vertex
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building fpgui-svg2hvif [1/6]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] No resources directory found (src/main/resources), skipping
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Found 2 source file(s)
[WARNING] Profile not found: wayland
[INFO] Build successful (see target/pasbuild-status/compile/compiler.log for details)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS [  0.110 s]
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building fpgui-framework [2/6]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] Processing resources from src/main/resources...
[INFO]   Filtering enabled
[INFO] Resources processed successfully
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Generating bootstrap program for library...
[INFO] Discovered 256 units
[INFO] Bootstrap program generated: target/bootstrap_program.pas
[INFO] Found 280 source file(s)
[INFO] Found 63 include file(s)
[INFO] Activating profile: wayland
[ERROR] fpg_impl.pas(32,3) Fatal: Can't find unit wayland used by fpg_impl
[ERROR] Fatal: Compilation aborted
[ERROR] Error: /usr/bin/ppcx64 returned an error exitcode
[ERROR] Build failed with exit code: 1 (see target/pasbuild-status/compile/compiler.log for details)
[ERROR] Goal failed: compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE [  0.098 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] fpgui-svg2hvif ..... SUCCESS [  0.110 s]
[INFO] fpgui-framework .... FAILURE [  0.098 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.208 s
[INFO] ------------------------------------------------------------------------
[ERROR] Goal failed: reactor-compile

[andrewd207]

@fredvs Sorry no I hadn't seen this. You might have to do pasbuild compile first. it says there are no units.

[andrewd207]

Also, you need to use the --compiler option for both wayland and fpgui. otherwise it may be trying to find a 3.2.2 wayland which doesn't exist.

[fredvs]

@andrewd207 Thanks for helping.

You might have to do pasbuild compile first. it says there are no units.

From which directory?

Also, you need to use the --compiler option for both wayland and fpgui. otherwise it may be trying to find a 3.2.2 wayland

Hum but I have already installed fpc 3.3.1 on my system, doing fpc load fpc 3.3.1, so no need --compiler (from what I understand...).

[andrewd207]

If fpc says it's 3.3.1 then you should be fine.
pasbuild compile in the wayland dir. Then pasbuild install. I think install will normally do a compile if it needs it. But work checking.
I doubt it makes a difference but use pasbuild wayland-units don't run the script directly. It's a pasbuild plugin. After it runs do
ls ./framework/target/units | grep wayland to make sure it's copied the wayland units there. If there's a specific file missing (fpc error about unfound unit) look in ~/.pasbuild/repository/wayland* for the .o and .ppu files and copy them there(framework/target/units/) . And let me know what it was so I can update the plugin. I did some reorganization but it shouldn't have changed anything.

[andrewd207]

@graemeg I made x11 or wayland runtime loadable. X11 is always available and if you use -p wayland it adds it as the default. Falls back to x11 if there's no wayland.

https://github.com/andrewd207/fpGUI/tree/runtime-backend if you're interested :D it should apply directly to develop.

[graemeg]

Thank you Andrew. I'll have a look later today.

[fredvs]

@graemeg : You dont need to install a VM with Wayland.
You can try "pure" Wayland apps on a X11 machine, just install the libs and run the app via the terminal of Weston.

First install the libraries:
sudo apt install libwayland-dev wayland-protocols

and then Weston:
sudo apt install weston

Start Weston from your X11 terminal. It will open as an ordinary desktop window:
weston --width=1280 --height=720 &

From the terminal of Weston, load + run the app.

You may also compile the"pure" Waland app on X11 after install the Wayland libraries.

[fredvs]

And https://github.com/andrewd207/fpGUI/tree/wayland

You have to pasbuild install the wayland-pascal project above.

@andrewd207 : I try to pasbuild install but get errors:

$ pasbuild install[INFO] PasBuild 1.9.0 — Born 2026-06-15. Raised by Graeme Geldenhuys.
[INFO] Compiler: FPC (fpc)
[INFO] Executing goal: reactor-install
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO] 
[INFO] wayland-client
[INFO] wayland-rt
[INFO] wayland-stable
[INFO] wayland-unstable
[INFO] wayland-staging
[INFO] wayland-classes
[INFO] wayland-server
[INFO] wayland-server-rt
[INFO] wayland-server-stable
[INFO] wayland-server-unstable
[INFO] wayland-server-staging
[INFO] wayland-server-classes
[INFO] wayland-demo
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building wayland-client [1/13]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping aggregator module: wayland-client
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building wayland-rt [2/13]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] No resources directory found (src/main/resources), skipping
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Generating bootstrap program for library...
[INFO] Discovered 3 units
[INFO] Bootstrap program generated: target/bootstrap_program.pas
[INFO] Found 3 source file(s)
[ERROR] wayland_internal_interfaces.pas(46,106) Error: Identifier not found "INFINITE"
[ERROR] wayland_internal_interfaces.pas(46,114) Error: Illegal expression
[ERROR] wayland_internal_interfaces.pas(61,1) Fatal: There were 2 errors compiling module, stopping
[ERROR] Fatal: Compilation aborted
[ERROR] Error: /usr/bin/ppcx64 returned an error exitcode
[ERROR] Build failed with exit code: 1 (see target/pasbuild-status/compile/compiler.log for details)
[ERROR] Goal failed: compile
[ERROR] Dependency failed: compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE [  0.070 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] wayland-client .... SKIPPED
[INFO] wayland-rt ........ FAILURE [  0.070 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.070 s
[INFO] ------------------------------------------------------------------------
[ERROR] Goal failed: reactor-install
 

I did change INFINITE by 9999999 only for testing but then there are other errors:

[ERROR] wayland_core.pas(36,44) Error: Identifier not found "TCustomAttribute"
[ERROR] wayland_core.pas(36,44) Error: class type expected, but got "<erroneous type>"
[ERROR] wayland_core.pas(251,1) Fatal: There were 2 errors compiling module, stopping
[ERROR] Fatal: Compilation aborted
[ERROR] Error: /usr/bin/ppcx64 returned an error exitcode
[ERROR] Build failed with exit code: 1 (see target/pasbuild-status/compile/compiler.log for details)

[andrewd207]

@fredvs I'll have a look. I suspect you are using fpc 3.2.2 and I developed this with 3.3.1.

Edit: yes, I just checked. This can't compile with fpc 3.2.2, you'll have to use 3.3.1.

[andrewd207]

I used version information as attributes on the objects so it's not something that could be quickly changed to allow fpc3.2.2 to compile it

[fredvs]

Ha yes i use fpc 3.2.2 ... Is it possible to assign a other fpc compiler than the one installed on the system with the pasbuild command?

[andrewd207]

I just did some expirimenting and pasbuild doesn't like pasbuild install --compiler /path/to/ppcx64 it seems to want fpc

So on my system deleted the /usr/bin/ppcx64 file and made a symlink in /usr/local/bin to /usr/local/lib/fpc/3.3.1/ppcx64 then fpc.

Fair warning do this at your own risk :D and ofc everything you try to compile will use 3.3.1 by default which can cause you other problems.

A better solution might be playing with your PATH variable to make sure it finds a 3.3.1 compiler first. That's probably safer.

[fredvs]

Also with official fpc you will need to update /etc/fpc.cfg
Or maybe, if you have energy, adapt your code for fpc 3.2.2/3.2.4 ... ?

[andrewd207]

Also with official fpc you will need to update /etc/fpc.cfg Or maybe, if you have energy, adapt your code for fpc 3.2.2/3.2.4 ... ?

I'm my fpc.cfg file I have many lines like this

-Fl/usr/lib/x86_64-linux-gnu/fpc/$fpcversion/lib/$FPCTARGET

So that I can use any version that is installed. As long as the units are installed following that template.

[graemeg]

I just did some expirimenting and pasbuild doesn't like pasbuild install --compiler /path/to/ppcx64 it seems to want fpc

I looked everywhere. pasbuild honours the compiler passed in, and uses it correctly everywhere. It works fine here, so my only conclusion is that your fpc.cfg file might not be configured to support multiple fpc versions. As in hard-coded unit path with the fpc version in the path. Mine is configured to support various fpc versions, but that requires a strict directory layout.

[rchastain2]

For me, when I want to use a specific version of FPC not installed, I create a Bash script named fpcXXX in ~/.local/bin which looks like this:

/path/to/fpc -n @/path/to/fpc.cfg $*

The -n option tells the compiler to ignore any other fpc.cfg that it can find.

After that I think it should be possible to do pasbuild install --compiler fpcXXX (not tested).

[andrewd207]

Nah, sorry :) If it was a tiny change I'd do it but it changes the design.

I was thinking you could make an executable bash script called fpc. it can just pass all it's options to ppcx64 3.3.1. Assuming it's on your system. pasbuild seems to really want "fpc" to be the name of the compiler you pass it.

[fredvs]

OK, it was only in case of ;) .

[graemeg]

I'll fix Pasbuild today, as the --compiler is supposed to work.

Disclaimer: I've really only tested that argument for using Blaise compiler. Guess I still have a 'fpc' hardcoded somewhere.

[andrewd207]

@graemeg Yes this worked for me today! So I'm not sure what happened before. It definitely said something about not finding fpc before. I was using pasbuild from jun 15 and updated it now.

Anyway @fredvs it seems pasbuild should work if you give it a direct path to a 3.3.1 compiler. fpgui will need the same compiler.

[fredvs]

@andrewd207 Ha ok (but I already installed fpc 3.3.1 ;) ) did you see #193 (reply in thread)?

[fredvs]

@andrewd207 Thanks for helping.

You might have to do pasbuild compile first. it says there are no units.

Ok from /wayland-pascal-main i did:

$ pasbuild compile

Seems perfect:

Building wayland-demo [13/13]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] No resources directory found (src/main/resources), skipping
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Found 1 source file(s)
[INFO] Build successful (see target/pasbuild-status/compile/compiler.log for details)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS [  0.162 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] wayland-client ............. SKIPPED
[INFO] wayland-rt ................. SUCCESS [  0.165 s]
[INFO] wayland-stable ............. SUCCESS [  0.178 s]
[INFO] wayland-unstable ........... SUCCESS [  0.182 s]
[INFO] wayland-staging ............ SUCCESS [  0.192 s]
[INFO] wayland-classes ............ SUCCESS [  0.172 s]
[INFO] wayland-server ............. SKIPPED
[INFO] wayland-server-rt .......... SUCCESS [  0.148 s]
[INFO] wayland-server-stable ...... SUCCESS [  0.145 s]
[INFO] wayland-server-unstable .... SUCCESS [  0.172 s]
[INFO] wayland-server-staging ..... SUCCESS [  0.193 s]
[INFO] wayland-server-classes ..... SUCCESS [  0.169 s]
[INFO] wayland-demo ............... SUCCESS [  0.162 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.878 s

Then

$ pasbuild install

And here some errors:

[INFO] Building wayland-demo [13/13]
[INFO] ------------------------------------------------------------------------
[INFO] Executing goal: process-resources
[INFO] No resources directory found (src/main/resources), skipping
[INFO] Executing goal: compile
[INFO] Compiling project...
[INFO] Found 1 source file(s)
[INFO] Build successful (see target/pasbuild-status/compile/compiler.log for details)
[INFO] Executing goal: install
[INFO] Installing to local repository...
[ERROR] No compiled units (.ppu) found in: target/units
[ERROR] Goal failed: install
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE [  0.201 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] wayland-client ............. SKIPPED
[INFO] wayland-rt ................. SUCCESS [  0.215 s]
[INFO] wayland-stable ............. SUCCESS [  0.217 s]
[INFO] wayland-unstable ........... SUCCESS [  0.241 s]
[INFO] wayland-staging ............ SUCCESS [  0.240 s]
[INFO] wayland-classes ............ SUCCESS [  0.228 s]
[INFO] wayland-server ............. SKIPPED
[INFO] wayland-server-rt .......... SUCCESS [  0.205 s]
[INFO] wayland-server-stable ...... SUCCESS [  0.224 s]
[INFO] wayland-server-unstable .... SUCCESS [  0.229 s]
[INFO] wayland-server-staging ..... SUCCESS [  0.254 s]
[INFO] wayland-server-classes ..... SUCCESS [  0.198 s]
[INFO] wayland-demo ............... FAILURE [  0.201 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.454 s
[INFO] ------------------------------------------------------------------------
[ERROR] Goal failed: reactor-install

And fpGUI fail to build from /fpGUI-wayland:

$ pasbuild compile -p wayland

[INFO] Activating profile: wayland
[ERROR] fpg_impl.pas(32,3) Fatal: Can't find unit wayland used by fpg_impl
[ERROR] Fatal: Compilation aborted
[ERROR] Error: /usr/bin/ppcx64 returned an error exitcode
[ERROR] Build failed with exit code: 1 (see target/pasbuild-status/compile/compiler.log for details)
[ERROR] Goal failed: compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE [  0.104 s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] fpgui-svg2hvif ..... SUCCESS [  0.116 s]
[INFO] fpgui-framework .... FAILURE [  0.104 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.221 s
[INFO] ------------------------------------------------------------------------
[ERROR] Goal failed: reactor-compile

[andrewd207]

setup-wayland-pascal.sh

I made you a crazy script that does all the steps for you. I'm deleting this later so I don't have to maintain it

[andrewd207]

[fredvs]

OK I did run your script from terminal of my X11 machine: out-of-the-box.
But lot of [WARNING] Profile not found: wayland

Then run maximus from Weston installed on X11.

Woooow!

Then I try to run the same binary from X11:

Woooow x1000!

@andrewd207 You're truly impressive. I already knew you were a genius, but you're even more so.

I know how difficult it is to work with Wayland. I tried, but I lacked the skills and the courage to persevere.

And you successfully completed the entire fpGUI migration, even creating a hybrid X11-Wayland binary.

I'm speechless.

Congratulations, you're truly the best.

PS: Dont delete your script too fast, I am sure other people will love it.

[andrewd207]

I'm not a genius but thanks for saying :) I tried to write documentation for the wayland components I made. I did write most of that but for sure claude filled in the gaps in the last weeks. https://github.com/andrewd207/wayland-pascal/blob/main/docs/wayland-classes/index.md

I'm glad that worked for you :)

[fredvs]

I'm not a genius

Indeed, you are even more so.

I was already impressed by the help you provided to my UOS project in facilitating access to web audio streams, your noise reduction tool, and so many other remarkable code elements for fpGUI.
You and Graeme make a wonderful team.

[andrewd207]

@graemeg I guess it wouldn't be a problem for fpgui to depend on the wayland packages. But the problem I encountered was that any other project I make with pasbuild also needs to depend on the wayland packages if I use pasbuild. Shouldn't pasbuild automatically pull in sub dependancies without needing to add them directly to a project? This is why I made the plugin to "cheat" and just copy the ppu files into fpgui/framework.