RE: [Rails-devel] Suggested object model for core generic framework

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

Ah, the object model was attached to the next message. 

A few comments (see also my other mail on companies):

- Tokens are sometimes not bound to a location but
to one of two (or even three) cities on one tile.
I think we need "City" as a separate object type
(also for revenue calculation).
Also remember that the values of two cities on one tile
are not always equal, see 1841 Venice.
Cities can merge, be upgraded, or even disappear (1856).

- How should we model the "availability" of shares, trains and tiles?
Shares sometimes come in packages, the availability 
of VariableTiles depends on Phase etc.

Taking about revenue, "Revenue" and "Route" might be useful 
(if volatile) classes.

I suspect that more objects will show up when we dig deeper,
but this looks like a very good start.

Erik.