On Jan 28, 2008, at 12:04 PM, Mr. Pierre Frisch wrote:
I understand this problem quite well but I just curious of how much
code is out there.
I am fairly certain that we have some other stuff using the format
binding. We use NSTimestampFormatter in about 95% of our code. It
is all pretty concentrated, so updating this will not be too painful.
I personally have moved out of NSTimestampFormatter a long time ago
so I am probably a bad judge.
I think that is probably true. :-) I think the people to keep in
mind are not the power users, but the people with less experience.
There are probably more of them and they are more likely to use this
and the format binding and will have more trouble making this
change. Add to that the large number of applications using this
class and the need to do something much more than just recompile and
test and the "cost" of a better solution starts to look really worth
while.
I will have a look into the problem but I cannot guarantee anything.
I (and I am guessing this is getting obvious) really think that there
should be a bridge in place, as simple as it might be. Please.
Chuck
On Jan 28, 2008, at 11:47, Mike Schrag wrote:
Having NSTimestampFormatter as a "symbol translating sub-class"
would ease the pain of transition for many.
Yeah, this is what I'm proposing as well ... I feel Pierre's pain
with not wanting to rewrite and maintain deprecated code, but I
fear WO becoming what everyone hates about Tapestry, which is that
it goes through huge breaking revisions every release. There is a
large base of legacy apps, and especially if there are relatively
straightforward deprecation routes, it would be better to not
break than to break, I think (this is obviously subject to a
religious debate, I suspect). I'm especially wary of breaking
changes that just break semantics rather than syntax. In this
case, it's breaking the interpretation of random strings inside of
WODs, which will make for a really annoying fix. Alternatively, I
suppose someone could write a conversion app to convert all the
old style into new style, but that only partially addresses the
issue.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/pierre%
40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%
40global-village.net
This email sent to [EMAIL PROTECTED]
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
