I've got an issue with the rendertexture class, when i include the example as an extra layer in my project, it seems to clip the right hand side.. anyone have any idea what could be causing that?

Ahhh.. nvm

http://www.cocos2d-iphone.org/forum/topic/1384#post-8311

tricky trying to get all the new cool stuff w/ an older core set :)

ahh apologies. So its a static lib, but its created within the same project then?

This is the first time I've used a template (the box2d one was a great time saver. Thanks!), and my previous xcode projects were based off the tutorial at http://www.clintharris.net/2009/iphone-app-shared-libraries/

This uses the 'Source Tree' feature in xcode, so you can have cocos2d & your other dependencies in their own dirs (so you can easily svn update to grab changes), separate to your project code, and you can easily flick between different versions by changing COCOS2D_SRC to the dir of your choice. Or setup different source trees so various projects can link to specific versions. Its made updating other projects super easy. No copying and pasting of files needed.

I presumed that was a feature of a 'static lib', but it seems thats an extra way to use them within xcode.

@PhilM: the templates use static libs.

there is no "official" upgrade path, but you can do:

A)

1. Create a new template
2. copy all your classes / resources from the old template to the new one

B)

1. copy all the cocos2d / cocosdenshion / cocoslive / box2d / chipmunk files from the new template to the old one
2. Make sure to add the new files/directory (eg: FontLabel)

Thanks riq (& other contributors), great work!

It would be nice if the templates used cocos2d and extra dependencies as a static libs, as that would make upgrading much easier (IMHO). Also interested in the 'official' upgrade path for now.

what's the "official" way to upgrade a project that was created using the cocos2d template? just copy cocos2d/box2d/etc directories over?

I am not sure I can open anything else than defect issues, but ok.

@badawe: Both of them are good engines. Box2d seems to be more advanced, but the Chipmunk API seems to be easier to learn.

@ob1: I'm not sure if it will part of v0.9 or not, but could you add an enhancement on the issue tracker describing the feature ? thanks

Keep up great work

Riq, what about also adding "button sprites" in 0.9 that support clicks and states and such. Would often be easier to use than menuItemImage I think.

thanks riq! keep the good work.

Can i ask something?

After many treads like: Box2D vs Chipmunk and all of then enumerate the superiority of Box2D why keep chipmunk support? I know some developer use chipmunk yet, but

Hi,

v0.8.2-rc0 is available for download:
http://cocos2d-iphone.googlecode.com/files/cocos2d-iphone-0.8.2-rc0.tar.gz

Release Notes:
http://www.cocos2d-iphone.org/wiki/doku.php/release_notes:0_8_2_rc0

Highlights:
- Fixes and more fixes
- Chipmunk + cocos2d template

What's next:
- v0.8.2 final should be ready in 1 or 2 weeks
- after v0.8.2 I'll put focus on v0.9 ( new sprites, CC namespace and more )
- a v0.8.3 might be released if needed