support for TexturePacker XML files

[mcapraro]

in some engines, the tiles have to have a "name" property to be used by the engine (i'm using Citrus Engine on AIR). I wrote a little script that parses the TexturePacker file i built the tilesheet with and pulled out the texture names, then wrote out TMX xml for the "name" property in each of the tiles in the tileset. it seems that this would be something fruitful to have built right into Tiled. so when you open a tilset, one of the options is to load the XML data and auto-populate the property.

another awesome addition would be to read in the TexturePacker XML and honor the "frameWidth" and "frameHeight" attributes. this would allow Tiled to use ultra compressed tilesets and still display each tile properly.

[boozook]

Will be good.
+1

[bjorn]

The way I would recommended is to use a daily build of Tiled and add your unpacked images to an "image collection" tileset. This will make sure your engine can know the individual filenames and it should be able to use that to match them to the right regions in the packed texture using the associated metadata generated by TexturePacker.

This way you can use all the features provided by TexturePacker (or whatever other packer you're using) while Tiled will simply use your source images and can be blissfully unaware of your texture packing process.

[bjorn]

Closing this since the use-case should be covered by the "image collection" tilesets. See also my explanation at issue #286.