On Dec 28, 2011, at 1:37 AM, Matt Neuburg wrote: > On Mon, 26 Dec 2011 09:07:33 +0800, Roland King <r...@rols.org> said: >> >> I'll put one vote in defence of StoryBoards > > I'm not saying they're completely bad; I do use them, especially for table > view cells. But I think the overall design is just not finished; they should > have spent less time coding and more time thinking. As I've said many times > in public, the insight that the whole transition between view controller A > and view controller B might be packaged up as an object (a segue) is > potentially brilliant and might ultimate result in neater code. But it > doesn't now, for many reasons (one of which, that you yourself grant, being > the fact that you get no help whatever with the reverse of the segue).
Full agreement - and the things you've said in public make lots of sense to me too, it's not finished and custom segues are currently half useless. I have filed a couple of radars with my comments on exactly that. > >> I think also they fit nicely with iOS 5.0's improvements in UIViewController >> (especially containment > > But how can they, when they know nothing of your custom container > controller??? If you're using custom container controller you *can't* use a > storyboard. > You can .. I do. You set the class of your view controller to be your custom container class and it you get one. 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. For the two cases I have thus far it's 2-3 lines of code in each. In both of those cases the entire container VC segues away to the next scene, I don't have anything like a split view controller where I want to change one pane during a segue, so I can still easily segue from the whole VC to the next. Limited, yes, much benefit gained from storyboard in that case, no, but it's not entirely orthogonal and when I have one such controller in an app with 30 .. doesn't really matter. It would be nice to be able to plug in to IB and tell it your custom controller is a container, in the way that the tab and splitview controllers were obviously hardcoded into the current IB .. given that you can't even write IB plugins for simple views anymore I fear that will not happen anytime soon and so yes, storyboarding will be limited with your custom VCs in the way IB is limited with your custom views. > Indeed, it seems to me that just the opposite is true: the storyboard project > doesn't "fit" at all - it feels like a skunkworks project that did a bunch of > stuff without any communication to or from the rest of the company. It's > totally gone its own way (else the table view cells stuff would have migrated > back to the nib editor). It fits, but, I feel like a lot of iOS 5, there were a load of new features slammed on the table and they all showed up a bit rough. Storyboarding is definitely a bit rough. ARC was awfully rough for the first few betas but got some serious love and is now very good. I really hope that storyboards, which capture 80-90% of the transitions people probably usually do, are improved to fit with the rest of the ideas in the release, I'd like the next n releases of Xcode to be more evolutionary than revolutionary and add more coherence for the new technologies. _______________________________________________ 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
