So i created a new plugin, decided that i wanted to use a storyboard in my Buzztouch application. I can get Xib's to work no problems, but without a file's Owner in StoryBoard i can't seem to get it working..? Any Ideas? Thanks in advance. :) edit: Still uber stuck with this, been pulling my hair out all day!

Create storyboard name it same as class files of custom plugin Highlight the view controller make custom class same as class files (as with xib} Give that bad boy a storyboard id (just underneath) Add this code to your .m file under view will appear UIStoryboard *storyboard = [UIStoryboard storyboardWithName:@"yourcustomclass" bundle:nil]; UIViewController *vc = [storyboard instantiateViewControllerWithIdentifier:@"storyboardID"]; [vc setModalPresentationStyle:UIModalTransitionStyleCrossDissolve]; [self presentModalViewController:vc animated:NO]; Voila

nice. thanks for the tip. curious to see how this works with the BTnavigation controller.

Haveant had chance to try this, looks right though. I still don't understand why you don't have Files Owner for each view?

@atrain53 it doesn't react very well at all. You have to program every nav bar seperately on each controller in the storyboard, but they can all be linked into the same class and modified using the buzztouch control panel.

I suspected something like that. I guess I could see using a storyboard to link a couple of views together - but getting back to the BT navigation in an app was tricky enough with XIB's... I didn't have much interest trying to figure out using Storyboards - but there are a couple of VC's that use them I was tinkering with. Nice to have the option to use SB's if they will work. Thanks! is that the method then - you just add the BT_viewUtilities configurebackgroundandnavbar statement on each screen then inside a viewwillappear? and hows your icarousel menu going? I've got some childitems set-up now, but it doesn't like to take image names from JSON values however! odd...

I'm waiting for david to get back to me. I'm working on about six different plugins at the moment, there's no rush, store not open till january. The navbar will not marry as a view in xib file is controlled by the class, where as the view is built into the view controller so you can't use the navbar code. you have to do it separetly will still link to control panel . I wouldn't advise using the storyboard as a plugin either as it's not backward compatible, plus it's quite complicated to get the classes. I have used it as a instruction manual for aurasma.

I am a bit concerned of the difficulty since Storyboards will be used even more in the future. I have asked David Book to share his crystal ball with us on this topic.

@MacBoy: Crystal ball - funny. I'm not exactly sure what you guys are asking here. The Storyboard docs are here, for reference: http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/UsingViewControllersinYourApplication/UsingViewControllersinYourApplication.html The idea is that you can use Storyboards to connect screens and their data together. In most cases, an app either "Users Storyboards" or "Does not use Storyboards." Naturally there are cases where Storyboards are intermingled in other application UI parts without specifying the Main Storyboard in your app's plist (application settings). Like anything else in programming, there are countless ways to use, or avoid this concept. I'm happy to lend some thoughts on specific questions?