Re: [Rails-devel] Selling shares (was: Further 1835 testing)

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

Actually, I think we can have it both ways. 
We'll have to change the SellShares action completely.  We can as well
create a new SellCertificates action, which works the new way, keeping the
old one for compatibility.
Only SellCertificates will be newly created in Rails, but both are still
accepted (in separate processing methods).
All existing saved files and test cases will only use the old one, though.
So we'll have to build an entire new collection of test cases - but we'll
have to do that anyhow.

Erik

> > The basic idea is that we no longer present a list of sell options to
> > the user, but just a list of certificates that he owns.
> > The UI inserts a checkbox next to each certificate, enabling the user
> > to select the certificates to be sold.
> > The president certificate should then have two (or more) checkboxes to
> > enable whole or partial selling, and to indicate what certificates
> > should be returned if the victim owns both 10% and 20% certificates in
> 1835.
> > (Possibly I'm not the first to suggest such an approach; if so, let
> > credit be where it is due).
> >
> 
> +1 to this.
> 
> 
> > Such a process would radically change the existing information
> > exchange between the UI and the game engine (which will be based upon
> > certificate IDs), and (as said above), old save files become
incompatible.
> >
> > So we'll perhaps have to keep this idea for Rails 2.x.
> >
> 
> It sounds like it's time to focus our efforts on 2.x.
> 
> My recommendation:
> 
> Let's create a new public branch for doing 1.x maintenance work. Any
> bugfixes for the next few 1.x releases can go here and, if applicable, be
> merged or cherry-picked to master.
> 
> This will allow us to use master for 2.x (and beyond).
> 
> > Erik.
> 
> ---Brett.
> 
>
----------------------------------------------------------------------------
--
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity, and more. Splunk takes this data and makes sense of
it. IT
> sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel