rails-devel — List for discussion of Rails development

[Rails-devel] Alpha8 test - focus UI / sound

[Frederick W. <fre...@go...>]

​Here are some observerations made when giving Alpha8 a quick test on 1856
(new game) and 1889 (load game). I put the focus on the UI and the sound.


The positive:

* Both profile and docking config are perfectly compatible if taken from 1.x

* Loading an old game works (at least mine).

* SoundFX / music triggers seem still to be working (tested about every
trigger), exception see below.

* Right-click to get next tiles works fine.


The issues:

* Map: Prelaid tiles are painted on top of 1856 background map (i12, l15,
n17, f15, m4), same for 1889.

* Map: Hex mouseover does not lead to "can-be-upgraded-to" highlighting in
tiles pane

* Sound: Left clicking on tile to be changed / oriented does not trigger
the sound fx any more. That sound event should probably also apply to the
new right click.

* Lay track: after unselecting hex (by selecting a non permissible hex),
the hex is still with thick red border.

* Lay track: repeatedly pressing left mouse button leads to the next
possible tile if the first tile only had one possible orientation. Is this
by purpose? You could envisage either cycling through all possible tile
lays with the left button or enforce a strict distinction of the left/right
button by never changing the tile when the left is pressed.

* Lay track (1889): company owning D still has to pay the 80 bucks on
non-river mountains (eg, E4).


-- Frederick

[Rails-devel] Test run and comments - Rails 2.0 alpha 8

[John D. G. <jd...@di...>]

I tried a 3-player game of 1835, and got as far as the first turn of Sx.

- Startup seems normal, but there is a new game option, "Ignore reserved
PR shares", with no explanation.  I didn't try it.

- I undid a couple of turns during the Start Round, and discovered that
Undoing actions by clicking on an action in the Game Report window and
then hitting "Play from here" doesn't work any more.  (The cursor goes
forward to the latest completed turn, and the Game Status window confirms
that nothing was undone.)  Moderator -> Forced Undo, though, still works.

- As in earlier alpha versions, the Game Status window does not show who
owns private companies.

- I mostly like the new, smaller buttons displayed when it is time to lay
tiles or tokens.  However, the top legend "Select a hex" doesn't make it
clear what I'm supposed to do.  "Select a hex to lay a tile in" or "Select
a hex to place a token in" would be clearer.

- The logic determining what tile or token lays are legal needs tweaking.
Koln is highlighted on M1's second turn even though M1 does not have the
50M to lay a tile there.  And after BY has placed the NF token, the NF hex
is still highlighted each turn as if BY were allowed to place a second
token there.  In addition, SX is offered the opportunity to lay a token in
Ludwigshafen/Mannheim even though it is not yet green phase (and no token
can legally be placed there until after the BA home station has appeared).

- At the point of this save file, SX has already declined to lay a token
but is being offered the opportunity again -- and the program won't take
no for an answer.  Hitting "Skip" causes a pop-up with the message,
"Action Biff executed NullAction, mode = SKIP, optionalLabel = NULL is not
allowed".  The program is effectively hung, so I am done.

I've included the "18xx.log" debug log as well as the saved game file.

Re: [Rails-devel] Rails 2.0 alpha 8 available

[Stefan F. <ste...@we...>]

The default file download location of Sourceforge is working again.

Thus a single jar for testing alpha 8 is available at:

http://sourceforge.net/projects/rails/files/Rails/2.0/

in addition to webstart:

http://rails.sf.net/webstart/rails.jnlp


-------- Forwarded Message --------
Subject: [Rails-devel] Rails 2.0 alpha 8 available
Date: Wed, 19 Nov 2014 16:13:12 +0100
From: Stefan Frey <ste...@we...>
Reply-To: Development list for Rails: an 18xx game 
<rai...@li...>
To: Development list for Rails: an 18xx game 
<rai...@li...>

Another alpha release for Rails 2.0. This is the autumn edition.

*** New Features

It includes a full rewrite of the tile and token laying UI.
This comes in addition to the full enforcement of tile and token laying
rules.

The following changes should simplify the selection of tiles & tokens:
=> Rotation is possible on the upgrade panel in addition to the map.
=> Selected upgrade is highlighted
=> First possible rotation is automatically selected
=> First upgrade is automatically selected
=> Buttons always stay visible at the top

It allows to select and rotate the upgrade selections via mouse clicks:
=> left click to rotate
=> right click to select next upgrade

I am happy about feedback on both usability and bugs of the new tile and
token laying interface.

*** Remarks

- All automatic test games run.
- Most reported bugs from previous 2.0 Alpha releases are still open.


*** Testing possible via Webstart or Download ***

* Webstart the alpha release:

http://rails.sf.net/webstart/rails.jnlp

* Download the alpha release:

Download the single jar and start it directly (by double-click or
command line "java -jar" command).

### Please use:
http://rails.sf.net/rails-2.0.alpha8.jar

### Does not work currently (due to SourceForge upload problems)
### https://sourceforge.net/projects/rails/files/Rails/2.0/


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel

[Rails-devel] Rails 2.0 alpha 8 available

[Stefan F. <ste...@we...>]

Another alpha release for Rails 2.0. This is the autumn edition.

*** New Features

It includes a full rewrite of the tile and token laying UI.
This comes in addition to the full enforcement of tile and token laying 
rules.

The following changes should simplify the selection of tiles & tokens:
=> Rotation is possible on the upgrade panel in addition to the map.
=> Selected upgrade is highlighted
=> First possible rotation is automatically selected
=> First upgrade is automatically selected
=> Buttons always stay visible at the top

It allows to select and rotate the upgrade selections via mouse clicks:
=> left click to rotate
=> right click to select next upgrade

I am happy about feedback on both usability and bugs of the new tile and 
token laying interface.

*** Remarks

- All automatic test games run.
- Most reported bugs from previous 2.0 Alpha releases are still open.


*** Testing possible via Webstart or Download ***

* Webstart the alpha release:

http://rails.sf.net/webstart/rails.jnlp

* Download the alpha release:

Download the single jar and start it directly (by double-click or
command line "java -jar" command).

### Please use:
http://rails.sf.net/rails-2.0.alpha8.jar

### Does not work currently (due to SourceForge upload problems)
### https://sourceforge.net/projects/rails/files/Rails/2.0/


------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] bug 1880

[<Dr....@t-...>]

Hi Volker,

if i recall correctly the Investor shouldnt have been able to lay a tile, correct ? So thats a procedural bug.

The next bug stems from the current determination if an investor is connected.Currently rails checks if the networks of companies meet at one and the same vertex (station). This of course would be the offshore hex. I'll try to remove the possibility of having offshore hexes included there.

Thanks for reporting,

Martin

-----Original-Nachricht-----
Betreff: [Rails-devel] bug 1880
Datum: Sun, 26 Oct 2014 19:58:51 +0100
Von: "Schnell, Volker" <vol...@ar...>
An: Development list for Rails: an 18xx game <rai...@li...>

Hello,

here is a Bug in Rails 1.8.11.
The JGG starts the communist Phase with buying the first 4-Train.
Next Company is the Investor 6 with no connection to the related company 
HKR.
The Investor lay no tile. Rails now offer to merge the Investor into the 
HKR (money and company).

The rules say, that the investor do nothing. The above question is 
nessesary when the connection is established or at game end.

the save-Files includes before and after  the investor operates and the 
status-file

greetings

Volker

-- 
Volker Schnell
email: vol...@ar...
homepage: home.arcor.de\volker_schnell

[Rails-devel] bug 1880

[Schnell, V. <vol...@ar...>]

Hello,

here is a Bug in Rails 1.8.11.
The JGG starts the communist Phase with buying the first 4-Train.
Next Company is the Investor 6 with no connection to the related company 
HKR.
The Investor lay no tile. Rails now offer to merge the Investor into the 
HKR (money and company).

The rules say, that the investor do nothing. The above question is 
nessesary when the connection is established or at game end.

the save-Files includes before and after  the investor operates and the 
status-file

greetings

Volker

-- 
Volker Schnell
email: vol...@ar...
homepage: home.arcor.de\volker_schnell

Re: [Rails-devel] Next 2.0 alpha release soon

[Michael A. <out...@gm...>]

I unfortunately have had little time to work on it since the last alpha
release, so I have nothing to merge in.

On Wed, Sep 17, 2014 at 5:52 AM, Stefan Frey <ste...@we...> wrote:

> Hi,
> I will do another alpha release soon that has improvements in the
> token/tile UI, especially for those triggered by special powers of
> privates.
>
> Most likely today (end-of-day) or some time tomorrow.
>
> So if anyone wants to merge new features, please do before that time...
>
> Stefan
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

[Rails-devel] Next 2.0 alpha release soon

[Stefan F. <ste...@we...>]

Hi,
I will do another alpha release soon that has improvements in the 
token/tile UI, especially for those triggered by special powers of privates.

Most likely today (end-of-day) or some time tomorrow.

So if anyone wants to merge new features, please do before that time...

Stefan

Re: [Rails-devel] [Rails-users] 1856 diesel route

[Stefan F. <ste...@we...>]

Hi,
thanks for reporting.
Unfortunately I cannot give you a better answer than the following:

Loading your game file with either your current version 1.8.8, or with 
the current 1.8.x release 1.8.11 the bug can be reproduced.
Same is true for 1.7.13. However it is clearly shown in your picture 
that it has been reported. It is only possible to figure with the log 
file that is written in the working directory of rails.

However the most likely reason for that behavior: The tile/token 
redo/undo mechanism has some edge cases that do not work correctly in 
rails 1.x.

If you believe in rails 1.x the calculation is wrong, save a game file 
and load the save file again, if the calculation changes, it was due to 
a redo/undo bug.

In rails 2.0 the undo/redo mechanism is rewritten nearly from scratch 
and should avoid such issues in the future.

Stefan

On 09/15/2014 11:25 AM, Luiz Cláudio Silveira Duarte wrote:
> Hi, folks. I'm currently playing 1856 using Rails 1.8.8. We are at
> endgame, with several diesels running.
>
> THB, the first company running on OR 9.1, has many possibilities for
> its tile. The two attached image files show that Rails shows a longer
> route if a tile is placed on I18 (although it isn't traversed by the
> route). If, however, the new tile is placed on N15, the proposed route
> is shorter. The N15 tile should allow for the longer route, with the
> addition of Welland (N17) to the route.
>
> Or at least so it seems to me. Can one of the developers take a look
> at it? Many thanks.
>
> --
> Semper imitatum, nunquam idem.
>
> Hoc volo, sic jubeo, sit pro ratione voluntas.
>
> Quidquid latine dictum sit, altum viditur.
>
> "People don't quit playing because they grow old. They grow old because
> they quit playing." [segundo G. Stanley Hall]
>
> http://luiz.claudio.nom.br/
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-users mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-users
>

Re: [Rails-devel] Changes to Stockmarket

[Stefan F. <ste...@we...>]

yes, UI support is a different matter. I was mostly discussing the 
underlying core mechanisms.

On 09/11/2014 06:55 AM, Chris Shaffer wrote:
> If I'm not mistaken, the use of linear grid and hex grid are completely
> independent of the graphic display presented to players. The grids are
> the logical underpinnings, but players would see the same stock market
> that appears printed on the board now. Correct?
>
>
> --
> Chris
>
> /Warning! NSA analysts could be reading this email. And because there’s
> hardly any accountability, we have no idea how they may use it. If that
> bothers you, click here to do something about it.
> <https://www.aclu.org/secure/stopnsa>/
>
>
> On Wed, Sep 10, 2014 at 2:56 PM, <com...@ip...
> <mailto:com...@ip...>> wrote:
>
>     For me, the critical things would be "what are players used to?" and
>     "what
>     are the official rules?" Hexgrid may be a more logical or concise
>     layout,
>     but if it doesn't meet either or both of those criteria, it should be an
>     option, not a default. Which would then raise the logical question
>     of whether
>     or not it is worth the effort of creating it as an option.
>
>     Mike Bourke
>
>
>
>     >-- Original Message --
>     >From: brett lentz <bre...@gm... <mailto:bre...@gm...>>
>     >Date: Wed, 10 Sep 2014 15:43:02 -0400
>     >To: an 18xx game <rai...@li...
>     <mailto:rai...@li...>>
>     >Subject: Re: [Rails-devel] Changes to Stockmarket
>     >Reply-To: "Development list for Rails: an 18xx game"
>     >       <rai...@li...
>     <mailto:rai...@li...>>
>     >
>     >
>     >Thanks for the clarification. It looks like we're all in agreement about
>     >the behavior.
>     >
>     >I don't see any reason to bikeshed the implementation details. HexGrid
>     >seems as good as LinearGrid to me for this case.
>
>
>     ------------------------------------------------------------------------------
>     Want excitement?
>     Manually upgrade your production database.
>     When you want reliability, choose Perforce
>     Perforce version control. Predictably reliable.
>     http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>     _______________________________________________
>     Rails-devel mailing list
>     Rai...@li...
>     <mailto:Rai...@li...>
>     https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

Re: [Rails-devel] Changes to Stockmarket

[Chris S. <chr...@gm...>]

If I'm not mistaken, the use of linear grid and hex grid are completely
independent of the graphic display presented to players. The grids are the
logical underpinnings, but players would see the same stock market that
appears printed on the board now. Correct?


--
Chris

*Warning! NSA analysts could be reading this email. And because there's
hardly any accountability, we have no idea how they may use it. If that
bothers you, click here to do something about it.
<https://www.aclu.org/secure/stopnsa>*

On Wed, Sep 10, 2014 at 2:56 PM, <com...@ip...> wrote:

> For me, the critical things would be "what are players used to?" and "what
> are the official rules?" Hexgrid may be a more logical or concise layout,
> but if it doesn't meet either or both of those criteria, it should be an
> option, not a default. Which would then raise the logical question of
> whether
> or not it is worth the effort of creating it as an option.
>
> Mike Bourke
>
>
>
> >-- Original Message --
> >From: brett lentz <bre...@gm...>
> >Date: Wed, 10 Sep 2014 15:43:02 -0400
> >To: an 18xx game <rai...@li...>
> >Subject: Re: [Rails-devel] Changes to Stockmarket
> >Reply-To: "Development list for Rails: an 18xx game"
> >       <rai...@li...>
> >
> >
> >Thanks for the clarification. It looks like we're all in agreement about
> >the behavior.
> >
> >I don't see any reason to bikeshed the implementation details. HexGrid
> >seems as good as LinearGrid to me for this case.
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

Re: [Rails-devel] Changes to Stockmarket

[<com...@ip...>]

For me, the critical things would be "what are players used to?" and "what
are the official rules?" Hexgrid may be a more logical or concise layout,
but if it doesn't meet either or both of those criteria, it should be an
option, not a default. Which would then raise the logical question of whether
or not it is worth the effort of creating it as an option.

Mike Bourke



>-- Original Message --
>From: brett lentz <bre...@gm...>
>Date: Wed, 10 Sep 2014 15:43:02 -0400
>To: an 18xx game <rai...@li...>
>Subject: Re: [Rails-devel] Changes to Stockmarket
>Reply-To: "Development list for Rails: an 18xx game"
>	<rai...@li...>
>
>
>Thanks for the clarification. It looks like we're all in agreement about
>the behavior.
>
>I don't see any reason to bikeshed the implementation details. HexGrid
>seems as good as LinearGrid to me for this case.

Re: [Rails-devel] Changes to Stockmarket

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

Thanks for the clarification. It looks like we're all in agreement about
the behavior.

I don't see any reason to bikeshed the implementation details. HexGrid
seems as good as LinearGrid to me for this case.

---Brett.


---Brett.

On Wed, Sep 10, 2014 at 3:32 PM, Stefan Frey <ste...@we...> wrote:

> Resubmit with correct indentation of the sketch below, if it works this
> time...
>
>
> Brett, Martin and Erik:
> you all make good points. I do not claim that it IS a hexagonal market
> and it IS NOT a rectangular or anything else.
>
> I only wanted to point out, that treating it as hexagonal is a good
> representation and potentially a better one as the alternatives.
>
> A sketch easily shows the equivalence of mine interpretation to that of
> Brett below:
>
>    /-\ /-\ /-\ /-\ /-\
>   | 1 | 3 | 5 | 7 | 9
>    \-/ \-/ \-/ \-/-\-/
>     | 2 | 4 | 6 | 8 |
>      \-/ \-/ \-/ \-/
>
> Actually any hexagonal grid is equivalent to a rectangular one with a
> half square offset: There are six directions from each square (two each
> at the top and bottom, one each left and right) and this is equivalent
> to a hexagon grid.
>
> And as Martin already pointed out by using adapted movements it can also
> be modelled as rectangular grid without any offset.
>
> My mere intention was to point out that the stockmarket of 1860/1862 is
> very similar to the one of 1837/1854 and thus could be treated
> at a variation of an hexagonal market. Even the movement directions of
> 1860/1862 are identical to those of 1837/1854  (selling shares movement
> to lower left, dividend payments to the right).
>
> How the UI displays the market in the end is a completely different matter.
>
> Stefan
>
>
> On 09/10/2014 05:48 PM, brett lentz wrote:
> > Stefan -
> >
> > Your description is not entirely accurate.
> >
> > The market in 1862 is quasi-linear, not hexagonal. It is two rows of
> > values with a half-value offset between the rows.
> >
> > For example:
> >
> > +------------------------+
> >   | 1 | 3 | 5 | 7 | 9 | | |
> >   |-------------------------|
> >   | | 2 | 4 | 6 | 8 | 10 |
> >   +------------------------+
> >
> > Stock values start on the top row. In this example, let's say a
> > company's par value is at 3.
> >
> > When dividends are paid, the value goes "forward" to 5. The value stays
> > in the same row.
> > When revenue is withheld, the value goes "backward" to 1. The value
> > stays in the same row.
> >
> > When shares are sold during the stock round, the value moves in a
> > "zig-zag" fashion between the rows. So, if the market value is at 5, and
> > three shares are sold, the value moves 5->4->3->2, which leaves the
> > stock price ending on a different row. From that value, the stock price
> > will again move "forward" or "back", linearly, during the operating
> round.
> >
> > An additional wrinkle to 1862 is that values have a tiered forward
> > progression. Depending on the value of dividends paid, a stock value may
> > move "forward" between 1 and 4 spaces. So, for example a company with a
> > stock price of 5 may move forward one space if they pay out between
> > 3-10, two spaces if they pay 11-20, three spaces if they pay 21-30, and
> > four spaces for paying 31+.
> >
> > (Note: all of these numbers are completely fictitious, as I don't have
> > my copy of 1862 in front of me.)
> >
> > Ultimately, this is really just a linear stock market with different
> > movement multipliers for different actions. The visual representation is
> > largely separate from the basic math. Rails can represent the 1862
> > market entirely linearly, if we want. A single "forward" movement is
> > simply moving 2 spaces on a one-dimensional market, where a sale would
> > be a movement of -1 space.
> >
> > ---Brett.
> >
> >
> >
> > On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...
> > <mailto:ste...@we...>> wrote:
> >
> >     Follow up with details on 1860/1862 stockmarket:
> >
> >     My understanding of the stockmarket of 1860/1862 is that it
> resembles a
> >     hexagonal stock market with pointy topped hexagons (or East/West
> >     orientation as it is called in Rails for 18xx maps).
> >
> >     It has two rows of hexagons and wraps around at the upper/lower edge.
> >
> >     In the following I refer to the definitions used by
> >     http://www.redblobgames.com/grids/hexagons/.
> >
> >     In axial coordinates we have the following:
> >
> >     * The first coordinate is identical to the column number of each
> row, if
> >     we assign the bankrupt field to the first column.
> >     * The second coordinate is not vertical, but 60 degrees going from
> NW to
> >     SE. It is identical to the row number (0 and 1).
> >
> >     Using this for the 1862 stock market: Bankrupt hex has coordinates
> (0,0)
> >     then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1)
> etc.
> >
> >     * Wrap around at the bottom implies that we jump from a "virtual"
> >     coordinate (x,2) to coordinate (x+1,0)
> >     * Wrap around at the top implies that we jump from a "virtual"
> >     coordinate (x,-1) to coordinate (x-1,1).
> >
> >     Selling shares implies a transition of (-1, +1):
> >
> >     * From 26 (2,0) to 20 (1,1)
> >     * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
> >     * From 14 (1,0) to 7 (0,1)
> >     * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
> >
> >     Paying dividends is simply increasing the first coordinate according
> to
> >     the number of spaces moved.
> >
> >     A more complex version of a hexagonal stockmarket is used in 1854.
> >
> >     Stefan
> >
> >     On 09/08/2014 06:38 PM, Stefan Frey wrote:
> >      > Mike:
> >      > below you find a proposal how to restructure StockMarket. This is
> an
> >      > example how I would like to change other components of Rails in
> the
> >      > longer run.
> >      >
> >      > Please feel free to comment.
> >      >
> >      > I will write a mail on 1862/1860 stock market specifics later.
> >      >
> >      > Stefan
> >      >
> >      > Suggestions for a component structure. Example: Stockmarket
> >      >
> >      > Currently the core parts of logic, data and creation for the
> >     Stockmarket
> >      > is combined in one class: Stockmarket.
> >      >
> >      > A) Separation of Data and Logic
> >      >
> >      > The data parts of Stockmarket should be moved to a separate class
> >     (e.g.
> >      > xxxMarketModel).
> >      > Possible classes depend on the StockMarket:
> >      > e.g. RectangularMarketModel, HexagonalMarketModel,
> LinearMarketModel
> >      >
> >      > The logic part replaces the existing StockMarket class and
> contains
> >      > method called from Rails that operate on the
> >      > StockMarket, e.g. payout, withhold, sharesSold, etc.
> >      >
> >      > Most likely there will be some default Markets, like
> >     RectangularMarket,
> >      > HexagonalMarket or LinearMarket, but more
> >      > specialized are possible.
> >      >
> >      > Customization should be possible in two ways:
> >      >
> >      > i) Internal configuration due to xml settings.
> >      >
> >      > ii) Implementing StrategyInterfaces that adjust part of the
> internal
> >      > working of the default market.
> >      > E.g. there could be a SoldOutStrategy interface, that allows to
> >     change
> >      > how the market behaves if
> >      > shares are sold out after a stock round.
> >      >
> >      > B) Move Creation to a Builder/Factory class (StockMarketFactory)
> >      >
> >      > Creation of the StockMarket is then done by a separate class,
> >     that wires
> >      > together the different classes according
> >      > of the needs of the specific 18xx.
> >      >
> >      > I prefer to use code to wire together Java elements, so no class
> >     names
> >      > should appear in xml files. This allows easier refactoring
> >      > and code optimizations.
> >      >
> >      > C) Roadmap
> >      >
> >      > I offer to create the basic components for 1830 according to the
> >      > structure outlined above. Then other
> >      > stockmarkets can be modelled along these lines.
> >      >
> >      > On 09/07/2014 09:18 AM, Michael Alexander wrote:
> >      >> Yes, it is extremely similar to 1860.  It might be that the only
> >      >> difference is that the one in 1862 is longer at the high end.
> >      >>
> >      >> No hurry on the response, there are plenty of other things to do.
> >      >>
> >      >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
> >     <mailto:ste...@we...>
> >      >> <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
> >      >>
> >      >>      Mike:
> >      >>      I will come up with a more detailed answer later today.
> >      >>      I have not played 1862 yet, however from a short glance, it
> >     seems that
> >      >>      the stock market is similar to the one of 1860.
> >      >>      I would not recommend that path, instead please wait on my
> >     thoughts, if
> >      >>      you do not mind ;-)
> >      >>      Stefan
> >      >>
> >      >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
> >      >>      > And now that I'm looking at the stock market...
> >      >>      >
> >      >>      > I don't think I can use much of the existing Stock Market
> >     class for
> >      >>      > it.  It just won't fit in a rectangle.  I could make a
> >     new "Stock
> >      >>      > Market" class for this one and make the .xml file specify
> >     which one to
> >      >>      > use.  Should I take that direction?
> >      >>      >
> >      >>      > Mike
> >      >>      >
> >      >>      >
> >      >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
> >      >>      > <out...@gm... <mailto:out...@gm...>
> >     <mailto:out...@gm... <mailto:out...@gm...>>
> >      >>      <mailto:out...@gm...
> >     <mailto:out...@gm...> <mailto:out...@gm...
> >     <mailto:out...@gm...>>>>
> >      >>      wrote:
> >      >>      >
> >      >>      >     I've pushed up my changes - I think I did it
> >     correctly, please let
> >      >>      >     me know if I messed something up.
> >      >>      >
> >      >>      >     I have the Parliament Round mostly working.  My next
> >     step is to
> >      >>      >     work on the stock market.
> >      >>      >
> >      >>      >
> >      >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey
> >     <ste...@we... <mailto:ste...@we...>
> >     <mailto:ste...@we... <mailto:ste...@we...>>
> >      >>      >     <mailto:ste...@we...
> >     <mailto:ste...@we...> <mailto:ste...@we...
> >     <mailto:ste...@we...>>>> wrote:
> >      >>      >
> >      >>      >         I will delay for a further day, as I will only
> >     return on
> >      >>      >         Saturday. Change of plans. ;-)
> >      >>      >
> >      >>      >
> >      >>      >
> >      >>      >
> >      >>      >         Michael Alexander <out...@gm...
> >     <mailto:out...@gm...> <mailto:out...@gm...
> >     <mailto:out...@gm...>>
> >      >>       >         <mailto:out...@gm...
> >     <mailto:out...@gm...>
> >      >>      <mailto:out...@gm...
> >     <mailto:out...@gm...>>>>schrieb:
> >      >>      >
> >      >>      >             I unfortunately had something come up.  Don't
> >     wait for me.
> >      >>      >
> >      >>      >
> >      >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
> >      >>      >             Alexander<out...@gm...
> >     <mailto:out...@gm...> <mailto:out...@gm...
> >     <mailto:out...@gm...>>
> >      >>      >             <mailto:out...@gm...
> >     <mailto:out...@gm...> <mailto:out...@gm...
> >     <mailto:out...@gm...>>>> wrote:
> >      >>      >
> >      >>      >                 I can get it to a state where I can do
> >     that tonight.
> >      >>      >                  Thanks for the heads up.
> >      >>      >
> >      >>      >
> >      >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
> >      >>       >                 Frey<ste...@we...
> >     <mailto:ste...@we...>
> >      >>      <mailto:ste...@we... <mailto:ste...@we...>>
> >     <mailto:ste...@we... <mailto:ste...@we...>
> >      >>      <mailto:ste...@we... <mailto:ste...@we...>>>>
> >      >>      >                 wrote:
> >      >>      >
> >      >>      >                     Martin & Alexander:
> >      >>      >                     I have now rewritten a lot of the
> >     tile and token
> >      >>      >                     lay UI code and intend
> >      >>      >                     a new alpha tomorrow end-of-day.
> >      >>      >                     So if you would like to merge some
> >     code into
> >      >>      >                     rails_2_develop, there is
> >      >>      >                     some time left to do so.
> >      >>      >                     Good coding,
> >      >>      >                     Stefan
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Want excitement?
> > Manually upgrade your production database.
> > When you want reliability, choose Perforce
> > Perforce version control. Predictably reliable.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> >
> >
> >
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel
> >
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

Re: [Rails-devel] Changes to Stockmarket

[Martin B. <dr....@t-...>]

Hi Stefan,

question 3: do we, to keep with the original display implement a new
stockmarket display ?

or do we trust the players to understand the switch from hexagonal to
rectangular ?

Regards,
Martin

On 10.09.2014 21:32, Stefan Frey wrote:
> Resubmit with correct indentation of the sketch below, if it works this 
> time...
> 
> 
> Brett, Martin and Erik:
> you all make good points. I do not claim that it IS a hexagonal market 
> and it IS NOT a rectangular or anything else.
> 
> I only wanted to point out, that treating it as hexagonal is a good 
> representation and potentially a better one as the alternatives.
> 
> A sketch easily shows the equivalence of mine interpretation to that of 
> Brett below:
> 
>    /-\ /-\ /-\ /-\ /-\
>   | 1 | 3 | 5 | 7 | 9
>    \-/ \-/ \-/ \-/-\-/
>     | 2 | 4 | 6 | 8 |
>      \-/ \-/ \-/ \-/ 	  	
> 
> Actually any hexagonal grid is equivalent to a rectangular one with a 
> half square offset: There are six directions from each square (two each 
> at the top and bottom, one each left and right) and this is equivalent
> to a hexagon grid.
> 
> And as Martin already pointed out by using adapted movements it can also 
> be modelled as rectangular grid without any offset.
> 
> My mere intention was to point out that the stockmarket of 1860/1862 is 
> very similar to the one of 1837/1854 and thus could be treated
> at a variation of an hexagonal market. Even the movement directions of 
> 1860/1862 are identical to those of 1837/1854  (selling shares movement 
> to lower left, dividend payments to the right).
> 
> How the UI displays the market in the end is a completely different matter.
> 
> Stefan
> 
> 
> On 09/10/2014 05:48 PM, brett lentz wrote:
>> Stefan -
>>
>> Your description is not entirely accurate.
>>
>> The market in 1862 is quasi-linear, not hexagonal. It is two rows of
>> values with a half-value offset between the rows.
>>
>> For example:
>>
>> +------------------------+
>>   | 1 | 3 | 5 | 7 | 9 | | |
>>   |-------------------------|
>>   | | 2 | 4 | 6 | 8 | 10 |
>>   +------------------------+
>>
>> Stock values start on the top row. In this example, let's say a
>> company's par value is at 3.
>>
>> When dividends are paid, the value goes "forward" to 5. The value stays
>> in the same row.
>> When revenue is withheld, the value goes "backward" to 1. The value
>> stays in the same row.
>>
>> When shares are sold during the stock round, the value moves in a
>> "zig-zag" fashion between the rows. So, if the market value is at 5, and
>> three shares are sold, the value moves 5->4->3->2, which leaves the
>> stock price ending on a different row. From that value, the stock price
>> will again move "forward" or "back", linearly, during the operating round.
>>
>> An additional wrinkle to 1862 is that values have a tiered forward
>> progression. Depending on the value of dividends paid, a stock value may
>> move "forward" between 1 and 4 spaces. So, for example a company with a
>> stock price of 5 may move forward one space if they pay out between
>> 3-10, two spaces if they pay 11-20, three spaces if they pay 21-30, and
>> four spaces for paying 31+.
>>
>> (Note: all of these numbers are completely fictitious, as I don't have
>> my copy of 1862 in front of me.)
>>
>> Ultimately, this is really just a linear stock market with different
>> movement multipliers for different actions. The visual representation is
>> largely separate from the basic math. Rails can represent the 1862
>> market entirely linearly, if we want. A single "forward" movement is
>> simply moving 2 spaces on a one-dimensional market, where a sale would
>> be a movement of -1 space.
>>
>> ---Brett.
>>
>>
>>
>> On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...
>> <mailto:ste...@we...>> wrote:
>>
>>     Follow up with details on 1860/1862 stockmarket:
>>
>>     My understanding of the stockmarket of 1860/1862 is that it resembles a
>>     hexagonal stock market with pointy topped hexagons (or East/West
>>     orientation as it is called in Rails for 18xx maps).
>>
>>     It has two rows of hexagons and wraps around at the upper/lower edge.
>>
>>     In the following I refer to the definitions used by
>>     http://www.redblobgames.com/grids/hexagons/.
>>
>>     In axial coordinates we have the following:
>>
>>     * The first coordinate is identical to the column number of each row, if
>>     we assign the bankrupt field to the first column.
>>     * The second coordinate is not vertical, but 60 degrees going from NW to
>>     SE. It is identical to the row number (0 and 1).
>>
>>     Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0)
>>     then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.
>>
>>     * Wrap around at the bottom implies that we jump from a "virtual"
>>     coordinate (x,2) to coordinate (x+1,0)
>>     * Wrap around at the top implies that we jump from a "virtual"
>>     coordinate (x,-1) to coordinate (x-1,1).
>>
>>     Selling shares implies a transition of (-1, +1):
>>
>>     * From 26 (2,0) to 20 (1,1)
>>     * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
>>     * From 14 (1,0) to 7 (0,1)
>>     * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
>>
>>     Paying dividends is simply increasing the first coordinate according to
>>     the number of spaces moved.
>>
>>     A more complex version of a hexagonal stockmarket is used in 1854.
>>
>>     Stefan
>>
>>     On 09/08/2014 06:38 PM, Stefan Frey wrote:
>>      > Mike:
>>      > below you find a proposal how to restructure StockMarket. This is an
>>      > example how I would like to change other components of Rails in the
>>      > longer run.
>>      >
>>      > Please feel free to comment.
>>      >
>>      > I will write a mail on 1862/1860 stock market specifics later.
>>      >
>>      > Stefan
>>      >
>>      > Suggestions for a component structure. Example: Stockmarket
>>      >
>>      > Currently the core parts of logic, data and creation for the
>>     Stockmarket
>>      > is combined in one class: Stockmarket.
>>      >
>>      > A) Separation of Data and Logic
>>      >
>>      > The data parts of Stockmarket should be moved to a separate class
>>     (e.g.
>>      > xxxMarketModel).
>>      > Possible classes depend on the StockMarket:
>>      > e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
>>      >
>>      > The logic part replaces the existing StockMarket class and contains
>>      > method called from Rails that operate on the
>>      > StockMarket, e.g. payout, withhold, sharesSold, etc.
>>      >
>>      > Most likely there will be some default Markets, like
>>     RectangularMarket,
>>      > HexagonalMarket or LinearMarket, but more
>>      > specialized are possible.
>>      >
>>      > Customization should be possible in two ways:
>>      >
>>      > i) Internal configuration due to xml settings.
>>      >
>>      > ii) Implementing StrategyInterfaces that adjust part of the internal
>>      > working of the default market.
>>      > E.g. there could be a SoldOutStrategy interface, that allows to
>>     change
>>      > how the market behaves if
>>      > shares are sold out after a stock round.
>>      >
>>      > B) Move Creation to a Builder/Factory class (StockMarketFactory)
>>      >
>>      > Creation of the StockMarket is then done by a separate class,
>>     that wires
>>      > together the different classes according
>>      > of the needs of the specific 18xx.
>>      >
>>      > I prefer to use code to wire together Java elements, so no class
>>     names
>>      > should appear in xml files. This allows easier refactoring
>>      > and code optimizations.
>>      >
>>      > C) Roadmap
>>      >
>>      > I offer to create the basic components for 1830 according to the
>>      > structure outlined above. Then other
>>      > stockmarkets can be modelled along these lines.
>>      >
>>      > On 09/07/2014 09:18 AM, Michael Alexander wrote:
>>      >> Yes, it is extremely similar to 1860.  It might be that the only
>>      >> difference is that the one in 1862 is longer at the high end.
>>      >>
>>      >> No hurry on the response, there are plenty of other things to do.
>>      >>
>>      >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
>>     <mailto:ste...@we...>
>>      >> <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
>>      >>
>>      >>      Mike:
>>      >>      I will come up with a more detailed answer later today.
>>      >>      I have not played 1862 yet, however from a short glance, it
>>     seems that
>>      >>      the stock market is similar to the one of 1860.
>>      >>      I would not recommend that path, instead please wait on my
>>     thoughts, if
>>      >>      you do not mind ;-)
>>      >>      Stefan
>>      >>
>>      >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
>>      >>      > And now that I'm looking at the stock market...
>>      >>      >
>>      >>      > I don't think I can use much of the existing Stock Market
>>     class for
>>      >>      > it.  It just won't fit in a rectangle.  I could make a
>>     new "Stock
>>      >>      > Market" class for this one and make the .xml file specify
>>     which one to
>>      >>      > use.  Should I take that direction?
>>      >>      >
>>      >>      > Mike
>>      >>      >
>>      >>      >
>>      >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>>      >>      > <out...@gm... <mailto:out...@gm...>
>>     <mailto:out...@gm... <mailto:out...@gm...>>
>>      >>      <mailto:out...@gm...
>>     <mailto:out...@gm...> <mailto:out...@gm...
>>     <mailto:out...@gm...>>>>
>>      >>      wrote:
>>      >>      >
>>      >>      >     I've pushed up my changes - I think I did it
>>     correctly, please let
>>      >>      >     me know if I messed something up.
>>      >>      >
>>      >>      >     I have the Parliament Round mostly working.  My next
>>     step is to
>>      >>      >     work on the stock market.
>>      >>      >
>>      >>      >
>>      >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey
>>     <ste...@we... <mailto:ste...@we...>
>>     <mailto:ste...@we... <mailto:ste...@we...>>
>>      >>      >     <mailto:ste...@we...
>>     <mailto:ste...@we...> <mailto:ste...@we...
>>     <mailto:ste...@we...>>>> wrote:
>>      >>      >
>>      >>      >         I will delay for a further day, as I will only
>>     return on
>>      >>      >         Saturday. Change of plans. ;-)
>>      >>      >
>>      >>      >
>>      >>      >
>>      >>      >
>>      >>      >         Michael Alexander <out...@gm...
>>     <mailto:out...@gm...> <mailto:out...@gm...
>>     <mailto:out...@gm...>>
>>      >>       >         <mailto:out...@gm...
>>     <mailto:out...@gm...>
>>      >>      <mailto:out...@gm...
>>     <mailto:out...@gm...>>>>schrieb:
>>      >>      >
>>      >>      >             I unfortunately had something come up.  Don't
>>     wait for me.
>>      >>      >
>>      >>      >
>>      >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>>      >>      >             Alexander<out...@gm...
>>     <mailto:out...@gm...> <mailto:out...@gm...
>>     <mailto:out...@gm...>>
>>      >>      >             <mailto:out...@gm...
>>     <mailto:out...@gm...> <mailto:out...@gm...
>>     <mailto:out...@gm...>>>> wrote:
>>      >>      >
>>      >>      >                 I can get it to a state where I can do
>>     that tonight.
>>      >>      >                  Thanks for the heads up.
>>      >>      >
>>      >>      >
>>      >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>>      >>       >                 Frey<ste...@we...
>>     <mailto:ste...@we...>
>>      >>      <mailto:ste...@we... <mailto:ste...@we...>>
>>     <mailto:ste...@we... <mailto:ste...@we...>
>>      >>      <mailto:ste...@we... <mailto:ste...@we...>>>>
>>      >>      >                 wrote:
>>      >>      >
>>      >>      >                     Martin & Alexander:
>>      >>      >                     I have now rewritten a lot of the
>>     tile and token
>>      >>      >                     lay UI code and intend
>>      >>      >                     a new alpha tomorrow end-of-day.
>>      >>      >                     So if you would like to merge some
>>     code into
>>      >>      >                     rails_2_develop, there is
>>      >>      >                     some time left to do so.
>>      >>      >                     Good coding,
>>      >>      >                     Stefan
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Want excitement?
>> Manually upgrade your production database.
>> When you want reliability, choose Perforce
>> Perforce version control. Predictably reliable.
>> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>>
>>
>>
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
> 
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
> 
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
> 

Re: [Rails-devel] Changes to Stockmarket

[Stefan F. <ste...@we...>]

Resubmit with correct indentation of the sketch below, if it works this 
time...


Brett, Martin and Erik:
you all make good points. I do not claim that it IS a hexagonal market 
and it IS NOT a rectangular or anything else.

I only wanted to point out, that treating it as hexagonal is a good 
representation and potentially a better one as the alternatives.

A sketch easily shows the equivalence of mine interpretation to that of 
Brett below:

   /-\ /-\ /-\ /-\ /-\
  | 1 | 3 | 5 | 7 | 9
   \-/ \-/ \-/ \-/-\-/
    | 2 | 4 | 6 | 8 |
     \-/ \-/ \-/ \-/ 	  	

Actually any hexagonal grid is equivalent to a rectangular one with a 
half square offset: There are six directions from each square (two each 
at the top and bottom, one each left and right) and this is equivalent
to a hexagon grid.

And as Martin already pointed out by using adapted movements it can also 
be modelled as rectangular grid without any offset.

My mere intention was to point out that the stockmarket of 1860/1862 is 
very similar to the one of 1837/1854 and thus could be treated
at a variation of an hexagonal market. Even the movement directions of 
1860/1862 are identical to those of 1837/1854  (selling shares movement 
to lower left, dividend payments to the right).

How the UI displays the market in the end is a completely different matter.

Stefan


On 09/10/2014 05:48 PM, brett lentz wrote:
> Stefan -
>
> Your description is not entirely accurate.
>
> The market in 1862 is quasi-linear, not hexagonal. It is two rows of
> values with a half-value offset between the rows.
>
> For example:
>
> +------------------------+
>   | 1 | 3 | 5 | 7 | 9 | | |
>   |-------------------------|
>   | | 2 | 4 | 6 | 8 | 10 |
>   +------------------------+
>
> Stock values start on the top row. In this example, let's say a
> company's par value is at 3.
>
> When dividends are paid, the value goes "forward" to 5. The value stays
> in the same row.
> When revenue is withheld, the value goes "backward" to 1. The value
> stays in the same row.
>
> When shares are sold during the stock round, the value moves in a
> "zig-zag" fashion between the rows. So, if the market value is at 5, and
> three shares are sold, the value moves 5->4->3->2, which leaves the
> stock price ending on a different row. From that value, the stock price
> will again move "forward" or "back", linearly, during the operating round.
>
> An additional wrinkle to 1862 is that values have a tiered forward
> progression. Depending on the value of dividends paid, a stock value may
> move "forward" between 1 and 4 spaces. So, for example a company with a
> stock price of 5 may move forward one space if they pay out between
> 3-10, two spaces if they pay 11-20, three spaces if they pay 21-30, and
> four spaces for paying 31+.
>
> (Note: all of these numbers are completely fictitious, as I don't have
> my copy of 1862 in front of me.)
>
> Ultimately, this is really just a linear stock market with different
> movement multipliers for different actions. The visual representation is
> largely separate from the basic math. Rails can represent the 1862
> market entirely linearly, if we want. A single "forward" movement is
> simply moving 2 spaces on a one-dimensional market, where a sale would
> be a movement of -1 space.
>
> ---Brett.
>
>
>
> On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...
> <mailto:ste...@we...>> wrote:
>
>     Follow up with details on 1860/1862 stockmarket:
>
>     My understanding of the stockmarket of 1860/1862 is that it resembles a
>     hexagonal stock market with pointy topped hexagons (or East/West
>     orientation as it is called in Rails for 18xx maps).
>
>     It has two rows of hexagons and wraps around at the upper/lower edge.
>
>     In the following I refer to the definitions used by
>     http://www.redblobgames.com/grids/hexagons/.
>
>     In axial coordinates we have the following:
>
>     * The first coordinate is identical to the column number of each row, if
>     we assign the bankrupt field to the first column.
>     * The second coordinate is not vertical, but 60 degrees going from NW to
>     SE. It is identical to the row number (0 and 1).
>
>     Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0)
>     then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.
>
>     * Wrap around at the bottom implies that we jump from a "virtual"
>     coordinate (x,2) to coordinate (x+1,0)
>     * Wrap around at the top implies that we jump from a "virtual"
>     coordinate (x,-1) to coordinate (x-1,1).
>
>     Selling shares implies a transition of (-1, +1):
>
>     * From 26 (2,0) to 20 (1,1)
>     * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
>     * From 14 (1,0) to 7 (0,1)
>     * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
>
>     Paying dividends is simply increasing the first coordinate according to
>     the number of spaces moved.
>
>     A more complex version of a hexagonal stockmarket is used in 1854.
>
>     Stefan
>
>     On 09/08/2014 06:38 PM, Stefan Frey wrote:
>      > Mike:
>      > below you find a proposal how to restructure StockMarket. This is an
>      > example how I would like to change other components of Rails in the
>      > longer run.
>      >
>      > Please feel free to comment.
>      >
>      > I will write a mail on 1862/1860 stock market specifics later.
>      >
>      > Stefan
>      >
>      > Suggestions for a component structure. Example: Stockmarket
>      >
>      > Currently the core parts of logic, data and creation for the
>     Stockmarket
>      > is combined in one class: Stockmarket.
>      >
>      > A) Separation of Data and Logic
>      >
>      > The data parts of Stockmarket should be moved to a separate class
>     (e.g.
>      > xxxMarketModel).
>      > Possible classes depend on the StockMarket:
>      > e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
>      >
>      > The logic part replaces the existing StockMarket class and contains
>      > method called from Rails that operate on the
>      > StockMarket, e.g. payout, withhold, sharesSold, etc.
>      >
>      > Most likely there will be some default Markets, like
>     RectangularMarket,
>      > HexagonalMarket or LinearMarket, but more
>      > specialized are possible.
>      >
>      > Customization should be possible in two ways:
>      >
>      > i) Internal configuration due to xml settings.
>      >
>      > ii) Implementing StrategyInterfaces that adjust part of the internal
>      > working of the default market.
>      > E.g. there could be a SoldOutStrategy interface, that allows to
>     change
>      > how the market behaves if
>      > shares are sold out after a stock round.
>      >
>      > B) Move Creation to a Builder/Factory class (StockMarketFactory)
>      >
>      > Creation of the StockMarket is then done by a separate class,
>     that wires
>      > together the different classes according
>      > of the needs of the specific 18xx.
>      >
>      > I prefer to use code to wire together Java elements, so no class
>     names
>      > should appear in xml files. This allows easier refactoring
>      > and code optimizations.
>      >
>      > C) Roadmap
>      >
>      > I offer to create the basic components for 1830 according to the
>      > structure outlined above. Then other
>      > stockmarkets can be modelled along these lines.
>      >
>      > On 09/07/2014 09:18 AM, Michael Alexander wrote:
>      >> Yes, it is extremely similar to 1860.  It might be that the only
>      >> difference is that the one in 1862 is longer at the high end.
>      >>
>      >> No hurry on the response, there are plenty of other things to do.
>      >>
>      >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
>     <mailto:ste...@we...>
>      >> <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
>      >>
>      >>      Mike:
>      >>      I will come up with a more detailed answer later today.
>      >>      I have not played 1862 yet, however from a short glance, it
>     seems that
>      >>      the stock market is similar to the one of 1860.
>      >>      I would not recommend that path, instead please wait on my
>     thoughts, if
>      >>      you do not mind ;-)
>      >>      Stefan
>      >>
>      >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
>      >>      > And now that I'm looking at the stock market...
>      >>      >
>      >>      > I don't think I can use much of the existing Stock Market
>     class for
>      >>      > it.  It just won't fit in a rectangle.  I could make a
>     new "Stock
>      >>      > Market" class for this one and make the .xml file specify
>     which one to
>      >>      > use.  Should I take that direction?
>      >>      >
>      >>      > Mike
>      >>      >
>      >>      >
>      >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>      >>      > <out...@gm... <mailto:out...@gm...>
>     <mailto:out...@gm... <mailto:out...@gm...>>
>      >>      <mailto:out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>>>
>      >>      wrote:
>      >>      >
>      >>      >     I've pushed up my changes - I think I did it
>     correctly, please let
>      >>      >     me know if I messed something up.
>      >>      >
>      >>      >     I have the Parliament Round mostly working.  My next
>     step is to
>      >>      >     work on the stock market.
>      >>      >
>      >>      >
>      >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey
>     <ste...@we... <mailto:ste...@we...>
>     <mailto:ste...@we... <mailto:ste...@we...>>
>      >>      >     <mailto:ste...@we...
>     <mailto:ste...@we...> <mailto:ste...@we...
>     <mailto:ste...@we...>>>> wrote:
>      >>      >
>      >>      >         I will delay for a further day, as I will only
>     return on
>      >>      >         Saturday. Change of plans. ;-)
>      >>      >
>      >>      >
>      >>      >
>      >>      >
>      >>      >         Michael Alexander <out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>
>      >>       >         <mailto:out...@gm...
>     <mailto:out...@gm...>
>      >>      <mailto:out...@gm...
>     <mailto:out...@gm...>>>>schrieb:
>      >>      >
>      >>      >             I unfortunately had something come up.  Don't
>     wait for me.
>      >>      >
>      >>      >
>      >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>      >>      >             Alexander<out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>
>      >>      >             <mailto:out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>>> wrote:
>      >>      >
>      >>      >                 I can get it to a state where I can do
>     that tonight.
>      >>      >                  Thanks for the heads up.
>      >>      >
>      >>      >
>      >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>      >>       >                 Frey<ste...@we...
>     <mailto:ste...@we...>
>      >>      <mailto:ste...@we... <mailto:ste...@we...>>
>     <mailto:ste...@we... <mailto:ste...@we...>
>      >>      <mailto:ste...@we... <mailto:ste...@we...>>>>
>      >>      >                 wrote:
>      >>      >
>      >>      >                     Martin & Alexander:
>      >>      >                     I have now rewritten a lot of the
>     tile and token
>      >>      >                     lay UI code and intend
>      >>      >                     a new alpha tomorrow end-of-day.
>      >>      >                     So if you would like to merge some
>     code into
>      >>      >                     rails_2_develop, there is
>      >>      >                     some time left to do so.
>      >>      >                     Good coding,
>      >>      >                     Stefan
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Rails-devel mailing list
Rai...@li...
https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] Changes to Stockmarket

[Stefan F. <ste...@we...>]

Brett, Martin and Erik:
you all make good points. I do not claim that it IS a hexagonal market 
and it IS NOT a rectangular or anything else.

I only wanted to point out, that treating it as hexagonal is a good 
representation and potentially a better one as the alternatives.

A sketch easily shows the equivalence of mine interpretation to that of 
Brett below:

  /-\ /-\ /-\ /-\ /-\
| 1 | 3 | 5 | 7 | 9
  \-/ \-/ \-/ \-/-\-/
   | 2 | 4 | 6 | 8 |
    \-/ \-/ \-/ \-/ 	  	

Actually any hexagonal grid is equivalent to a rectangular one with a 
half square offset: There are six directions from each square (two each 
at the top and bottom, one each left and right) and this is equivalent
to a hexagon grid.

And as Martin already pointed out by using adapted movements it can also 
be modelled as rectangular grid without any offset.

My mere intention was to point out that the stockmarket of 1860/1862 is 
very similar to the one of 1837/1854 and thus could be treated
at a variation of an hexagonal market. Even the movement directions of 
1860/1862 are identical to those of 1837/1854  (selling shares movement 
to lower left, dividend payments to the right).

How the UI displays the market in the end is a completely different matter.

Stefan


On 09/10/2014 05:48 PM, brett lentz wrote:
> Stefan -
>
> Your description is not entirely accurate.
>
> The market in 1862 is quasi-linear, not hexagonal. It is two rows of
> values with a half-value offset between the rows.
>
> For example:
>
> +------------------------+
>   | 1 | 3 | 5 | 7 | 9 | | |
>   |-------------------------|
>   | | 2 | 4 | 6 | 8 | 10 |
>   +------------------------+
>
> Stock values start on the top row. In this example, let's say a
> company's par value is at 3.
>
> When dividends are paid, the value goes "forward" to 5. The value stays
> in the same row.
> When revenue is withheld, the value goes "backward" to 1. The value
> stays in the same row.
>
> When shares are sold during the stock round, the value moves in a
> "zig-zag" fashion between the rows. So, if the market value is at 5, and
> three shares are sold, the value moves 5->4->3->2, which leaves the
> stock price ending on a different row. From that value, the stock price
> will again move "forward" or "back", linearly, during the operating round.
>
> An additional wrinkle to 1862 is that values have a tiered forward
> progression. Depending on the value of dividends paid, a stock value may
> move "forward" between 1 and 4 spaces. So, for example a company with a
> stock price of 5 may move forward one space if they pay out between
> 3-10, two spaces if they pay 11-20, three spaces if they pay 21-30, and
> four spaces for paying 31+.
>
> (Note: all of these numbers are completely fictitious, as I don't have
> my copy of 1862 in front of me.)
>
> Ultimately, this is really just a linear stock market with different
> movement multipliers for different actions. The visual representation is
> largely separate from the basic math. Rails can represent the 1862
> market entirely linearly, if we want. A single "forward" movement is
> simply moving 2 spaces on a one-dimensional market, where a sale would
> be a movement of -1 space.
>
> ---Brett.
>
>
>
> On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...
> <mailto:ste...@we...>> wrote:
>
>     Follow up with details on 1860/1862 stockmarket:
>
>     My understanding of the stockmarket of 1860/1862 is that it resembles a
>     hexagonal stock market with pointy topped hexagons (or East/West
>     orientation as it is called in Rails for 18xx maps).
>
>     It has two rows of hexagons and wraps around at the upper/lower edge.
>
>     In the following I refer to the definitions used by
>     http://www.redblobgames.com/grids/hexagons/.
>
>     In axial coordinates we have the following:
>
>     * The first coordinate is identical to the column number of each row, if
>     we assign the bankrupt field to the first column.
>     * The second coordinate is not vertical, but 60 degrees going from NW to
>     SE. It is identical to the row number (0 and 1).
>
>     Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0)
>     then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.
>
>     * Wrap around at the bottom implies that we jump from a "virtual"
>     coordinate (x,2) to coordinate (x+1,0)
>     * Wrap around at the top implies that we jump from a "virtual"
>     coordinate (x,-1) to coordinate (x-1,1).
>
>     Selling shares implies a transition of (-1, +1):
>
>     * From 26 (2,0) to 20 (1,1)
>     * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
>     * From 14 (1,0) to 7 (0,1)
>     * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
>
>     Paying dividends is simply increasing the first coordinate according to
>     the number of spaces moved.
>
>     A more complex version of a hexagonal stockmarket is used in 1854.
>
>     Stefan
>
>     On 09/08/2014 06:38 PM, Stefan Frey wrote:
>      > Mike:
>      > below you find a proposal how to restructure StockMarket. This is an
>      > example how I would like to change other components of Rails in the
>      > longer run.
>      >
>      > Please feel free to comment.
>      >
>      > I will write a mail on 1862/1860 stock market specifics later.
>      >
>      > Stefan
>      >
>      > Suggestions for a component structure. Example: Stockmarket
>      >
>      > Currently the core parts of logic, data and creation for the
>     Stockmarket
>      > is combined in one class: Stockmarket.
>      >
>      > A) Separation of Data and Logic
>      >
>      > The data parts of Stockmarket should be moved to a separate class
>     (e.g.
>      > xxxMarketModel).
>      > Possible classes depend on the StockMarket:
>      > e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
>      >
>      > The logic part replaces the existing StockMarket class and contains
>      > method called from Rails that operate on the
>      > StockMarket, e.g. payout, withhold, sharesSold, etc.
>      >
>      > Most likely there will be some default Markets, like
>     RectangularMarket,
>      > HexagonalMarket or LinearMarket, but more
>      > specialized are possible.
>      >
>      > Customization should be possible in two ways:
>      >
>      > i) Internal configuration due to xml settings.
>      >
>      > ii) Implementing StrategyInterfaces that adjust part of the internal
>      > working of the default market.
>      > E.g. there could be a SoldOutStrategy interface, that allows to
>     change
>      > how the market behaves if
>      > shares are sold out after a stock round.
>      >
>      > B) Move Creation to a Builder/Factory class (StockMarketFactory)
>      >
>      > Creation of the StockMarket is then done by a separate class,
>     that wires
>      > together the different classes according
>      > of the needs of the specific 18xx.
>      >
>      > I prefer to use code to wire together Java elements, so no class
>     names
>      > should appear in xml files. This allows easier refactoring
>      > and code optimizations.
>      >
>      > C) Roadmap
>      >
>      > I offer to create the basic components for 1830 according to the
>      > structure outlined above. Then other
>      > stockmarkets can be modelled along these lines.
>      >
>      > On 09/07/2014 09:18 AM, Michael Alexander wrote:
>      >> Yes, it is extremely similar to 1860.  It might be that the only
>      >> difference is that the one in 1862 is longer at the high end.
>      >>
>      >> No hurry on the response, there are plenty of other things to do.
>      >>
>      >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
>     <mailto:ste...@we...>
>      >> <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
>      >>
>      >>      Mike:
>      >>      I will come up with a more detailed answer later today.
>      >>      I have not played 1862 yet, however from a short glance, it
>     seems that
>      >>      the stock market is similar to the one of 1860.
>      >>      I would not recommend that path, instead please wait on my
>     thoughts, if
>      >>      you do not mind ;-)
>      >>      Stefan
>      >>
>      >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
>      >>      > And now that I'm looking at the stock market...
>      >>      >
>      >>      > I don't think I can use much of the existing Stock Market
>     class for
>      >>      > it.  It just won't fit in a rectangle.  I could make a
>     new "Stock
>      >>      > Market" class for this one and make the .xml file specify
>     which one to
>      >>      > use.  Should I take that direction?
>      >>      >
>      >>      > Mike
>      >>      >
>      >>      >
>      >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>      >>      > <out...@gm... <mailto:out...@gm...>
>     <mailto:out...@gm... <mailto:out...@gm...>>
>      >>      <mailto:out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>>>
>      >>      wrote:
>      >>      >
>      >>      >     I've pushed up my changes - I think I did it
>     correctly, please let
>      >>      >     me know if I messed something up.
>      >>      >
>      >>      >     I have the Parliament Round mostly working.  My next
>     step is to
>      >>      >     work on the stock market.
>      >>      >
>      >>      >
>      >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey
>     <ste...@we... <mailto:ste...@we...>
>     <mailto:ste...@we... <mailto:ste...@we...>>
>      >>      >     <mailto:ste...@we...
>     <mailto:ste...@we...> <mailto:ste...@we...
>     <mailto:ste...@we...>>>> wrote:
>      >>      >
>      >>      >         I will delay for a further day, as I will only
>     return on
>      >>      >         Saturday. Change of plans. ;-)
>      >>      >
>      >>      >
>      >>      >
>      >>      >
>      >>      >         Michael Alexander <out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>
>      >>       >         <mailto:out...@gm...
>     <mailto:out...@gm...>
>      >>      <mailto:out...@gm...
>     <mailto:out...@gm...>>>>schrieb:
>      >>      >
>      >>      >             I unfortunately had something come up.  Don't
>     wait for me.
>      >>      >
>      >>      >
>      >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>      >>      >             Alexander<out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>
>      >>      >             <mailto:out...@gm...
>     <mailto:out...@gm...> <mailto:out...@gm...
>     <mailto:out...@gm...>>>> wrote:
>      >>      >
>      >>      >                 I can get it to a state where I can do
>     that tonight.
>      >>      >                  Thanks for the heads up.
>      >>      >
>      >>      >
>      >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>      >>       >                 Frey<ste...@we...
>     <mailto:ste...@we...>
>      >>      <mailto:ste...@we... <mailto:ste...@we...>>
>     <mailto:ste...@we... <mailto:ste...@we...>
>      >>      <mailto:ste...@we... <mailto:ste...@we...>>>>
>      >>      >                 wrote:
>      >>      >
>      >>      >                     Martin & Alexander:
>      >>      >                     I have now rewritten a lot of the
>     tile and token
>      >>      >                     lay UI code and intend
>      >>      >                     a new alpha tomorrow end-of-day.
>      >>      >                     So if you would like to merge some
>     code into
>      >>      >                     rails_2_develop, there is
>      >>      >                     some time left to do so.
>      >>      >                     Good coding,
>      >>      >                     Stefan
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

Re: [Rails-devel] Changes to Stockmarket

[Chris S. <chr...@gm...>]

If you represented the 1862 stock market as a single linear track:

Sale = -1 per share
Pay less than value = null
Pay value = +2
Pay double value = +4
Pay triple value = +6
Pay quad value = +8

There are additional wrinkles for ignoring the first share sold by a
non-director in certain ranges, for allowed par values, etc. However, I
basically agree with Brett that it's a linear stock market with a
double-linear graphical presentation.


--
Chris

*Warning! NSA analysts could be reading this email. And because there's
hardly any accountability, we have no idea how they may use it. If that
bothers you, click here to do something about it.
<https://www.aclu.org/secure/stopnsa>*

On Wed, Sep 10, 2014 at 8:48 AM, brett lentz <bre...@gm...> wrote:

> Stefan -
>
> Your description is not entirely accurate.
>
> The market in 1862 is quasi-linear, not hexagonal. It is two rows of
> values with a half-value offset between the rows.
>
> For example:
>
> +------------------------+
>  | 1 | 3 | 5 | 7 | 9 | | |
>  |-------------------------|
>  | | 2 | 4 | 6 | 8 | 10 |
>  +------------------------+
>
> Stock values start on the top row. In this example, let's say a company's
> par value is at 3.
>
> When dividends are paid, the value goes "forward" to 5. The value stays in
> the same row.
> When revenue is withheld, the value goes "backward" to 1. The value stays
> in the same row.
>
> When shares are sold during the stock round, the value moves in a
> "zig-zag" fashion between the rows. So, if the market value is at 5, and
> three shares are sold, the value moves 5->4->3->2, which leaves the stock
> price ending on a different row. From that value, the stock price will
> again move "forward" or "back", linearly, during the operating round.
>
> An additional wrinkle to 1862 is that values have a tiered forward
> progression. Depending on the value of dividends paid, a stock value may
> move "forward" between 1 and 4 spaces. So, for example a company with a
> stock price of 5 may move forward one space if they pay out between 3-10,
> two spaces if they pay 11-20, three spaces if they pay 21-30, and four
> spaces for paying 31+.
>
> (Note: all of these numbers are completely fictitious, as I don't have my
> copy of 1862 in front of me.)
>
> Ultimately, this is really just a linear stock market with different
> movement multipliers for different actions. The visual representation is
> largely separate from the basic math. Rails can represent the 1862 market
> entirely linearly, if we want. A single "forward" movement is simply moving
> 2 spaces on a one-dimensional market, where a sale would be a movement of
> -1 space.
>
> ---Brett.
>
>
>
>
> On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...> wrote:
>
>> Follow up with details on 1860/1862 stockmarket:
>>
>> My understanding of the stockmarket of 1860/1862 is that it resembles a
>> hexagonal stock market with pointy topped hexagons (or East/West
>> orientation as it is called in Rails for 18xx maps).
>>
>> It has two rows of hexagons and wraps around at the upper/lower edge.
>>
>> In the following I refer to the definitions used by
>> http://www.redblobgames.com/grids/hexagons/.
>>
>> In axial coordinates we have the following:
>>
>> * The first coordinate is identical to the column number of each row, if
>> we assign the bankrupt field to the first column.
>> * The second coordinate is not vertical, but 60 degrees going from NW to
>> SE. It is identical to the row number (0 and 1).
>>
>> Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0)
>> then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.
>>
>> * Wrap around at the bottom implies that we jump from a "virtual"
>> coordinate (x,2) to coordinate (x+1,0)
>> * Wrap around at the top implies that we jump from a "virtual"
>> coordinate (x,-1) to coordinate (x-1,1).
>>
>> Selling shares implies a transition of (-1, +1):
>>
>> * From 26 (2,0) to 20 (1,1)
>> * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
>> * From 14 (1,0) to 7 (0,1)
>> * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
>>
>> Paying dividends is simply increasing the first coordinate according to
>> the number of spaces moved.
>>
>> A more complex version of a hexagonal stockmarket is used in 1854.
>>
>> Stefan
>>
>> On 09/08/2014 06:38 PM, Stefan Frey wrote:
>> > Mike:
>> > below you find a proposal how to restructure StockMarket. This is an
>> > example how I would like to change other components of Rails in the
>> > longer run.
>> >
>> > Please feel free to comment.
>> >
>> > I will write a mail on 1862/1860 stock market specifics later.
>> >
>> > Stefan
>> >
>> > Suggestions for a component structure. Example: Stockmarket
>> >
>> > Currently the core parts of logic, data and creation for the Stockmarket
>> > is combined in one class: Stockmarket.
>> >
>> > A) Separation of Data and Logic
>> >
>> > The data parts of Stockmarket should be moved to a separate class (e.g.
>> > xxxMarketModel).
>> > Possible classes depend on the StockMarket:
>> > e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
>> >
>> > The logic part replaces the existing StockMarket class and contains
>> > method called from Rails that operate on the
>> > StockMarket, e.g. payout, withhold, sharesSold, etc.
>> >
>> > Most likely there will be some default Markets, like RectangularMarket,
>> > HexagonalMarket or LinearMarket, but more
>> > specialized are possible.
>> >
>> > Customization should be possible in two ways:
>> >
>> > i) Internal configuration due to xml settings.
>> >
>> > ii) Implementing StrategyInterfaces that adjust part of the internal
>> > working of the default market.
>> > E.g. there could be a SoldOutStrategy interface, that allows to change
>> > how the market behaves if
>> > shares are sold out after a stock round.
>> >
>> > B) Move Creation to a Builder/Factory class (StockMarketFactory)
>> >
>> > Creation of the StockMarket is then done by a separate class, that wires
>> > together the different classes according
>> > of the needs of the specific 18xx.
>> >
>> > I prefer to use code to wire together Java elements, so no class names
>> > should appear in xml files. This allows easier refactoring
>> > and code optimizations.
>> >
>> > C) Roadmap
>> >
>> > I offer to create the basic components for 1830 according to the
>> > structure outlined above. Then other
>> > stockmarkets can be modelled along these lines.
>> >
>> > On 09/07/2014 09:18 AM, Michael Alexander wrote:
>> >> Yes, it is extremely similar to 1860.  It might be that the only
>> >> difference is that the one in 1862 is longer at the high end.
>> >>
>> >> No hurry on the response, there are plenty of other things to do.
>> >>
>> >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
>> >> <mailto:ste...@we...>> wrote:
>> >>
>> >>      Mike:
>> >>      I will come up with a more detailed answer later today.
>> >>      I have not played 1862 yet, however from a short glance, it seems
>> that
>> >>      the stock market is similar to the one of 1860.
>> >>      I would not recommend that path, instead please wait on my
>> thoughts, if
>> >>      you do not mind ;-)
>> >>      Stefan
>> >>
>> >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
>> >>      > And now that I'm looking at the stock market...
>> >>      >
>> >>      > I don't think I can use much of the existing Stock Market class
>> for
>> >>      > it.  It just won't fit in a rectangle.  I could make a new
>> "Stock
>> >>      > Market" class for this one and make the .xml file specify which
>> one to
>> >>      > use.  Should I take that direction?
>> >>      >
>> >>      > Mike
>> >>      >
>> >>      >
>> >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>> >>      > <out...@gm... <mailto:out...@gm...>
>> >>      <mailto:out...@gm... <mailto:out...@gm...
>> >>>
>> >>      wrote:
>> >>      >
>> >>      >     I've pushed up my changes - I think I did it correctly,
>> please let
>> >>      >     me know if I messed something up.
>> >>      >
>> >>      >     I have the Parliament Round mostly working.  My next step
>> is to
>> >>      >     work on the stock market.
>> >>      >
>> >>      >
>> >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey <
>> ste...@we... <mailto:ste...@we...>
>> >>      >     <mailto:ste...@we... <mailto:ste...@we...>>>
>> wrote:
>> >>      >
>> >>      >         I will delay for a further day, as I will only return on
>> >>      >         Saturday. Change of plans. ;-)
>> >>      >
>> >>      >
>> >>      >
>> >>      >
>> >>      >         Michael Alexander <out...@gm... <mailto:
>> out...@gm...>
>> >>       >         <mailto:out...@gm...
>> >>      <mailto:out...@gm...>>>schrieb:
>> >>      >
>> >>      >             I unfortunately had something come up.  Don't wait
>> for me.
>> >>      >
>> >>      >
>> >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>> >>      >             Alexander<out...@gm... <mailto:
>> out...@gm...>
>> >>      >             <mailto:out...@gm... <mailto:
>> out...@gm...>>> wrote:
>> >>      >
>> >>      >                 I can get it to a state where I can do that
>> tonight.
>> >>      >                  Thanks for the heads up.
>> >>      >
>> >>      >
>> >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>> >>       >                 Frey<ste...@we...
>> >>      <mailto:ste...@we...> <mailto:ste...@we...
>> >>      <mailto:ste...@we...>>>
>> >>      >                 wrote:
>> >>      >
>> >>      >                     Martin & Alexander:
>> >>      >                     I have now rewritten a lot of the tile and
>> token
>> >>      >                     lay UI code and intend
>> >>      >                     a new alpha tomorrow end-of-day.
>> >>      >                     So if you would like to merge some code into
>> >>      >                     rails_2_develop, there is
>> >>      >                     some time left to do so.
>> >>      >                     Good coding,
>> >>      >                     Stefan
>>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>

Re: [Rails-devel] Changes to Stockmarket

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

Stefan -

Your description is not entirely accurate.

The market in 1862 is quasi-linear, not hexagonal. It is two rows of values
with a half-value offset between the rows.

For example:

+------------------------+
 | 1 | 3 | 5 | 7 | 9 | | |
 |-------------------------|
 | | 2 | 4 | 6 | 8 | 10 |
 +------------------------+

Stock values start on the top row. In this example, let's say a company's
par value is at 3.

When dividends are paid, the value goes "forward" to 5. The value stays in
the same row.
When revenue is withheld, the value goes "backward" to 1. The value stays
in the same row.

When shares are sold during the stock round, the value moves in a "zig-zag"
fashion between the rows. So, if the market value is at 5, and three shares
are sold, the value moves 5->4->3->2, which leaves the stock price ending
on a different row. From that value, the stock price will again move
"forward" or "back", linearly, during the operating round.

An additional wrinkle to 1862 is that values have a tiered forward
progression. Depending on the value of dividends paid, a stock value may
move "forward" between 1 and 4 spaces. So, for example a company with a
stock price of 5 may move forward one space if they pay out between 3-10,
two spaces if they pay 11-20, three spaces if they pay 21-30, and four
spaces for paying 31+.

(Note: all of these numbers are completely fictitious, as I don't have my
copy of 1862 in front of me.)

Ultimately, this is really just a linear stock market with different
movement multipliers for different actions. The visual representation is
largely separate from the basic math. Rails can represent the 1862 market
entirely linearly, if we want. A single "forward" movement is simply moving
2 spaces on a one-dimensional market, where a sale would be a movement of
-1 space.

---Brett.



On Wed, Sep 10, 2014 at 11:26 AM, Stefan Frey <ste...@we...> wrote:

> Follow up with details on 1860/1862 stockmarket:
>
> My understanding of the stockmarket of 1860/1862 is that it resembles a
> hexagonal stock market with pointy topped hexagons (or East/West
> orientation as it is called in Rails for 18xx maps).
>
> It has two rows of hexagons and wraps around at the upper/lower edge.
>
> In the following I refer to the definitions used by
> http://www.redblobgames.com/grids/hexagons/.
>
> In axial coordinates we have the following:
>
> * The first coordinate is identical to the column number of each row, if
> we assign the bankrupt field to the first column.
> * The second coordinate is not vertical, but 60 degrees going from NW to
> SE. It is identical to the row number (0 and 1).
>
> Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0)
> then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.
>
> * Wrap around at the bottom implies that we jump from a "virtual"
> coordinate (x,2) to coordinate (x+1,0)
> * Wrap around at the top implies that we jump from a "virtual"
> coordinate (x,-1) to coordinate (x-1,1).
>
> Selling shares implies a transition of (-1, +1):
>
> * From 26 (2,0) to 20 (1,1)
> * From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
> * From 14 (1,0) to 7 (0,1)
> * From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)
>
> Paying dividends is simply increasing the first coordinate according to
> the number of spaces moved.
>
> A more complex version of a hexagonal stockmarket is used in 1854.
>
> Stefan
>
> On 09/08/2014 06:38 PM, Stefan Frey wrote:
> > Mike:
> > below you find a proposal how to restructure StockMarket. This is an
> > example how I would like to change other components of Rails in the
> > longer run.
> >
> > Please feel free to comment.
> >
> > I will write a mail on 1862/1860 stock market specifics later.
> >
> > Stefan
> >
> > Suggestions for a component structure. Example: Stockmarket
> >
> > Currently the core parts of logic, data and creation for the Stockmarket
> > is combined in one class: Stockmarket.
> >
> > A) Separation of Data and Logic
> >
> > The data parts of Stockmarket should be moved to a separate class (e.g.
> > xxxMarketModel).
> > Possible classes depend on the StockMarket:
> > e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
> >
> > The logic part replaces the existing StockMarket class and contains
> > method called from Rails that operate on the
> > StockMarket, e.g. payout, withhold, sharesSold, etc.
> >
> > Most likely there will be some default Markets, like RectangularMarket,
> > HexagonalMarket or LinearMarket, but more
> > specialized are possible.
> >
> > Customization should be possible in two ways:
> >
> > i) Internal configuration due to xml settings.
> >
> > ii) Implementing StrategyInterfaces that adjust part of the internal
> > working of the default market.
> > E.g. there could be a SoldOutStrategy interface, that allows to change
> > how the market behaves if
> > shares are sold out after a stock round.
> >
> > B) Move Creation to a Builder/Factory class (StockMarketFactory)
> >
> > Creation of the StockMarket is then done by a separate class, that wires
> > together the different classes according
> > of the needs of the specific 18xx.
> >
> > I prefer to use code to wire together Java elements, so no class names
> > should appear in xml files. This allows easier refactoring
> > and code optimizations.
> >
> > C) Roadmap
> >
> > I offer to create the basic components for 1830 according to the
> > structure outlined above. Then other
> > stockmarkets can be modelled along these lines.
> >
> > On 09/07/2014 09:18 AM, Michael Alexander wrote:
> >> Yes, it is extremely similar to 1860.  It might be that the only
> >> difference is that the one in 1862 is longer at the high end.
> >>
> >> No hurry on the response, there are plenty of other things to do.
> >>
> >> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
> >> <mailto:ste...@we...>> wrote:
> >>
> >>      Mike:
> >>      I will come up with a more detailed answer later today.
> >>      I have not played 1862 yet, however from a short glance, it seems
> that
> >>      the stock market is similar to the one of 1860.
> >>      I would not recommend that path, instead please wait on my
> thoughts, if
> >>      you do not mind ;-)
> >>      Stefan
> >>
> >>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
> >>      > And now that I'm looking at the stock market...
> >>      >
> >>      > I don't think I can use much of the existing Stock Market class
> for
> >>      > it.  It just won't fit in a rectangle.  I could make a new "Stock
> >>      > Market" class for this one and make the .xml file specify which
> one to
> >>      > use.  Should I take that direction?
> >>      >
> >>      > Mike
> >>      >
> >>      >
> >>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
> >>      > <out...@gm... <mailto:out...@gm...>
> >>      <mailto:out...@gm... <mailto:out...@gm...>>>
> >>      wrote:
> >>      >
> >>      >     I've pushed up my changes - I think I did it correctly,
> please let
> >>      >     me know if I messed something up.
> >>      >
> >>      >     I have the Parliament Round mostly working.  My next step is
> to
> >>      >     work on the stock market.
> >>      >
> >>      >
> >>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey <
> ste...@we... <mailto:ste...@we...>
> >>      >     <mailto:ste...@we... <mailto:ste...@we...>>>
> wrote:
> >>      >
> >>      >         I will delay for a further day, as I will only return on
> >>      >         Saturday. Change of plans. ;-)
> >>      >
> >>      >
> >>      >
> >>      >
> >>      >         Michael Alexander <out...@gm... <mailto:
> out...@gm...>
> >>       >         <mailto:out...@gm...
> >>      <mailto:out...@gm...>>>schrieb:
> >>      >
> >>      >             I unfortunately had something come up.  Don't wait
> for me.
> >>      >
> >>      >
> >>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
> >>      >             Alexander<out...@gm... <mailto:
> out...@gm...>
> >>      >             <mailto:out...@gm... <mailto:
> out...@gm...>>> wrote:
> >>      >
> >>      >                 I can get it to a state where I can do that
> tonight.
> >>      >                  Thanks for the heads up.
> >>      >
> >>      >
> >>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
> >>       >                 Frey<ste...@we...
> >>      <mailto:ste...@we...> <mailto:ste...@we...
> >>      <mailto:ste...@we...>>>
> >>      >                 wrote:
> >>      >
> >>      >                     Martin & Alexander:
> >>      >                     I have now rewritten a lot of the tile and
> token
> >>      >                     lay UI code and intend
> >>      >                     a new alpha tomorrow end-of-day.
> >>      >                     So if you would like to merge some code into
> >>      >                     rails_2_develop, there is
> >>      >                     some time left to do so.
> >>      >                     Good coding,
> >>      >                     Stefan
>

Re: [Rails-devel] Changes to Stockmarket

[Martin B. <dr....@t-...>]

Am 10.09.2014 17:43, schrieb Erik Vos:
>> A more complex version of a hexagonal stockmarket is used in 1854.
> And 1837
>
> Erik
>

The 1837 could be matched by using different moves to the standard
quadratic Market.

Re: [Rails-devel] Changes to Stockmarket

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

> A more complex version of a hexagonal stockmarket is used in 1854.

And 1837

Erik

Re: [Rails-devel] Changes to Stockmarket

[Stefan F. <ste...@we...>]

Follow up with details on 1860/1862 stockmarket:

My understanding of the stockmarket of 1860/1862 is that it resembles a 
hexagonal stock market with pointy topped hexagons (or East/West 
orientation as it is called in Rails for 18xx maps).

It has two rows of hexagons and wraps around at the upper/lower edge.

In the following I refer to the definitions used by 
http://www.redblobgames.com/grids/hexagons/.

In axial coordinates we have the following:

* The first coordinate is identical to the column number of each row, if 
we assign the bankrupt field to the first column.
* The second coordinate is not vertical, but 60 degrees going from NW to 
SE. It is identical to the row number (0 and 1).

Using this for the 1862 stock market: Bankrupt hex has coordinates (0,0) 
then 7 is (0,1), followed by 14 (1,0), 20 (1,1), 26 (2,0), 31 (2,1) etc.

* Wrap around at the bottom implies that we jump from a "virtual" 
coordinate (x,2) to coordinate (x+1,0)
* Wrap around at the top implies that we jump from a "virtual" 
coordinate (x,-1) to coordinate (x-1,1).

Selling shares implies a transition of (-1, +1):

* From 26 (2,0) to 20 (1,1)
* From 20 (1,1) to virtual (0,2) => wrap around edges => 14 (1,0)
* From 14 (1,0) to 7 (0,1)
* From 7 (0,1) to virtual (-1,2) => wrap => bankrupt (0,0)

Paying dividends is simply increasing the first coordinate according to 
the number of spaces moved.

A more complex version of a hexagonal stockmarket is used in 1854.

Stefan

On 09/08/2014 06:38 PM, Stefan Frey wrote:
> Mike:
> below you find a proposal how to restructure StockMarket. This is an
> example how I would like to change other components of Rails in the
> longer run.
>
> Please feel free to comment.
>
> I will write a mail on 1862/1860 stock market specifics later.
>
> Stefan
>
> Suggestions for a component structure. Example: Stockmarket
>
> Currently the core parts of logic, data and creation for the Stockmarket
> is combined in one class: Stockmarket.
>
> A) Separation of Data and Logic
>
> The data parts of Stockmarket should be moved to a separate class (e.g.
> xxxMarketModel).
> Possible classes depend on the StockMarket:
> e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel
>
> The logic part replaces the existing StockMarket class and contains
> method called from Rails that operate on the
> StockMarket, e.g. payout, withhold, sharesSold, etc.
>
> Most likely there will be some default Markets, like RectangularMarket,
> HexagonalMarket or LinearMarket, but more
> specialized are possible.
>
> Customization should be possible in two ways:
>
> i) Internal configuration due to xml settings.
>
> ii) Implementing StrategyInterfaces that adjust part of the internal
> working of the default market.
> E.g. there could be a SoldOutStrategy interface, that allows to change
> how the market behaves if
> shares are sold out after a stock round.
>
> B) Move Creation to a Builder/Factory class (StockMarketFactory)
>
> Creation of the StockMarket is then done by a separate class, that wires
> together the different classes according
> of the needs of the specific 18xx.
>
> I prefer to use code to wire together Java elements, so no class names
> should appear in xml files. This allows easier refactoring
> and code optimizations.
>
> C) Roadmap
>
> I offer to create the basic components for 1830 according to the
> structure outlined above. Then other
> stockmarkets can be modelled along these lines.
>
> On 09/07/2014 09:18 AM, Michael Alexander wrote:
>> Yes, it is extremely similar to 1860.  It might be that the only
>> difference is that the one in 1862 is longer at the high end.
>>
>> No hurry on the response, there are plenty of other things to do.
>>
>> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
>> <mailto:ste...@we...>> wrote:
>>
>>      Mike:
>>      I will come up with a more detailed answer later today.
>>      I have not played 1862 yet, however from a short glance, it seems that
>>      the stock market is similar to the one of 1860.
>>      I would not recommend that path, instead please wait on my thoughts, if
>>      you do not mind ;-)
>>      Stefan
>>
>>      On 09/07/2014 05:42 AM, Michael Alexander wrote:
>>      > And now that I'm looking at the stock market...
>>      >
>>      > I don't think I can use much of the existing Stock Market class for
>>      > it.  It just won't fit in a rectangle.  I could make a new "Stock
>>      > Market" class for this one and make the .xml file specify which one to
>>      > use.  Should I take that direction?
>>      >
>>      > Mike
>>      >
>>      >
>>      > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>>      > <out...@gm... <mailto:out...@gm...>
>>      <mailto:out...@gm... <mailto:out...@gm...>>>
>>      wrote:
>>      >
>>      >     I've pushed up my changes - I think I did it correctly, please let
>>      >     me know if I messed something up.
>>      >
>>      >     I have the Parliament Round mostly working.  My next step is to
>>      >     work on the stock market.
>>      >
>>      >
>>      >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey <ste...@we... <mailto:ste...@we...>
>>      >     <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
>>      >
>>      >         I will delay for a further day, as I will only return on
>>      >         Saturday. Change of plans. ;-)
>>      >
>>      >
>>      >
>>      >
>>      >         Michael Alexander <out...@gm... <mailto:out...@gm...>
>>       >         <mailto:out...@gm...
>>      <mailto:out...@gm...>>>schrieb:
>>      >
>>      >             I unfortunately had something come up.  Don't wait for me.
>>      >
>>      >
>>      >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>>      >             Alexander<out...@gm... <mailto:out...@gm...>
>>      >             <mailto:out...@gm... <mailto:out...@gm...>>> wrote:
>>      >
>>      >                 I can get it to a state where I can do that tonight.
>>      >                  Thanks for the heads up.
>>      >
>>      >
>>      >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>>       >                 Frey<ste...@we...
>>      <mailto:ste...@we...> <mailto:ste...@we...
>>      <mailto:ste...@we...>>>
>>      >                 wrote:
>>      >
>>      >                     Martin & Alexander:
>>      >                     I have now rewritten a lot of the tile and token
>>      >                     lay UI code and intend
>>      >                     a new alpha tomorrow end-of-day.
>>      >                     So if you would like to merge some code into
>>      >                     rails_2_develop, there is
>>      >                     some time left to do so.
>>      >                     Good coding,
>>      >                     Stefan
>>      >
>>      >                     ------------------------------------------------------------------------------
>>      >                     Slashdot TV.
>>      >                     Video for Nerds.  Stuff that matters.
>>      >http://tv.slashdot.org/
>>      >                     _______________________________________________
>>      >                     Rails-devel mailing list
>>      >Rai...@li...
>>      <mailto:Rai...@li...>
>>       >                     <mailto:Rai...@li...
>>      <mailto:Rai...@li...>>
>>      >https://lists.sourceforge.net/lists/listinfo/rails-devel
>>      >
>>      >
>>      >
>>      >             ------------------------------------------------------------------------------
>>      >             Slashdot TV. Video for Nerds. Stuff that
>>      >             matters.http://tv.slashdot.org/_______________________________________________
>>      >             <http://tv.slashdot.org/_______________________________________________>
>>      >             Rails-devel mailing lis...@li...
>>      <mailto:Rai...@li...>
>>       >             <mailto:Rai...@li...
>>      <mailto:Rai...@li...>>https://lists.sourceforge.net/lists/listinfo/rails-devel
>>      >             <https://lists.sourceforge.net/lists/listinfo/rails-devel>
>>      >
>>      >
>>      >         ------------------------------------------------------------------------------
>>      >         Slashdot TV.
>>      >         Video for Nerds.  Stuff that matters.
>>      >http://tv.slashdot.org/
>>      >         _______________________________________________
>>      >         Rails-devel mailing list
>>      >Rai...@li...
>>      <mailto:Rai...@li...>
>>       >         <mailto:Rai...@li...
>>      <mailto:Rai...@li...>>
>>      >https://lists.sourceforge.net/lists/listinfo/rails-devel
>>      >
>>      >
>>      >
>>      >
>>      >
>>      > ------------------------------------------------------------------------------
>>      > Slashdot TV.
>>      > Video for Nerds.  Stuff that matters.
>>      >http://tv.slashdot.org/
>>      >
>>      >
>>      > _______________________________________________
>>      > Rails-devel mailing list
>>      >Rai...@li...
>>      <mailto:Rai...@li...>
>>      >https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
>>
>>      ------------------------------------------------------------------------------
>>      Slashdot TV.
>>      Video for Nerds.  Stuff that matters.
>>      http://tv.slashdot.org/
>>      _______________________________________________
>>      Rails-devel mailing list
>>      Rai...@li...
>>      <mailto:Rai...@li...>
>>      https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>>
>>
>>
>> _______________________________________________
>> Rails-devel mailing list
>> Rai...@li...
>> https://lists.sourceforge.net/lists/listinfo/rails-devel
>>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

[Rails-devel] 1880 foreign investor connectivity

[Stefan F. <ste...@we...>]

