Re: [Rails-devel] Tile Database API & route calculation

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

> >How would you then distinguish the tracks and cities of a 
> tile on one hex
> >from those on another similar tile placed on a different hex?
> >I suppose I'm missing some point here.
> >  
> >
> You ask the map what tile is placed on hex A17 (or whatever), and it 
> gives you a pointer ot the Tile object along with the 
> orientation it was 
> placed at.  The fact that it also returns the same Tile object for a 
> different hex (or even from the TileManifest object) is 
> irrelevant since 
> it doesn't store any context.
> 
> When you are building the connectivity graph, you would 
> obviously take 
> into account the location where the tile is placed -- the tile object 
> simple gives connectivity within that hex and to the hex edges.

I guess it's mostly a matter of words.
To me, the Track, Junction and Station objects *are* the connectivity graph.
Our difference then is, as it seems to me, that you restrict the cloning 
to those Track, Junction and Station objects, not including 
the parent tile itself. Not much saving, I would think.

Or does your graph consist of entirely different objects?
 
> I realize that the current design has a UI-specific things 
> tied to the 
> tile object, but I would like to keep the Java port of the tile 
> rendering code and eventually route-calculation useable separate from 
> Rails, which means not tying it to any particular UI code.

I think only the token slot coordinates are UI-tied.
The tile images (or SVG definitiona) are completely separate from 
the tile descriotions in Tiles.xml
(although both are derived from TileDesigner now).

Erik.