From: Erik V. <eri...@hc...> - 2007-10-26 17:26:45
|
> Since Rails doesn't render the tiles from the tile data, it > seems like > most of that data is useless to Rails. Also, I currently do not keep > information useful for route calculations which Rails will eventually > need, although I wouldn't be averse to extended it and > storing it as well. > Finally, I am more concerned with a unified database of all > tiles so I can > search for which games contain which tiles etc while Rails > doesn't care > for such a database (at least that is my recollection of a discussion > about this a couple of years ago). Our "database" is a big file named Tile.xml that has all the tiles that currently exist in our version of the TileDesigner file. I run the XML exported by TileDesigner through a utility that extracts the connectivity information from it*. >From this big file, another utility extracts the tiles needed for a particular game into a game-specific subset Tiles.xml file. As it is now, we have to live which the original TileDesigner features. This does not cover all our graphics needs (for instance, we can't create off-board tiles with "arrows"), but for creating the connectivity XML in a simple way it seems good enough to me. I'll look at your upload later. For now it seems to me, that I can best continue to create new tiles via TileDesigner for the purpose of XML creation, whereas Brett can meanwhile work with you to see if we can obtain better graphics that way. Any remaining numbering or naming differences can be resolved via our manually coded TileSet.xml files, e.g. by the 'pic' attribute that I proposed in an earlier post. Erik. *which is why I prefer the old-style 80-83 tiles for this purpose. |