On Nov 14, 2006, at 12:08 AM, Ryan Dary wrote:
I understand the idea that people want the controls to behave
similarly on each platform, but it raises a question: What does the
customers and users of the software want? Do they want the
controls to work the same on all platforms, or do they want the
most "native" controls on their platform?
In reality probably both.
Some will answer one way and some the other.
The editfield is probably the best example of what's wrong with
simply supplying the basic native control on all sides.
The assumption and expectation seems ot be that it will behave that
way on all platforms which is not true.
So anyone writing and editor quickly runs smack into the reply "Oh
but you have to write that yourself" along with "Rb gives you the
tools to do it".
Yes, it does. So does C or C++.
But when people buy a cross platform tool many expect that they will
have similar functionality across platforms on fairly standard kinds
of controls like the editfield.
And when they don't their is disappointment.
But the down side of non-native controls is that they look non native
if the UI changes. Just look at any old Qt apps or old Java apps. You
could pick them out miles away.
On the flip side it is nice to sue native controls where possible
because then automated testing tools can actually drive the UI, and
if the standard control gets updated by the OS vendor everyone gets
that for free. This is very desirable.
So, as Brendon said, I'm not sure it's a one way or the other choice.
There needs to be both.
That way you, as a developer, can choose.
If you need a consistent cross platform experience with a text editor
you would have one. And not a very low functionality one.(At least
not if they incorporated his FTC)
If you don't need that then you don't use it and stick with the
native control.
Yes, the controls might differ in their functionality, but there is
no reason why a lowest-common-denominator subset of the desired
features couldn't be exposed, and specific enhanced, platform-
specific, features couldn't be made available. Isn't that what
they've done with the HTML browser control?
That's basically what we have now with the editfields.
And it does have issues when you try to provide a consistent cross
platform experience.
Especially if you start by developing on Windows and then move to the
Mac.
It just doesn't seem like cross platform that really works at that
point.
Just look at how many people on the lists over the years have said
something like "Hey my program is really a great idea and I need an
editor" only to find out that the editfield is inadequate for a cross
platform solution. It's a disappointment and maybe they don't make a
Mac version when this really can and should be easy for them to do
given the ret of the toolset.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
