Navigation Layer - best practices to implement?

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

Navigation Layer - best practices to implement?

(4 posts) (2 voices)

Started 1 year ago by emilebennett
Latest reply from Dragyn

Tags:

emilebennett
Member

Hi Guys,

I'm working on an interactive kids book which has about 50 pages, and need to figure out the best way to implement a navigation system.

Delegates/Protocols/Layers ... i'm somewhat confused as to which is the best way to go. Essentially each page will be a separate scene object. Rather than programming the navigation in each scene, I just want to write 1 navigation class that I can pull in to (or rather, on top of) each scene quickly and easily.

I have already written a singleton class for handling navigation changes which is working nicely, so now it's about building the navigation view and how best to apply it to each page.

Any guidance on the best practice (non-dirty!) way of doing this would be much appreciated.

Thanks a lot guys, looking forward to your responses!

Emile

Posted 1 year ago #
Dragyn
Member

I'd suggest building a new subclass of CCLayer, and adding all your navigation control creation methods to that subclass. Then, all your pages include layers that are subclasses of that. This will keep all page control GUI logic in that one object, and you won't have to worry about anything except a call to those methods in your individual pages. (i.e [self displayNavControls])

Posted 1 year ago #
emilebennett
Member

Hi Dragyn, thanks for your response.

Just to clarify, do you mean that my book pages themselves subclass my navigation object, or that they contain a 2nd layer that is the navigation object?

I imagine you mean the first?

cheers, emile

Posted 1 year ago #
Dragyn
Member

I mean that your direct subclass of CCLayer contains the navigation object, and the pages inherit from that subclass.

Here's how I would lay it out:

CClayerWithNavControlMethods inherits from CCLayer

BookPageOneLayer inherits from CClayerWithNavControlMethods
BookPageTwoLayer inherits from CClayerWithNavControlMethods
BookPageThreeLayer inherits from CClayerWithNavControlMethods
...

And actually, the implementation of the navigation controls can be called in the INIT of CClayerWithNavControlMethods, as long as the BookPageLayers call [super init] in their init methods.

(Obviously, I used way too explicit/ugly names for this example. Hopefully your names are cooler than mine.)

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.