Personally, I don't see the point of LCL-fpGUI. If want to use LCL, use a native widget set like Cocoa, Windows or a well maintained layer like Qt. If want to use fpGUI, just use fpGUI.
It has an advantage if one wants to use the LCL (e.g. due to a legacy application), but does not want to rely on a widgetset like GTK or Qt - if LCL-fpGUI would be properly maintained of course. Then again one could also try to improve the LCL's CustomDrawn widgetset, which is essentially directly on top of for example X11.
However, this branch is suspended: Wayland is simply too closed, primarily because it would require independent development for each compositor.
You don't need independent development for each compositor, you just need to design against the correct interfaces. I've done that for our application at work that runs directly on top of X11 or Wayland and I didn't have many problems except functionality that's missing at all (like window positioning for which a few days ago the xx-zones protocol got merged).
Both LCL-fpGUI and LCL's CustomDrawn widgetsets are without a maintainer [abandoned] or just being slowly maintained/developed [no priority]?
What's the status of LCL-fpGUI widgetset?
Recent
