cocos2d/CocosBuilder — pull request #154 by atzoum (2012-10-19 12:40:27+00:00)
Title: Feature/Fix: Plugin property type "Check" is no more bound to CCNode's visible property

## Pull Request Summary
`type=Check` & `name=visible` don't share the same strong relationship anymore... they can start seeing other people, finally!

## Functionality Changes:
1. Any property within a plugin can be of type `Check`.
When this property is also `animatable`, each keyframe acts as a *toggle switch* for the property (exactly the same way as `Visible` keyframe is working already).

2. `Visible` property has to be animatable, otherwise it won't appear at the top row of the Timeline.

## Changes at Timeline's behaviour:
1. **Top row** displays the **first** `animatable` property of the Node.
2. **Sub rows** display the **rest** `animatable` properties.

It should be possible to create a custom Node Plug-in with any combination of animatable properties!

## Example:
Let's say I have a `CCNode` *subclass* and I only want to animate its `X` value.
I can now create a new Plug-In, override **all** `CCNode` properties to be `animatable = NO`, and add my `X` property as `animatable=YES`.

If I now use this Custom Plugin inside CocosBuilder, the *timeline* will display **only one** row for it, which will *draw* the keyframes for property `X`, no matter what the *type* of `X` is.

## Notice
Code has been tested and it has been confirmed that `ccb` & `ccbi` files are read and written the same way as before (...what I mean is that I didn't notice any adverse effect).

If you Merge the Request, please **do confirm** that I didn't miss anything!

Thanks!