From: Stefan F. <ste...@we...> - 2011-07-20 06:16:08
|
Erik, 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? Stefan |