I'd like to request some usability modifications. Can we turn this project into a proper stacking controller, one with a little more abstraction, like a UITabBarController or UINavigationController ...
In a sense, you would have perhaps only one exposed class that handles the set up and registration of menus, etc. This would distance most of the remaining parts of the framework from knowing the intricate details of the user's implementation.
@interface StackingController : UIViewController {
StackMenuViewController *menuViewController;
StackScrollViewController *stackScrollViewController;
NSArray *_stackingMenuItemControllers;
}
- (void) setMenuHeaderTitle:(NSString *)headerTitle icon:(UIImage*)headerIcon;
- (void) setMenuFooterTitle:(NSString *)footerTitle icon:(UIImage*)footerIcon;
- (void) addMenuItemController:(UIViewController*<StackableController>) menuTitle:(NSString*)title icon:(UIImage*)menuIcon;
Or alternative, you could set up a delegate/protocol ... the main controller allows the user to set a delegate that will answer questions about menu items (stackable controllers), icons, titles, etc.
I'd like to request some usability modifications. Can we turn this project into a proper stacking controller, one with a little more abstraction, like a UITabBarController or UINavigationController ...
In a sense, you would have perhaps only one exposed class that handles the set up and registration of menus, etc. This would distance most of the remaining parts of the framework from knowing the intricate details of the user's implementation.
Or alternative, you could set up a delegate/protocol ... the main controller allows the user to set a delegate that will answer questions about menu items (stackable controllers), icons, titles, etc.