Please do not post the same thing multiple times. The board software automatically flags certain posts as needing moderator attention. This happens the most often for new users. I'm pretty sure this is made clear at the time you attempt to post. Posting the same thing over and over again just makes that many more posts the moderators have to weed through later. This makes us sad. Don't make us sad. If your post/thread doesn't appear, just wait a while. Don't post it again. If it hasn't shown up by the next day, then you can try again. I normally go through posts in the mornings, and try to check a few times throughout the day, but I'm not here 24/7. There will typically be a significant delay before posts are approved. Just be patient.
Storyboard: I still don't use it.
Magic HandsPosts: 484iPhone Dev SDK Supporter, Registered Users
So Storyboard has been out for awhile now. I've read all the rants and raves about how it suppose to make dev time quicker yada yada yada. I have even played around with it quite a bit and tried to acclimate.
However, I still always reverent to not using it. I personally have not found it to be any faster and/or easier! Maybe its because I am not an expert at it. Maybe its because in reality it isn't that much faster and/or easier.
A simple example of how I, personally, find it more difficult is when passing data between classes. Maybe I missed something in the tutorial by the 7 yr. old on youTube. Maybe not.
I have spoken with some other developers that have recently started with iOS/Xcode and they seem to like it. Bah.
I wanted to see what the iOS veterans thought about it and if I should take more time to use it.
ps. sorry if this should be in another forum section.
So Storyboard has been out for awhile now. I've read all the rants and raves about how it suppose to make dev time quicker yada yada yada. I have even played around with it quite a bit and tried to acclimate.
However, I still always reverent to not using it. I personally have not found it to be any faster and/or easier! Maybe its because I am not an expert at it. Maybe its because in reality it isn't that much faster and/or easier.
A simple example of how I, personally, find it more difficult is when passing data between classes. Maybe I missed something in the tutorial by the 7 yr. old on youTube. Maybe not.
I have spoken with some other developers that have recently started with iOS/Xcode and they seem to like it. Bah.
I wanted to see what the iOS veterans thought about it and if I should take more time to use it.
ps. sorry if this should be in another forum section.
I'm in about the same boat as you. I've played with it, and it seems pretty neat, but I haven't invested the time in it to be fully up to speed, so using Storyboards is slower than doing it "the old way".
I'm still trying to get my head around managing persistent state in view controllers as you navigate between them. With storyboards, it almost forces you to dispose of a view controller when you segue away from it, and recreate it from scratch when you return. I'm more used to having my view controllers persist, and just recreating the views if needed.
Regards,
Duncan C WareTo
Animated GIF created with Face Dancer, available for free in the app store.
I'm still trying to get my head around managing persistent state in view controllers as you navigate between them. With storyboards, it almost forces you to dispose of a view controller when you segue away from it, and recreate it from scratch when you return. I'm more used to having my view controllers persist, and just recreating the views if needed.
There is an initWithNibName equivalent method for pulling VC's out of a storyboard. So presumably you could do that, stuff the VC into a property, then manage your own transitions.
I know you can find segue's by name, too, so I assume that you can force that to happen on your target VC.
I use storyboards, but I didn't start learning iOS development until after iOS 5 was released, so I'm in a different boat than the veterans of this board.
My only complaint about them is reusability. I'm just finishing up the development of my first app, and I already know my second app is going to reuse a lot of the view controllers that I have already created. The problem is, all of those view controllers are in a single storyboard file along with the ones that will not be reused. So... part of developing my second app is going to have to involve learning to smartly preplan the use of multiple storyboard files so they can be more easily reused, which of course wouldn't be an issue if I had learned the old way.
Then again, despite being a fast learner, I'm still pretty new, so my complaint should be taken with a grain of salt. I would've seen the reusability issue coming a mile away if I had had more previous experience.
There is an initWithNibName equivalent method for pulling VC's out of a storyboard. So presumably you could do that, stuff the VC into a property, then manage your own transitions.
I know you can find segue's by name, too, so I assume that you can force that to happen on your target VC.
instantiateViewControllerWithIdentifier: and performSegueWithIdentifier:sender: would be the methods you are referring to. Both are very helpful methods, although the latter is much more commonly needed in my experience.
You can also load a different storyboard using storyboardWithName:bundle: although I have yet to use that method (see my above reply about storyboard reusability for why I will need to eventually start using this).
I started developing for about a month ago, and I have to say that I really like storyboard. I believe it depends on what you are used to… I find that keeping everything at one spot, like storyboards, gives me a better overview of my different views. At least, thats my opinion :)
Magic Hands
Posts: 484iPhone Dev SDK Supporter, Registered Users
Replies
I'm still trying to get my head around managing persistent state in view controllers as you navigate between them. With storyboards, it almost forces you to dispose of a view controller when you segue away from it, and recreate it from scratch when you return. I'm more used to having my view controllers persist, and just recreating the views if needed.
Duncan C
WareTo
Animated GIF created with Face Dancer, available for free in the app store.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeI know you can find segue's by name, too, so I assume that you can force that to happen on your target VC.
SlickShopper 2 | BTIConcepts on GitHub | Free NSLog utility | Free Getter Utility | Leave a PayPal donation.
Are you a newbie? Things you should read:
Definitive Guide To Properties | UITableView Series | A Model (Object) Is A Beautiful Thing
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeMy only complaint about them is reusability. I'm just finishing up the development of my first app, and I already know my second app is going to reuse a lot of the view controllers that I have already created. The problem is, all of those view controllers are in a single storyboard file along with the ones that will not be reused. So... part of developing my second app is going to have to involve learning to smartly preplan the use of multiple storyboard files so they can be more easily reused, which of course wouldn't be an issue if I had learned the old way.
Then again, despite being a fast learner, I'm still pretty new, so my complaint should be taken with a grain of salt. I would've seen the reusability issue coming a mile away if I had had more previous experience.
Some of my code can be found on GitHub.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeYou can also load a different storyboard using storyboardWithName:bundle: although I have yet to use that method (see my above reply about storyboard reusability for why I will need to eventually start using this).
edit: fixed spelling mistake
Some of my code can be found on GitHub.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like Awesome- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like Awesome