Graeme Geldenhuys wrote:
For obvious reasons (no LCL-fpGUI yet) we opted for the last option.
We still use Lazarus as our IDE and we (fpGUI) do have our own visual
form designer.
Graeme,
Will fpGUI/LCL still support theming later when theming is implemented?
For me, using the native widget set is OK 95% of the time, but sometimes you
need to put a theme on it. But sometimes its necessary to create applications
that are very different from traditional widget sets as you have found.
The be-all-end-all of widget sets IMO, would be one that supports native look
and behavior as well as custom themes when required.
My company has a pos application for restaurants that consists primarily of 2
separate applications. The back office, looks and works like most traditional
desktop applications.
The POS portion however, is like night and day. Not just because navigation is
primarily through touch screen taps, but in terms of the UI itself which I think
any programmer would be hard pressed to guess which language it was written in
just by looking at the application itself.
http://www.datatrakpos.com/pos/screenshots.aspx
Many hours of photoshop and writing TImage descendents to get that look. I've
tried (and purchased 2 of) 3 theming engines for Delphi I've found and not one
could offer the speed and flicker free rendering we achieved from using simple
TImage descendents. This was especially important in a POS app where the UI
really has to "snap" and keep up with the users who eventually operate the POS
blindfolded.
I'm curious to see how fpGUI theming shapes up in terms of this kind of theme
rendering and speed.
--
Warm Regards,
Lee
"Everything I needed to learn in life, I learned selling encyclopedias door to
door."
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
