From: Stefan F. <ste...@we...> - 2011-07-08 07:50:24
|
Brett, so what is your suggestion exactly? Mine was: City (on the map, tokenable) => HexStation Station (on tile only) => Station I understood Erik's to be: City => Stop Station => Station I can live with that, however for me it is now improvement compared to the previous solution. But this still keeps Station. Maybe your a merger of the two: City => HexStop or MapStop Station => Stop or TileStop Stefan On Thursday, July 07, 2011 06:49:53 pm brett lentz wrote: > On Thu, Jul 7, 2011 at 8:59 AM, Erik Vos <eri...@xs...> wrote: > >> A. City vs. HexStation: > > I find myself increasingly using the term "train stop". So, what about > > Stop or TrainStop? Very descriptive, and (as you know) I love short > > type names. Also Stop has no confusing connotations, as City and Station > > have. > > > > Erik. > > +1 from me. I like "Stop" a bit better, too. It maps closer to the > logical function of those features on the hex. > > We can use "City" and "Station" as user-visible tags, if we want, but > to keep the internal data organization sane, I'd like to deprecate > those terms. > > --------------------------------------------------------------------------- > --- All of the data generated in your IT infrastructure is seriously > valuable. Why? It contains a definitive record of application performance, > security threats, fraudulent activity, and more. Splunk takes this data > and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel |