Re: [Rails-devel] Running to and through stations

[brett l. <bre...@gm...>]

Maybe I misunderstood, but I thought Erik was saying, make City and
Station both be "Stop" or "HexStop", just with different parameters.

Their behavior is largely identical, and what differences there are
usually don't really justify a separate class. In most games, A town
or whistle stop is just a city that can't be tokened, has a fixed
value, and, in some games, means the tile is non-upgradeable.

I'm not sure what difference you're referring to by "on the map" and
"on tile only". I wasn't suggesting changing the separation between
Model and View.

---Brett.



On Fri, Jul 8, 2011 at 12:52 AM, Stefan Frey <ste...@we...> wrote:
> 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
>
> ------------------------------------------------------------------------------
> 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
>