Martin & Mike:
there are answers by both Lonny and Helmut, that solve the issue, how 
the connectivity between foreign investor and public company is defined.

In German:
http://boardgamegeek.com/thread/1195228/knights-ikea-table-game-1-when-youre-big-japan-ton/page/9

In English:
http://boardgamegeek.com/thread/1220819/question-about-connection-condition-joint-network

It is running a virtual D train on a network without any intercepting 
tokens. If that train can run from the token of the foreign investor to 
any token of the public company, the investor and the company are 
considered to be connected.

As I intend to write a routine to check if any train can run a given 
network to allow Rails determine if a company needs to buy a train, you 
can leverage on that upcoming addition.

However I would like to ask the call to the procedure from the core 
engine to the UI, as I prefer to have all calls to the algorithm package 
to come from the UI instead of the core engine. This also avoids calls 
to the algorithm package during reload. Is it reasonable for you to move 
that call to you?

Thanks,
Stefan

Re: [Rails-devel] Changes to Stockmarket (was: Upcoming alpha for 2.0 tomorrow)

[Stefan F. <ste...@we...>]

Mike:
below you find a proposal how to restructure StockMarket. This is an 
example how I would like to change other components of Rails in the 
longer run.

Please feel free to comment.

I will write a mail on 1862/1860 stock market specifics later.

Stefan

Suggestions for a component structure. Example: Stockmarket

Currently the core parts of logic, data and creation for the Stockmarket 
is combined in one class: Stockmarket.

A) Separation of Data and Logic

The data parts of Stockmarket should be moved to a separate class (e.g. 
xxxMarketModel).
Possible classes depend on the StockMarket:
e.g. RectangularMarketModel, HexagonalMarketModel, LinearMarketModel

The logic part replaces the existing StockMarket class and contains 
method called from Rails that operate on the
StockMarket, e.g. payout, withhold, sharesSold, etc.

Most likely there will be some default Markets, like RectangularMarket, 
HexagonalMarket or LinearMarket, but more
specialized are possible.

Customization should be possible in two ways:

i) Internal configuration due to xml settings.

ii) Implementing StrategyInterfaces that adjust part of the internal 
working of the default market.
E.g. there could be a SoldOutStrategy interface, that allows to change 
how the market behaves if
shares are sold out after a stock round.

B) Move Creation to a Builder/Factory class (StockMarketFactory)

Creation of the StockMarket is then done by a separate class, that wires 
together the different classes according
of the needs of the specific 18xx.

I prefer to use code to wire together Java elements, so no class names 
should appear in xml files. This allows easier refactoring
and code optimizations.

C) Roadmap

I offer to create the basic components for 1830 according to the 
structure outlined above. Then other
stockmarkets can be modelled along these lines.

On 09/07/2014 09:18 AM, Michael Alexander wrote:
> Yes, it is extremely similar to 1860.  It might be that the only
> difference is that the one in 1862 is longer at the high end.
>
> No hurry on the response, there are plenty of other things to do.
>
> On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...
> <mailto:ste...@we...>> wrote:
>
>     Mike:
>     I will come up with a more detailed answer later today.
>     I have not played 1862 yet, however from a short glance, it seems that
>     the stock market is similar to the one of 1860.
>     I would not recommend that path, instead please wait on my thoughts, if
>     you do not mind ;-)
>     Stefan
>
>     On 09/07/2014 05:42 AM, Michael Alexander wrote:
>     > And now that I'm looking at the stock market...
>     >
>     > I don't think I can use much of the existing Stock Market class for
>     > it.  It just won't fit in a rectangle.  I could make a new "Stock
>     > Market" class for this one and make the .xml file specify which one to
>     > use.  Should I take that direction?
>     >
>     > Mike
>     >
>     >
>     > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
>     > <out...@gm... <mailto:out...@gm...>
>     <mailto:out...@gm... <mailto:out...@gm...>>>
>     wrote:
>     >
>     >     I've pushed up my changes - I think I did it correctly, please let
>     >     me know if I messed something up.
>     >
>     >     I have the Parliament Round mostly working.  My next step is to
>     >     work on the stock market.
>     >
>     >
>     >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey <ste...@we... <mailto:ste...@we...>
>     >     <mailto:ste...@we... <mailto:ste...@we...>>> wrote:
>     >
>     >         I will delay for a further day, as I will only return on
>     >         Saturday. Change of plans. ;-)
>     >
>     >
>     >
>     >
>     >         Michael Alexander <out...@gm... <mailto:out...@gm...>
>      >         <mailto:out...@gm...
>     <mailto:out...@gm...>>>schrieb:
>     >
>     >             I unfortunately had something come up.  Don't wait for me.
>     >
>     >
>     >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
>     >             Alexander<out...@gm... <mailto:out...@gm...>
>     >             <mailto:out...@gm... <mailto:out...@gm...>>> wrote:
>     >
>     >                 I can get it to a state where I can do that tonight.
>     >                  Thanks for the heads up.
>     >
>     >
>     >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
>      >                 Frey<ste...@we...
>     <mailto:ste...@we...> <mailto:ste...@we...
>     <mailto:ste...@we...>>>
>     >                 wrote:
>     >
>     >                     Martin & Alexander:
>     >                     I have now rewritten a lot of the tile and token
>     >                     lay UI code and intend
>     >                     a new alpha tomorrow end-of-day.
>     >                     So if you would like to merge some code into
>     >                     rails_2_develop, there is
>     >                     some time left to do so.
>     >                     Good coding,
>     >                     Stefan
>     >
>     >                     ------------------------------------------------------------------------------
>     >                     Slashdot TV.
>     >                     Video for Nerds.  Stuff that matters.
>     >http://tv.slashdot.org/
>     >                     _______________________________________________
>     >                     Rails-devel mailing list
>     >Rai...@li...
>     <mailto:Rai...@li...>
>      >                     <mailto:Rai...@li...
>     <mailto:Rai...@li...>>
>     >https://lists.sourceforge.net/lists/listinfo/rails-devel
>     >
>     >
>     >
>     >             ------------------------------------------------------------------------------
>     >             Slashdot TV. Video for Nerds. Stuff that
>     >             matters.http://tv.slashdot.org/_______________________________________________
>     >             <http://tv.slashdot.org/_______________________________________________>
>     >             Rails-devel mailing lis...@li...
>     <mailto:Rai...@li...>
>      >             <mailto:Rai...@li...
>     <mailto:Rai...@li...>>https://lists.sourceforge.net/lists/listinfo/rails-devel
>     >             <https://lists.sourceforge.net/lists/listinfo/rails-devel>
>     >
>     >
>     >         ------------------------------------------------------------------------------
>     >         Slashdot TV.
>     >         Video for Nerds.  Stuff that matters.
>     >http://tv.slashdot.org/
>     >         _______________________________________________
>     >         Rails-devel mailing list
>     >Rai...@li...
>     <mailto:Rai...@li...>
>      >         <mailto:Rai...@li...
>     <mailto:Rai...@li...>>
>     >https://lists.sourceforge.net/lists/listinfo/rails-devel
>     >
>     >
>     >
>     >
>     >
>     > ------------------------------------------------------------------------------
>     > Slashdot TV.
>     > Video for Nerds.  Stuff that matters.
>     >http://tv.slashdot.org/
>     >
>     >
>     > _______________________________________________
>     > Rails-devel mailing list
>     >Rai...@li...
>     <mailto:Rai...@li...>
>     >https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>     ------------------------------------------------------------------------------
>     Slashdot TV.
>     Video for Nerds.  Stuff that matters.
>     http://tv.slashdot.org/
>     _______________________________________________
>     Rails-devel mailing list
>     Rai...@li...
>     <mailto:Rai...@li...>
>     https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>

[Rails-devel] Rails 2.0 alpha 7 available

[Stefan F. <ste...@we...>]

Another alpha release for Rails 2.0. This is the late summer edition.

*** Features

- New Tile laying UI nearly 100% complete.
- Combined Tile and Token laying possible.
- Token laying UI needs some more work.

*** New Games under development

- Integrate current development of 1837 (see separate mail by Martin Brumm)

- First integration of initial development for 1862 (by Michael Alexander)

*** Remarks

- All automatic test games run.
- Most reported bugs from previous 2.0 Alpha releases are still open.


*** Testing possible via Webstart or Download ***

* Webstart the alpha release:

http://rails.sf.net/webstart/rails.jnlp

* Download the alpha release:

Download the single jar and start it directly (by double-click or
command line "java -jar" command).

https://sourceforge.net/projects/rails/files/Rails/2.0/

Re: [Rails-devel] Upcoming alpha for 2.0 tomorrow

[Michael A. <out...@gm...>]

Yes, it is extremely similar to 1860.  It might be that the only difference
is that the one in 1862 is longer at the high end.

No hurry on the response, there are plenty of other things to do.

On Sun, Sep 7, 2014 at 3:09 AM, Stefan Frey <ste...@we...> wrote:

> Mike:
> I will come up with a more detailed answer later today.
> I have not played 1862 yet, however from a short glance, it seems that
> the stock market is similar to the one of 1860.
> I would not recommend that path, instead please wait on my thoughts, if
> you do not mind ;-)
> Stefan
>
> On 09/07/2014 05:42 AM, Michael Alexander wrote:
> > And now that I'm looking at the stock market...
> >
> > I don't think I can use much of the existing Stock Market class for
> > it.  It just won't fit in a rectangle.  I could make a new "Stock
> > Market" class for this one and make the .xml file specify which one to
> > use.  Should I take that direction?
> >
> > Mike
> >
> >
> > On Sat, Sep 6, 2014 at 8:54 PM, Michael Alexander
> > <out...@gm... <mailto:out...@gm...>> wrote:
> >
> >     I've pushed up my changes - I think I did it correctly, please let
> >     me know if I messed something up.
> >
> >     I have the Parliament Round mostly working.  My next step is to
> >     work on the stock market.
> >
> >
> >     On Fri, Sep 5, 2014 at 2:46 AM, Stefan Frey <ste...@we...
> >     <mailto:ste...@we...>> wrote:
> >
> >         I will delay for a further day, as I will only return on
> >         Saturday. Change of plans. ;-)
> >
> >
> >
> >
> >         Michael Alexander <out...@gm...
> >         <mailto:out...@gm...>>schrieb:
> >
> >             I unfortunately had something come up.  Don't wait for me.
> >
> >
> >             On Thu, Sep 4, 2014 at 1:03 PM, Michael
> >             Alexander<out...@gm...
> >             <mailto:out...@gm...>> wrote:
> >
> >                 I can get it to a state where I can do that tonight.
> >                  Thanks for the heads up.
> >
> >
> >                 On Thu, Sep 4, 2014 at 12:56 PM, Stefan
> >                 Frey<ste...@we... <mailto:ste...@we...>>
> >                 wrote:
> >
> >                     Martin & Alexander:
> >                     I have now rewritten a lot of the tile and token
> >                     lay UI code and intend
> >                     a new alpha tomorrow end-of-day.
> >                     So if you would like to merge some code into
> >                     rails_2_develop, there is
> >                     some time left to do so.
> >                     Good coding,
> >                     Stefan
> >
> >
>  ------------------------------------------------------------------------------
> >                     Slashdot TV.
> >                     Video for Nerds.  Stuff that matters.
> >                     http://tv.slashdot.org/
> >                     _______________________________________________
> >                     Rails-devel mailing list
> >                     Rai...@li...
> >                     <mailto:Rai...@li...>
> >
> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >
> >
> >
> >
>  ------------------------------------------------------------------------------
> >             Slashdot TV. Video for Nerds. Stuff that
> >             matters.
> http://tv.slashdot.org/_______________________________________________
> >             <
> http://tv.slashdot.org/_______________________________________________>
> >             Rails-devel mailing list Rai...@li...
> >             <mailto:Rai...@li...>
> https://lists.sourceforge.net/lists/listinfo/rails-devel
> >             <https://lists.sourceforge.net/lists/listinfo/rails-devel>
> >
> >
> >
>  ------------------------------------------------------------------------------
> >         Slashdot TV.
> >         Video for Nerds.  Stuff that matters.
> >         http://tv.slashdot.org/
> >         _______________________________________________
> >         Rails-devel mailing list
> >         Rai...@li...
> >         <mailto:Rai...@li...>
> >         https://lists.sourceforge.net/lists/listinfo/rails-devel
> >
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Slashdot TV.
> > Video for Nerds.  Stuff that matters.
> > http://tv.slashdot.org/
> >
> >
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>