Separate project configuration from exported data

[GoogleCodeExporter]

The idea is to separate the exported data (bin, json, xml) from the project 
configuration, so someone could create a new project on his main folder and 
point where the images (probably before a texture pack) are, and map the images 
with a key to be identified when loading the fixtures, for example:

project file:
export location
default export type
map of key,imagelocation
   door -> images/mysuperdoor.png
   house -> images/somehouse.png

exported fixtures file:
door -> a polygon
house -> another polygon

Working in this way, you can avoid having the images location as the exported 
fixtures identifier instead you use the key you want for them. Also, the 
exported fixture file could be anywhere.

Don't know if I explained the issue well, hope I did and hope you find this 
useful.

Original issue reported on code.google.com by ariel.co...@gmail.com on 28 Dec 2011 at 8:24

[GoogleCodeExporter]

Accepted, but won't come before the next release, featuring big changes :)

Original comment by aurelien.ribon on 13 Jan 2012 at 9:59

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Part of the problem was fixed: fixtures are now named with user-chosen 
identifiers instead of using the images paths.

Original comment by aurelien.ribon on 27 Apr 2012 at 8:01

[GoogleCodeExporter]

In order to simplify the project management, the output will remain a single 
file for now. If the new features of the tool (dynamic objects and joints) 
requires too much project specific data in the exported file, I'll split the 
output in two: (1) project configuration and (2) exported data for loaders.

Closing the issue for now.

Original comment by aurelien.ribon on 29 May 2012 at 8:42

• Changed state: Done