cocos2d/cocos2d-frame — pull request #17 by gdagley (2013-05-18 05:47:52+00:00)
Title: New directory structure

Proposed structure that I am working on:

/my_new_game_project
/proj.ios
/proj.android
/libs
/published
/iOS
/mostly same directory structure as /shared/Resources
/Android
/mostly same directory structure as /shared/Resources
/shared
/Classes
/Resources
/images
/interface
/js
/sounds
project.ccbproj

My thinking for the folder structure is that I want someone who comes the project to immediately know where everything is. `proj.ios/` and `proj.android/` let's someone know that is where the platform wrappers are. `libs/` is where any external libraries will be.

`shared/` is where the common code (C++ or JS) and assets will live. And `published/` will be where Cocosbuilder puts files when publishing the CCB project. I did this to avoid confusing myself/others with duplicated files in the `/shared/Resources`. Since those folders really aren't shared, I didn't want to leave them in the `shared/` folder. I also used the images, interface, js, and sounds directories similar to how the sample [CocosDragonJS project](https://github.com/minggo/cocos2d-js-tests/tree/for-cocos2dx/games/CocosDragonJS/Source) does. It allows me to add the `published/iOS/` folders to the xCode project as Folder References. I had problems with the Xcode project missing new files as they were added and published and the Folder References helped solve that for me. Having `/published/Android` makes the copy to the Android assets folder straight forward too.

I have not figured out what to do with the shared Cocosplayer resource files yet, but once those are in place, the current `Resources/` will go away too.