On Dec 28, 2011, at 5:46 AM, Roland King wrote: > What you can't do is storyboard the embedded viewcontrollers into it, you > have to add them in code on creation. You can however set up those embedded > view controllers in the same storyboard as standalone headless unconnected > entities and instantiate them when you need and set them into your container > controller
Yes, good point (and very well described). And this accords well with what others have said too - instead of one gigantic main storyboard for the whole app, a better approach might be multiple storyboards encapsulating short spurts of successive segues, as it were. (And of course, as I've said, I'm using storyboards as a source of UITableViewControllers, just to get the benefits of designing the prototype cell in same editor or of designing the whole table as static cells.) So, I think we agree, there's no point throwing out the baby with the bathwater. But I look forward to a better baby! :) m. -- matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Among the 2007 MacTech Top 25, http://tinyurl.com/2rh4pf Programming iOS 4! http://www.apeth.net/matt/default.html#iosbook RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
