Re: [Rails-devel] revenue library

[Stefan F. (web.de) <ste...@we...>]

Erik:
see below.

On Saturday 15 May 2010 22:04:15 Erik Vos wrote:
> -> Berlin tile still has to be added to the hand-made tiles (city names to
> block double runs to yellow Berlin).
>
> [EV] Does this mean that the one and only function of Station city names in
> the Tile definitions is to block multiple runs?
> That does not sound very logical to me. Cannot this blocking feature (much)
> better be made a (single) MapHex property? Or, if it's colour-dependent, in
> TileSet?  Like <NoMultipleAccess/> or such?

I found it logical, but I came up with that solution, so that does not mean 
too much. And all solutions have reasonable pro/cons. My reasons were:

A) Choosing the city attribute mirrors the solution for the offboard 
locations/stations. The only difference is that for offboard locations the 
city name (like the revenue value) is defined on the MapHex instead of 
creating different tiles for each off-board area. Allows easy implementation.

I only hope that no one ever comes up with two different off-map locations 
combined on one hex, but that would cause headaches for the revenue value as 
well.

B) Why not in TileSet? Stations are defined in Tile.xml, I did not want to 
split that information over various  files.

C) Why not one property per MapHex/Tile? It allows easily to have restrictions 
that combine several hexes/tiles into one vertex set (as I call them). And 
think about a tile with three stations, where only belong to one city.
I admit that all that is not required for the games currently implemented.

Stefan