Re: [Rails-devel] Price Protection

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

Yes, that sounds exactly right.

I would suggest to make it a subclass of StockRound,
like ShareSellingRound (emergency selling to buy a train).

Like that other class, you can probably reuse GameStatus for the UI.
In this case only buy actions would be allowed 
(in ShareSellingRound only sell actions are allowed).

That is all governed by what you put into PossibleActions.

Erik.

> -----Original Message-----
> From: rai...@li... 
> [mailto:rai...@li...] On Behalf 
> Of Brett Lentz
> Sent: Friday 12 October 2007 01:26
> To: Development list for Rails: an 18xx game
> Subject: [Rails-devel] Price Protection
> 
> After whittling away at the rest of the 18EU XML, I think I'd like to
> take a stab at implementing Price Protection.
> 
> Judging by the code, it appears that the best way to go about 
> this is to
> implement it as a special Round, then have the StockRound 
> code signal to
> the GameManager whether it needs to initiate a "Price 
> Protection Round".
> 
> This looks like it will allow the GameManager and GameUIManager to
> prompt the user with an appropriate UI and handle the price protection
> processing based on the user's input.
> 
> Do I have that about right?  Is this a good way of implementing Price
> Protection?
> 
> 
>  ---Brett.
> 
> 
> Love is the only game that is not called on account of darkness.
> 		-- M. Hirschfield
> 
> 
> --------------------------------------------------------------
> -----------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and 
> a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>