Re: NSImage is a pain
Re: NSImage is a pain
- Subject: Re: NSImage is a pain
- From: Lee Morgan <email@hidden>
- Date: Thu, 23 Jun 2005 17:12:36 -0400
On Jun 23, 2005, at 4:51 PM, Scott Anguish wrote:
On Jun 23, 2005, at 4:22 PM, Lee Morgan wrote:
As you noted "and so on." is in there, the likes of which is never good for docs IMO.
not wanting to appear defensive ( I didn't write that anyways)...
Dang, and I was really wanting to blame you Scott :-) in this case "and so on" is used in place of enumerating every single option that item supports. If every single item was listed, then it'd be a nightmare to support as additional features are added. and if those new options were missed then devs would think you can't set those.
In all fairness it does make more sense to have "and so on" there instead of listing all possible features for the exact reasons you state. However I believe a better solution than (nothing at all) would be turning "and so on." into a link to a page that contained a list of NSImageRep and the standard NSImageRep subclasses page links that contain the possible options for each, since it wouldn't be a huge list of all features (but rather a couple of lists of class features) it shouldn't become a major maintenance problem.
If at nothing else it should point to the page mmalc gave, just to avoid any possible confusion in the future over what "and so on" is.
Just my one and a third cents (seem to be losing more each day).
- Lee |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden