Re: number formatting
Re: number formatting
- Subject: Re: number formatting
- From: Michael Gersten <email@hidden>
- Date: Sun, 17 Mar 2002 19:53:03 -0800
I disagree with both of these points.
>
I myself don't give a flying fling-flang whether it truncates or
>
rounds. What is more important, IMHO, is that my program will give the
>
same display a year or two from now as it does today. Since it has
>
truncated instead of rounding for many years now, it would be a bad idea
>
to change it.
The idea of "Display the same as it always did" led to Microsoft Win95
displaying ~'d file names for all old 16 bit programs. That little
"intentional marketing gimick" caused all the need to upgrade to 32
bit apps. And, it broke the whole point of using standard interfaces
-- if a bug is found, it can be fixed.
>
It's really pointless worrying about what is right or wrong. It works
>
the way it works, and it should continue to do so. It is deadly simple
>
to apply a formatter to a text field, so the point is rather moot anyway.
It's simple to apply a formatter to _ONE_ text field.
What if you have hundreds of them, all over several nibs?
Originally, you had to make a formatter for each one.
Now, you can make one formatter, and share it with all of them.
But you still have to do that extra work. You can't tell the NS API's
"Here's a default formatter".
IB may be miles ahead of the competition. But it's still miles behind
the flexibility of WO-based development -- it is NOT based on
reusable, get it right once components. You have to keep redoing the
same thing. Trying to make it work that way took a great deal of
effort, a lot of time, and the code is owned by a former employer. And
that code didn't handle all the cases, just those that we needed.
I don't want to have the hassle of hooking up every textfield and
formatter. There are a lot of textfields that you get with other
things. I've found nibs to be very fragile things over the years (easy
to alter by accident when you are looking at things; no easy way to
see "what have I changed before I save this"), and very hard to fully
examine. It's not like you can look at a text file that has a simple
description of what's in it, and grep to make sure that
formatter=<foo> has an object foo foreach formatter.
Michael
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.