Enhancement: support for CCProgressNode

[tanis2000]

It would be nice to have support for CCProgressNode from within SpriteBuilder. I usually use that for health bars and similar stuff that I attach to players and enemies.

[dissidently]

+1

I use it for animations.

[haligalaph]

If there was support for plugins as in CocosBuilder, It would be easy to add CCProgressNode and many others. Users would be able to add required nodes themself and then share these plugins with others.

[haligalaph]

It turns out that SpriteBuilder has the same plugins' structure as CocosBuilder, thanks to detailed tutorial written by @LearnCocos2D . I wrote several plugins for CocosBuilder including CCProgressTimer, so it wasn't difficult to adapt it for SpriteBuilder and cocos2d 3.0. Cause of CCProgressNode's implementation, I had to write additional category for it, which must be included to project in order to load CCProgressNode from ccb-file. Because of this, I think, this plugin shouldn't be included into SpriteBuilder, it should be external one.

[tanis2000]

@haligalaph that's interesting. I thought they dropped support for plugins completely. Are you planning on releasing your plugins?

[haligalaph]

@tanis2000 , If you are interested in CCProgressNode plugin, it can be found in my fork of SpriteBuilder within appropriate branch. You could compile it and add CCProgressNode.ccbPlugNode into SpriteBuilder's PlugIns folder. Don't forget to add CCProgressNode+SpriteBuilder category into your project. Since I'm planning to migrate to SpriteBuilder and cocos2d v3 soon, I will adapt other plugins. Maybe somebody else will find them useful.

[LearnCocos2D]

@tanis2000 plugin support is still there, currently it is using additional targets in the SpriteBuilder .xcodeproj rather than separate projects. The plan is to create a separate repository with SpriteBuilder plugins and a .xcodeproj containing the node plugin targets so that it becomes easier to build plugins without having to build SpriteBuilder (in theory, in practice one ought to test one's newly created plugins of course).