Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommended approach w/ TyphoonStoryboarrd #216

Closed
jasperblues opened this issue May 2, 2014 · 3 comments
Closed

Recommended approach w/ TyphoonStoryboarrd #216

jasperblues opened this issue May 2, 2014 · 3 comments

Comments

@jasperblues
Copy link
Member

The recommend approach of obtaining a TyphoonStoryboard is to load it within a view controller, as follows:

 TyphoonStoryboard *storyboard = [TyphoonStoryboard storyboardWithName:storyboardName factory:factory bundle:nil];

Update docs to show how to load if from the assembly using run-time arguments.

@jasperblues
Copy link
Member Author

Also need to document new bootstrapping approach for UIStateRestoration, with plist.

@IvanUshakov
Copy link
Contributor

Hi, @jasperblues. I start new app and would like to use TyphoonStoryboard and plist configuration. I would like refine, did you done this documentation? I can't find it. Or I should find my way to done it?:-)

I am waiting for your talk about Typhoon in Moscow at MBLT DEV

@jasperblues
Copy link
Member Author

Hello @IvanUshakov, it is supported and documented. But we don't yet have a sample application. There are two places you can use a plist:

  • Plist bootstrapping. The Typhoon Swift example shows this. This is the way to start Typhoon in a storyboard application.
  • Plist configuration. Both of the sample apps show this.

If you're interested in contributing such a sample we can help you. Otherwise please go ahead and try and if you have any questions we can answer on StackOverflow. . . worse case we can work through it and the conference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants