What about SpriteBuilder

[oxeron]

they added some stuff in 2.0 for retina displays but it's not finished ...

I have it running 3.4.9 in the hood, but some stuff need to be corrected

Maybe I should use 1.4 like you, less things to correct/modify ...

[jogo]

Will the resource system be like the resources from v4 described in https://github.com/cocos2d/cocos2d-objc/wiki/Cocos2D-v4-Alpha-Notes ? In general these nodes seem quite sensible to me. It did not follow develop really in the last two years, is there any specific problem prohibiting the use of the v4 version and continuing from there?

[birkemose]

I think, that if you can settle on which version to use, and get it to compile so that we can keep adding features, that we should fork it, and add it to the official cocos2d repo. That way we can make absolutely sure, that it continues to work.

So basically the latest version you can find, which works with 3.4.9

[oxeron]

There were some good ideas in this v4 :

Automatic Image Scaling

Explicit File Resolutions

CCSetup

...

[oxeron]

In my current version, when exporting a demo project in SB, I get this:

With AppStore version I get this:

Assets export in not the same, and also ccb exported files are now named .sbi instead of .ccbi This will not work with cocos 3.4.9 ...

This version also creates a Xcode project using CCSetup class which is not implemented in cocos2D 3.4.9 (found it in this repo: https://github.com/cocos2d/cocos2d-objc/tree/821826a16e8e4a1b2b2b2938878e062904279d2c/cocos2d/Platforms)

There were some good ideas in all this ... Should I start again with an older SB version or try to implement/add what is missing in cocos too or make this version of SB export a 3.4.9 compatible project ?

[oxeron]

I think I will start again with an older SB version, in order to have something fully compatible with 3.4.9 version and after add 3.5 support

We could look afterwards to add new features that were planed in v4, but it should be added both in cocos and in SB at the same time

[oxeron]

OK, I have a new SB version working with 3.4.9 inside, successfully exporting a test project using 3.4.9 too, compiling OK under Xcode ... Must do some more tests and create a clean github repository to put this

Unfortunately, we have to change some things to cocos2d and chipmunk too ...

What is the best solution, as we can't push requests to these projects ? should I create public repositories for all these related projects and put my modification inside ? (mostly concerning Xcode compilation information)

[s1ddok]

Develop it separetly for now, if everything is on i will copy it to main cocos2d repo.

[oxeron]

Here is my dev build:

https://www.dropbox.com/s/50891bn9l80hunq/SpriteBuilder.zip?dl=0

Can't guarantee it will even launch on someone else computer I built it on a 10.11 iMac

[s1ddok]

Better fork a repo and do it there, dropbox is not useful

[oxeron]

yes I know, this is just a test

[rraallvv]

Hi there!

Just wanted to know whether there is already a new “official” repo for SpriteBuilder. I think the faster the official repo’s been ruled out, the faster we can start fixing/updating things and testing new features.

Regards.

[oxeron]

I'm working on finishing the first stable release and it will be published on github in the cocosbuilder repository in a new 3.5 branch We'll keep you informed when it's done