On 4/2/07, Florian Klaempfl <[EMAIL PROTECTED]> wrote:
Having native controls is simply something people request. Just try to
convince somebody to use a Qt or GTK application on Windows or MacOS.
They will tell you always it looks and behaves strange. Consistent
Getting a native look is easy. QThemes (or something like that) was a
add on unit for CLX which could make a Kylix application look exactly
like XP (blue and silver themes) and exactly like a few GTK themes.
As far as I can see, getting the look of Windows and most probably the
behaviour as well would be a priority. I don't even run Windows on
any of my computers (I'm a Linux guy), but do understand the reality
that Windows is the dominant platform (no matter how much I hate it).
As for GTK and KDE. Does anybody actually know what the widgets are
supposed to look like? Lets take Gnome based distro's as an example.
Redhat, Ubuntu, Debian, Suse just to name a few all have different
default themes. Then run something like 'xman' which looks like the
stone ages. I don't think any *nix user can complain about look and
feel. There is *no* standard look and feel or behaviour on it. I use
Linux 24/7 and that's reality I live with. Giving the behaviour of
Windows widgets should please 95% of the target market. After all, a
ComboBox is a ComboBox. Making the object pascal widget set themeable
would solve the other problems.
I'm not being unrealistic. Our company targets a corporate
environment - very different from the home/hobby user. Integrating
with that environment, which is predominantly Windows, the obvious
choice would be to mimic the Windows behaviour. The path of least
resistance! As they switch users to Linux, those users will be
familiar with the widget set behaviour. Also in our environment, those
users will be spending 9-5 in our application and occasionally switch
to check emails or browse the web. Letting those users experience the
same behaviour under Windows and Linux in critical. After all, it's
the same application.
That brings me to another point. If those users can browse the web,
they can handle slightly different looking applications (on different
platforms). Their is no consistent look for web pages, but yet the
whole world can use it.
As I mentioned in my first post, I'm only concerned with the
commercial environment. We want a standard set of widgets we can use
in our applications. No 3rd Party widgets like fancy calendar edit
boxes, funky treeviews or calculator edit boxes, etc.. We already
burnt our fingers with that one in our previous Delphi projects. This
thread is to try and find out what it would take to get us to that
standard set of widgets. And if it makes the developer's life a bit
easier along the way, so much the better - after all, time is money.
Regards,
Graeme.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
