developing a doc based mac app. it will never be an IOS app.
I could easily create a splitview, and immediately bind document level objects to document level data using Xibs, instead of Storyboards, but I decided to put some effort into learning storyboards, on the presumption that they are the way of the future for IB.
it's not so easy with storyboards, in fact it seems darned near impossible, to just bind to data in the document. This concept of a Segue, keeps uneccessarily getting in the way. And reading up on segues, is an excercise in futility. Everything is written from the perspective of IOS development. Hello? I do not have the limitations that would make an individual ViewController loaded at a time necessary or attractive. In fact, Interface Builder very happily helped my build a Split-view Interface, without complaint or warning inside a storyboard.
I have 2 views inside a parentView, and I can't set any outlets, nor reach any ViewControllers from the parent ViewController. Every single one of these controllers will be live at the same time, I can't control them, and the documentation jumps right to the conclusion that only one ViewController will be instanced at a time.
I'm sure there is a way. And I'm sure this thread will get snowed under with those solutions. But that's not the point. I am here to find out : Does it benefit me in any way to use Storyboards? Because I am well versed in using XIBs, and if Storyboards are really the wrong tool for Desktop apps, I'd rather just avoid them.
