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

[John A. T. <ja...@ja...>]

On Sun, 20 Nov 2005, Erik Vos wrote:

>> What bitmaps are you referring to?  Everything is scalable graphics.
>
> Like this (from your original post to which I responded):
>
> junc_edge_conn	integer		bitmap of connections from junctions to
> edges
> 				d30-d31: two-bit type field
> 				00: normal; d0-d5=J0/A - J0/F, d6=J1/A...
> 				01: 6-way; always connected to nearest
> 				    edge, d0-d4=J0/J1 - J0/J5, ...
> 				1x: reserved
> interjunc_conn	integer		bitmap of connections between junctions
> 				d0-d4=J0/J1 - J0/J5, ...

It is pretty easy to do quick connectivity lookups and to rotate the 
connectivity graphs.  It is just a cache of the detailed 
junction/connection data, but much faster than having to check everything. 
If you don't need it for rails, that can certainly be left out.

> - well, you asked for comments, IIRC....

Certainly, I just thought you were referring to bitmap images.

> 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?

> 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.  I was just suggesting a 
shorthand for manually created XML tiles.

-- 
John A. Tamplin					ja...@ja...
770/436-5387 HOME				4116 Manson Ave
                 		 		Smyrna, GA  30082-3723