Re: Starting out with storyboards (on Mac)
Re: Starting out with storyboards (on Mac)
- Subject: Re: Starting out with storyboards (on Mac)
- From: Quincey Morris <email@hidden>
- Date: Tue, 01 Mar 2016 10:06:35 -0800
- Feedback-id: 167118m:167118agrif8a:167118sFJEs-YBZW:SMTPCORP
On Mar 1, 2016, at 07:20 , Jerry Krinock <email@hidden> wrote:
>
> If:
>
> • Your primary experience is in OS X>
> • You know nibs.
> • Your purpose is to ship OS X apps, not broaden your horizons.
>
> Is there any reason to learn and use storyboards?
There is one good (though mystical) reason. As we’ve seen numerous times over the years, Apple tends to signal its intentions by introducing new API. Sometimes the new co-exists alongside the old, and it’s not clear what it’s good for. Then, a while later, something big arrives that depends on the new API.
So the reason is: to learn the technology and not be blindsided later.
My suggestion is to spend *some* time on this, but not all your time on this.
On Mar 1, 2016, at 07:40 , Charles Jenkins <email@hidden> wrote:
>
> I am in Storyboards 101 right along with Daryle, and as I typed in example code from a tutorial project, my fumbling around with autolayout constraints confused XCode and caused it to lock up and crash—but not before saving my main storyboard file. After that, XCode beachballed for a long time and then crashed every time I attempted opening that file, so I lost access to all the screens in the storyboard at once.
>
> I’m sure I could have looked into ways to manually edit the file to remove the deadly constraints
I can’t remember whether this came up here or in the developer forums recently, so I apologize if I’m repeating this.
Xcode ties into the OS X Versions mechanism when saving source files, including storyboards. What it lacks is UI for browsing versions.
So, if a change that destroys the storyboard has been saved, open TextEdit, open the storyboard, and choose File -> Revert To Saved -> Browse All Versions… . You should be able to recover the previous version. If, in addition, you’ve become one of those obsessive developers who presses Command-S every time they pause to breathe (and doesn’t experience make us all obsessive in that way?) you should have pretty good granularity on recovering changes made just before the one that triggered the crash.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden