[ANN] fpGUI Toolkit v2.0.0 has been released

[Graeme]

The video can present 50% of the solution, from there, I would look for the other 50% on my own that may have been left out.

Until I make videos, maybe these could help. They are all from a few years ago, but still relevent.

Something I showed someone once (this is a very old UIDesigner version):
http://geldenhuys.co.uk/~graemeg/editform.gif

Then on fpGUI's website:

• Community applications (including YouTube videos): https://fpgui.sourceforge.net/community.shtml
• fpGUI dialogs (very few shown): https://fpgui.sourceforge.net/screenshots_widgets.shtml
• Some screenshots of applications included with fpGUI: https://fpgui.sourceforge.net/screenshots_apps.shtml
• Some built-in fpGUI themes: http://geldenhuys.co.uk/~graemeg/themes/start.html

I hope that helps a bit.

[Roland57]

• Community applications (including YouTube videos): https://fpgui.sourceforge.net/community.shtml

By the way, the description of my chess program is outdated, and the link is dead. Please (when you have time) put a link to the Codeberg repository.

[cdbc]

Hi Graeme
Speaking of built-in fpGUI themes:
I'm playing with the 'customstyles' demo app and I'm loving your themes, esp. the tech behind it -- Very intelligent and clever =^ (thumb's up).
Now I've got it running with the 'Carbon' theme, but not a single letter of text in any widget?!? 
I've compiled it with 'aggpas' and it works fine, but no text  ...what am I missing?!?  It has got to be some 'Font'-ThingymaJingy...?
Btw. fetched your PasBuild as well -- Nifty little gadget & works well =^ 
Good on you mate
Regards Benny

[Graeme]

By the way, the description of my chess program is outdated, and the link is dead. Please (when you have time) put a link to the Codeberg repository.

Fixed, thanks.

ps: I accept Merge Requests for the website too. However, that git repo is only published on the SourceForge website (not GitHub).

[Graeme]

I'm playing with the 'customstyles' demo app and I'm loving your themes, esp. the tech behind it

Thanks. I still have so much I want to improve with the theming though. Watch this space. ;-)

I've compiled it with 'aggpas' and it works fine, but no text  ...what am I missing?!?  It has got to be some 'Font'-ThingymaJingy...?

Are you by any chance using Windows? There was a bug with the font engine under Windows, but it's already been fixed and part of the 2.0.1 release (made today). Alternatively, if you cloned the git repo, simply pull the latest 'develop' branch to stay up to date easier.

[cdbc]

Hi Graeme
I cloned your repos, PasBuild too 
Nope  ...NO "Michaelsoft Binbows" here, my main environment are 3 PCLinuxOS' {and 1½ ElementaryOS 8.1 (RC & Release) but they're for sale so they don't count}
Nah, "The dog is buried with me", 'cause I was noob(ish) with 1.5 and now all these new shiny thingies in 2.0.1 -- I guess I spent way too long on GTK & QT 
Well, I'm here now, soooo..... 
Quick question: Why are you /deprecating/ 'SetPosition'?
-- I find it quite handy, when you're writing your form by hand in a jiffy...
Regards Benny

[Graeme]

I cloned your repos, PasBuild too 

I'll investigate, but could you file a bug report, se we can better keep track of it - compared to messages lost in this forum thread.

Quick question: Why are you /deprecating/ 'SetPosition'?
-- I find it quite handy, when you're writing your form by hand in a jiffy...

fpGUI has had a whole new "sizing model" implemented. It's now much closer to how many other popular toolkits work.

Hopefully this (section 9) explains it best: https://github.com/graemeg/fpGUI/blob/develop/docs/toolkit_sizing_comparison.adoc#why-setposition-is-deprecated

[dbannon]

... my main environment are 3 PCLinuxOS'...

Benny, I think your problem might be that your OS is desperately trying to workout if its Apt or RPM based, poor thing  must be so confused.

Davo

(and why implement apt but not dpkg ? Gee !)

[cdbc]

Hi Davo

Benny, I think your problem might be that your OS is desperately trying to workout if its Apt or RPM based, poor thing  must be so confused.

Hehehe...  Those days are long gone mate, we've been doing 'dnf' for the last 6..8 months and that's working brilliantly 
We've even developed our own _inhouse_ 'dnf-mgr' GUI for the Fedora-(I think)-backend, which also works pretty good, albeit a bit memory-hungry 
Ps.: The ElementaryOS is a modern delight  ...for non-techies or people migrating from "Michaelsoft Binbows", but maybe can't afford a Mac  With enough memory, it's a breeze.
Not for me though, as it's based off of 'buntu and running cutting edge GTK & Wayland _only_, with an own well-crafted /skin/ on top, which in turn makes it a "Memory-Hog" 
Regards Benny

[Roland57]

people migrating from "Michaelsoft Binbows"

[off-topic]
I like very much the name of that OS. Thank you. 
[/off-topic]

[PascalDragon]

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).

[Fred vS]

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).

Well, maybe the real reason is a lack of courage and passion. And above all, a lot of disappointment with the lack of features and the political aspect of Wayland.

[valdir.marcos]

The video can present 50% of the solution, from there, I would look for the other 50% on my own that may have been left out.

Until I make videos, maybe these could help. They are all from a few years ago, but still relevent.

Something I showed someone once (this is a very old UIDesigner version):
http://geldenhuys.co.uk/~graemeg/editform.gif

Then on fpGUI's website:

• Community applications (including YouTube videos): https://fpgui.sourceforge.net/community.shtml
• fpGUI dialogs (very few shown): https://fpgui.sourceforge.net/screenshots_widgets.shtml
• Some screenshots of applications included with fpGUI: https://fpgui.sourceforge.net/screenshots_apps.shtml
• Some built-in fpGUI themes: http://geldenhuys.co.uk/~graemeg/themes/start.html

I hope that helps a bit.

Thanks.

[valdir.marcos]

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]?

[valdir.marcos]

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).

Well, maybe the real reason is a lack of courage and passion. And above all, a lot of disappointment with the lack of features and the political aspect of Wayland.

Unfortunatelly, the problem of Wayland x X11 x LibreX11 x Ubuntu Mir[1] war[2] is too far beyond FPC/Lazarus' scope and end users knowledge: we, as programmers/developers, need to adapt ourselves and use whatever is available on end users' machines.

Try to imagine [irony] how end users get happy when they see messages like these: [/irony]

https://community.teamviewer.com/English/discussion/122410/teamviewer-support-on-wayland-experimental-state

TeamViewer Support on Wayland - Experimental State
JeanK
Community Manager
Apr 7, 2022
Updated Dec 30, 2025 by .Carol.fg.

It's a fact: Wayland gets more and more prominent as a display server protocol. Many Linux distributions, including Ubuntu, are adopting Wayland as the default display server.

Now it's time for TeamViewer to support also incoming connections when using Wayland in the first experimental state!

📌Note: Before getting started, make sure you are using the latest TeamViewer version. You can update your TeamViewer client by following the instructions in the article below:

📄 Update TeamViewer on Linux via repository
...

Older clients
If you see this message on the startup [...]
"teamviewer2_image.png"
[...] it means you are using an old client that does not yet support Wayland.

[1] https://en.wikipedia.org/wiki/Mir_(software)

[2] X11Libre, finally and fortunately.
https://forum.lazarus.freepascal.org/index.php/topic,71472.0.html