Re: [Rails-devel] using dropbox

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

> However!  While I have your ear, I did want to mention the 1-2  
> features that we would most want-   %-)
> 
> a) hex-edge boundaries displayed on the map
> 
> Eg, around Erie in 1830- none of these edges show on the rails map,  
> although rails enforces them in track-tile play.
> 
> This is a fairly big deal, as we have to use a separate jpg of the  
> static game map, to actually see the boundaries- in 1830 and 18AL (I  
> think there's only 1 impassable hex-edge in 18AL).

That is a long-standing request, and I will give it another look, but it's
not trivial
(and programming graphics isn't really my best skill).
 
> b) rollover city names more consistent
> 
> Eg- in 18AL, Nashville isn't identified as Nashville- just A3 or  
> whatever.  (I think it's Nashville, but anyway there's numerous  
> examples- lots of 1830 cities like baltimore, etc.)
> 
> In hot-seat play, it might not matter- but, when using rails 
> as a pbem  
> console, this makes it substantially more awkward to verify or  
> summarize route and track coordinates in email.

You can easily add names yourself in the Map.xml file of each game. 
See 18AL/Map.xml for examples, e.g. <Hex name="F1" tile="-112"
city="Tupelo"/> 
Indeed it has not been not done consistently in that game.
Why not update it yourself and submit the result?

On 1830, opinions differ on which cities belong to which hexes 
(see http://www.18xx.net/1830/1830n.htm) and I don't want to take sides in
that debate.
But you may do it for yourself the way you want it, see above.
 
> Finally- is this list a reasonable place for comments like this, or  
> should I strictly file these on the rails project page, or your team  
> to review at your leisure, and not clutter this list with 
> this kind of  
> discussion?

It's absolutely fine to ask for features here. 
At least it guarantees that requests get some attention on the short term.
The tracker database is not really frequently looked into.

There is a reasonable chance that easy to fulfill requests get implemented
quickly 
if you put these up here, or at least you might get some indication if
implementation
is anywhere on the horizon.

But for long-term memory you would do well to enter requests into the
Tracker database,
certainly if you don't get any response within a few days.

Regards,
Erik.