Re: Extending NSKeyValueCoding?
Re: Extending NSKeyValueCoding?
- Subject: Re: Extending NSKeyValueCoding?
- From: Anjo Krank <email@hidden>
- Date: Tue, 28 Oct 2003 13:25:50 +0100
- Xx-reply-to: email@hidden
Hi PA,
Am Dienstag, 28.10.03 um 11:17 Uhr schrieb petite_abeille:
And finally, I have bug report outstanding that NS* should implement
the various Collection interfaces.
Yes. That's the only reasonable thing to do. If WebObjects doesn't
play well with the java.util classes, it's pretty much a dead product
as far as I'm concerned.
?? You are spending quite a lot of time with it, though ?? I don't
really see a problem with these classes, but I'd prefer if they
extended ArrayList, HashMap and Set, so all the NSArray.Operators would
still work. They add quite a lot of convenience in the page development
process.
The argument given at WWDC 2000, when this first came up (null is not
supported as a value or key in NS*) is moot anyway, as this is also
not mandatory in the Collection contract.
Yea, whatever, all those funky Foundation classes have to go. There is
no place for sentimentality in a toolkit.
This is not about sentimentality: a lot of code simply depends on these
classes being there. So they certainly will "go away" only once WO is
dead, wept over and buried and not a minute sooner...
In any case, thanks for the moral support :)
Well, I like to cheer people up:)
Cheers, Anjo
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.