This is rephrasing my recent "binding an array controller to columns in an NSTableView" post. Saying "columns in an NSTableView" wasn't accurate.
Here's my basic data model: House: Attributes: name; Relationships: colors (to-many). Color: Attributes: name; Relationships: house. A house has one or more colors. Typically, I only expect to have 6 or 8 colors for each house. (I'm using House and Color for demonstrative purposes.) I want every color object to be associated with a custom view. All the color views for a given house need to be presented as a horizontally scrolling list. I also need drag and drop functionality to change the order of the colors in the list. I think I could use a view based table with one row with the number of columns equal to the number of colors. Does this sound like a reasonable approach? Whenever a color object is added or removed (from a house), I'll need to create or remove the associated custom color view. I'm not certain where the code (or binding) to create or remove the custom view for each color object should go. Thanks, Chuck _______________________________________________ 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
