Libraries is another one of those rather obscure topics for newbie programmers, kinda like Blocks and Delegates/Protocols. Think of libraries as just that, a resource you can use which doesn’t belong to you. A loaner 🙂
NOTE: If you need a nice tutorial on Blocks or Delegates, check out:
Ok back to our tutorial! Well a library is a piece of code that you can use (by importing it into your projects) but its not yours, so you can’t really do what you want to that piece of code, except use its functionality. In this tutorial we will create our own library and then import in into another project for its use.
The basic steps are:
1. Create your code. Usually Class method laden classes that create no state! Project must be CocoaTouch Library Framework.
A complex subject to wrap your head around, i agree! But its pretty cool once you get a working example going.
Let’s think of a game where a lander comes down from the sky (presumably on Mars – since Mars is a hot topic lately) and deploys a rover. In Cocos2d, you put all your objects on a Layer object. This means the layer class is the main class (analogous to a viewcontroller class contains buttons, views, labels, cells etc).
You create a Lander object class because you want to re-use it everywhere in the game. With every new level, you must create a new layer class but you can reuse your Lander Class. So you wan’t your Lander to be able to deploy these rovers so that each time you reuse the lander, it can deploy rovers on any given layer.
Let’s look at this image:
The Lander object declares a GameplayLayerDelegate property. This means any lander object will be a delegate to the GameplayLayer. This means the Lander can call the mystery protocol method in order to create the Rover object by saying:
And the GameplayLayer only has to adopt the GameplayLayerDelegate.
In the case of an iOS app, a typical scenario might be a To Do List where you have a list of items and you wish to add a new item. You have 2 view controllers: one lists the existing items and the other is called when the user taps on the “Add” button and wants to add a new item. You might have something that looks like this:
In this scenario the AddItemViewController on the right will want to take the user input and report it back to the ViewController on the left labeled To Do List. The steps are:
1) The ViewController on the left will conform to or adopt the AddItemViewControllerDelegate.
2) The AddItemViewController class declares its protocol like so: