Re: [Rails-devel] Rails-devel Digest, Vol 2, Issue 1

[Erik V. <eri...@hc...>]

> I wont have time in the next month or so to spend a 
> lot of time 
> such as finishing up the Java port of the tile rendering code 
> (or then 
> writing the Swing output device for it), but it wouldn't be hard to 
> implement the non-drawing parts of the API based on a static XML file 
> for use in route calculation (or derive it from the information 
> currently in Tiles.xml which appears to have the connectivity 
> requirements, other than track that merges before a city [ie, 
> city to A 
> and city to B share track before it gets to the city and 
> can't be used 
> by two different trains]).

As you may remember, Tiles.xml has been derived from an XML dump
of Marco Rocci's TileDesigner database (with a number of additional 
preprinted tiles added by me). Class util.ConvertTilesXML does 
that conversion (and should be in the jar). 

In Tiles.xml I had already included connectivity data for later
use in route determination etc. (indeed track merging info
is missing. I don't remember what my plan was for that part,
perhaps I would have added it by hand.)

One option may be to keep (perhaps somewhat extend) the Tiles.xml format.
Then our current capability to work with TileDesigner would not disappear.
I have created the special preprinted tiles (negative numbers) in the
TileDesigner 
both for creating new visual tiles and for updating Tiles.xml.

Of course, if you change the format, I can adapt the conversion class
mentioned.

Erik.