Creating a proper stacking controller as abstraction layer / delegate

[grgcombs]

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.

[thinknikhil]

This is a really great idea. We will surely implement this. If you have already started working on this, send us the pull request :)

Thanks for the suggestion :)

[grgcombs]

Is file renaming a problem? I've renamed most of the filenames to make it easier to integrate into larger projects. But I'm happy to issue a pull request. At the very least, you'll see what I've been up to ;-)

[Reefaq]

hey sorry for not being active, we were busy with other projects ..

renaming a file is not a problem.. Go for it ;-)

Looking forward for ur pull request !!