Ah! A Boilermaker. Did my MS and PhD there in EE may years ago, before I went to Bell Labs.
I just suggested a collection view because they are so easy to use when you need an array of identical views bound to an array of objects via the represented object. You just create the prototype and let the collection view do the replication work. On 2/23/13 11:59 PM, "N!K" <pu56ucl...@alumni.purdue.edu> wrote: > I've been following this thread because I have a similar application in mind, > displaying 6 sets (groupings, not NSSets) consisting of a label with slider > and > textview, both bound to an ivar. > > 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. > I'm not advanced enough to understand why there's a discussion. > > On the other hand, there seems to be interest in more complex ways, which > implies that there are advantages in them that I don't see. Specifically, I > don't see advantage in going on with collection views or boxes, and I don't > know what you would do with a subclass (of what?). > > What am I missing? It must be elementary. _______________________________________________ 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
