Re: Question about Deprecated Methods
Re: Question about Deprecated Methods
- Subject: Re: Question about Deprecated Methods
- From: Charles Srstka <email@hidden>
- Date: Sat, 27 Mar 2004 11:30:28 -0600
On Mar 27, 2004, at 6:37 AM, Gregory Weston wrote:
>
On Mar 27, 2004, at 12:14 AM, Charles Srstka wrote:
>
>
> but frankly, I just continue to use selectedRowEnumerator. Having to
>
> use the above construct every time you wanted to access the selected
>
> item(s) in a table view would be a pain. And besides, can Apple really
>
> remove those methods? They would break so much software by doing so
>
> that it's not even silly. If they do, it will be a very, very long
>
> time
>
> before they are able to do so. When I write an app that has 10.3 as
>
> the
>
> minimum requirement, then and only then will I use these new methods.
>
>
Bad strategy, unless you fully expect that your software doesn't have
>
a particularly long usable lifespan. The point of deprecating methods
>
is to give fair warning that at some point in the future they _will_
>
go away, so that by the time that happens they won't be breaking any
>
software that gets even cursory maintenance. Not today. Probably not
>
with 10.4. But if you get caught scrambling to fix half a dozen
>
programs in November 2005 you'll have only yourself to blame. And so
>
will your users.
Well maybe in November 2005 I won't have so many users still on 10.2.x
who will have my head if I drop support for their OS, as everyone will
be using 10.5 and 10.2 will be as ancient as 10.0 is now. As it is, I
tried to drop 10.1 support a while ago and a bunch of them complained,
so I had to re-introduce support for it as well. I should hope that
Apple would get around to removing some ancient methods that were
deprecated even in 10.1, IIRC, and which I doubt anyone still uses like
-[NSApplication runModalForWindow:relativeToWindow:] before they remove
a method like selectedRowEnumerator which *any* app developed under
10.2 or lower which has a table view in it is going to be using. So at
present my options are either to break support for 10.2 and lower and
anger many of my users or severely ugly my code up with lots of AppKit
version checking. On second thought, I guess I could define my own
selectedRowEnumerator method on my NSTableView subclass that calls
super's implementation in 10.2 and lower and converts the NSIndexSet to
an enumerator of NSNumbers in 10.3 and higher, that would probably be
okay. Hmm...
Charles
_______________________________________________
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.