Re: [Rails-devel] Game Options

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

> > OK, I had missed that point: you want a user allow to skip 
> the game options
> > part.
> > Fair enough.
> > 
> 
> 
> Yes.  They're called "options" because they're optional. Otherwise
> they'd be called "requirements" or "dependencies".  ;-)
 
Hmm, yes, so I guess you'll understand why I have always found "Options"
a somewhat confusing name for that whole class...  :-)
 
> > > This requires two separate UI paths:
> > > 
> > > First: Options() presented -> User hits New Game button 
> -> New game is
> > > started, code just assumes no optional 6 train (i.e. the 
> default value
> > > is used).
> > > 
> > > Second: Options() presented -> User clicks Variants 
> button -> Variants
> > > dialog is presented -> User selects variant options and hits an OK
> > > button -> User is returned to Options() -> User clicks 
> New Game button
> > > -> New Game starts.
> > 
> > OK, although the last to items can be skipped IMO: why not 
> let OK start the
> > game?
> 
> 
> We don't start the game with OK because the user may not be finished
> setting up their game. If I want to select my game options, then enter
> in the players names, that needs to be just as valid as 
> entering player
> names then selecting game options.
> 
> This is why I'd prefer to keep these things all in the same window.
> Changing the dialog (or having an extra dialog) isn't at all necessary
> and causes more problems with the UI than it solves.

OK, I'll try to change it that way one of these days.

First the functionality, then the beautification.

Erik.