From: John A. T. <ja...@ja...> - 2011-07-20 13:33:10
|
On Wed, Jul 20, 2011 at 2:18 AM, Stefan Frey <ste...@we...> wrote: > I have implemented revenue calculation for hex trains (for 1826). Instead > of a > dynamic modifier I kept the (older) plan to add that to the revenue > calculator > directly. So I treat hex trains as "first-class" citizens of Rails and they > should be supported directly via attributes in XML. > > What is your preference for the naming and type of such an attribute? > I would currently prefer a simple boolean isHexTrain = "yes" and (mis-) use > the number of majors as the number of hexes the train can travel. > > But maybe something like distanceType={stops|hexes} and then an integer > attribute for hexDistance is preferable? > BTW, note that there are two types of hex trains -- in 1844 a 2H train runs to two adjacent hexes, while in 18US a 1H train runs to two adjacent hexes (ie, it has a range of 1 from the origin). You can represent them internally the same way, but you need to display them differently. -- John A. Tamplin |