Re: NSBrowser: so very, very broken

FROM : Sheehan Olver
DATE : Sat Jan 25 21:34:18 2003

Couldn't you just split it into two classes, one deprecated (say
"NSBrowserView" having an updated interface while "NSBrowser" is
deprecated?) You could also just have NSBrowser extend from
NSBrowserView, solving some of the issues involved, though I guess
there may be some problems since the inherency graph is public
information. To me, its better to move a framework forward, and usually
you can keep legacy code still working. The more consistent and
complete Cocoa is, the more attractive it will be two new developers.
That being said, I haven't had any issue implementing an NSBrowser, so
I can certainly see how this isn't exactly top priority.

On Friday, January 24, 2003, at 11:38  PM,
<email_removed> wrote:

> There's a bit of a problem with simplifying the API of an existing
> class like NSBrowser, since doing so has the danger of breaking
> existing code.

_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.