On 24/02/2013, at 4:59 PM, N!K <pu56ucl...@alumni.purdue.edu> wrote:
> It seems so simple: create a custom view with one set, duplicate it to make 6 > such custom views, and place them all into another custom view. Well, you have to consider that NSView does not support NSCopying, though there are fairly simple ways around that, so "duplicate it" isn't as easy as it sounds if you're taking about doing this in code. Doing it in IB, fairly straightforward, except that these days IB no longer supports custom plug-ins, so it's not always possible to see what you're doing - you have to manipulate empty boxes instead of a true representation of your custom view. > I'm not advanced enough to understand why there's a discussion. Because there are Apple-provided classes that appear to get you a lot of what you need. It's usually better to use an Apple-designed class if there is one, because it's been debugged and in most cases, well-designed. The problem comes where there is a class that looks like it gets you a lot of what you need, but then needs a lot of subclassing and overriding to get the last mile. The question is at what point you draw the line and say it's better to start from something more basic, like NSView. That line will be in different places for different programmers with different levels of experience, hence the discussion. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
