By not being native fpGUI faults the user while trying to apply a cross-platform corporate symmetry.
Such statements always makes me laugh.
Lets be realist, if the person that pays me to develop their app wants pink polka dots on their user interface, then they WILL get pink polka dots. Who are you, me, some OS or some open source project to dictate to the paying customer what he or she may or may not get.
I'm sorry, but I don't agree.
You, me, some OS and especially the
paying customer, all have to account for the user.
So if the person wants polka dots, you, the developer, are to blame if he gets it, and then fails the user with it.
On a side note:
Web Apps - no native look (yet millions of Internet users have no problem with that) , Qt (most popular gui toolkit around) - not a native toolkit - all custom drawn, Microsoft Office (most popular office suite) - lots of custom components, Media Players - lots and lots of custom components, Mobile Devices - lots of non-native components and apps.
By native I don't mean the look, the colors.
By native I mean the ability to scale and fit and respect custom settings.
Web Apps are native to that concern.
People and companies want their products to stand out above the rest, that is why Microsoft makes Office, Visual Studio, IE etc look different to the rest of Windows. Same goes for Mac OS X. It's all about branding! LCL stifles this, and that is why I was asked to develop fpGUI (at least that was one of many reasons).
fpGUi functionality is far form being at that level: MS Office etc.
Just saying, let's be realistic.
Take a look at a fpGUI interface on a larger resolution with a larger DPI.
That depends on the app. Our commercial apps scale perfectly with DPI changes, but we added that functionality ourselves - it doesn't come as standard with fpGUI yet. Same applies to LCL. Lazarus IDE (compiled for GTK2), among many other apps, don't scale well on my system either.
If there is missing functionality in fpGUI, available only commercially, than this announcement is not in its right place, is it? Could you please provide a fpGUI binary to test that?
As it is, it doesn't scale well at all and it's not usable at all from my tests. I feel like Gulliver in Lilliput land, in a mono world, and I thought I should point this out. I was wrong?
Bottom line... if fpGUI doesn't suite your needs, simply don't use it.
My posts were only meant as honest assessment.
I acknowledge the effort, and I'm sorry if it came across as something else.
--
Mitică