Using an explicit selector is a * recommended means of using the compiler to enforce parameter types and type safety. * * If you require more explicit access to parameters then you may wish to consider using * fromPath:toViewController:withWillNavigateSelector: instead. * * Any parameters matched in the path pattern will be passed to * willNavigateWithPatternParameters:queryParameters: on the view controller. * If willNavigateWithPatternParameters:queryParameters: is implemented on the controller then * it will be called. * * # What happens when the navigator opens a path mapped with this method: * * A view controller will be created and initialized with the initWithNibName:bundle: method. ** * Add a route from the given path to the given view controller.
Each * navigator object (TODO: Name of the object here) instance has an instance of a NIRoutingMap. * * All routes are processed using SOCKit to gather parameter information from the paths. ** * A routing map maintains a mapping of routes from paths to view controllers and objects to paths. The routing interface will look roughly like the following: The routing functionality itself will be implemented using SOCKit. Nimbus Navigation will model directly off of Three20's navigation system by using URLs to map to view controllers and mapping objects to URLs. Imagine defining a single route and using it within an app that is otherwise completely custom navigation. A developer should be completely able to slowly integrate the navigator into an existing project if they so desire. For example, we won't provide any UIViewController subclasses that implement navigation functionality like Three20 does. This means that we do not want deep integration with UIKit components. The goal is to allow a developer to use the navigator when they want to, and to use their own navigation logic when they don't. This feature will complement the existing UIKit functionality by providing a thin, optional layer on top of UIKit. This includes iOS 5's Storyboards as well as pre-iOS 5 standard UINavigationController and modal controller presentation. The goal with Nimbus navigation is to provide a powerful navigation feature that complements UIKit's existing navigation functionality. Version 1.0 - Last updated September 1st, 2011 at 10:29PM EST. (and sorry for my English ) ) DB Manager to Abstract Core Data Boilerplate and Operation Also, I'm happy that you're starting Nimbus! So, good luck, guys! I love Three20 project and use it widely in projects.
XCode 4 framework projects templates (I'm using real static framework, it is perfect as for me!): There is a quick links (if you're interested): Also, there is no necessity to set "-fno-objc-arc" flag to a bunch of Nimbus *.m files! As for me - it would be perfect if nimbus will become a set of frameworks! I've tried this solution and it is perfect! You can handle dependencies, it is much easier to add framework to the project instead of static lib with all paths and other boring things. I'm just wondering why don't you wrap Nimbus in a static frameworks?
0 kommentar(er)
