RE: [Rails-devel] proposed structure for tile information

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

> > Once we manage to create whole maps as graphic objects, these
> > will (I suppose) also show the preprinted tiles, so by then
> > we can suppress displaying of these 'negative' tiles.
> > But we could keep using them as holders of the upgrade rules.
> 
> Why would you want to have an entire map as a single graphic object, 
> rather than consisting of the tiles which know how to draw themselves?

To make it look a lot better, with coastlines, rivers and all....
But that is entirely optional.

> > For easy orienting and rotating tiles the tile orientation can
> > best be expressed as a number internally.
> > But for external use (XML's, logs etc.) I favour wind 
> directions too.
> 
> Since everything is in polar coordinates, it is trivial to rotate 
> everything by just adding a angular offset.  

Sure, but that is GUI matter. 
This is what we now do in the GUI (the "view") as well.

But in the "model", which drives the GUI, we also need to register 
the orientation in some way, with respect to some standard orientation.
We have 6 possible orientations, so what is
more natural that to number these from 0...5?

Erik.