Re: [Rails-devel] Game Options

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

On 8/4/07, John A. Tamplin <ja...@ja...> wrote:
> brett lentz wrote:
> > And right now, that's not possible. If you get as far as setting the
> > optional rules, you can't change your mind and go back to select a
> > different game.
> >
> I'm all for fixing that.  However, it appears you want to go further and
> allow you to set the options before selecting the game, which seems
> backwards and counterintuitive.  What do you do with selected options
> when you change the game?  If you change the game to one that doesn't
> have that same option (or the same value available, such as changing a
> 5-player 18GL to 18FL), what do you do?  Do you remember that option if
> they change the game back?


Perhaps this is where I may not be making myself clear enough.

Here's a step by step of what I'm looking for:

1. Jar is executed, startup window is shown.
2. game.properties is read, we find out what games are available.
3. As UI is built, a default game (1830) is set as selected.
4. We read the Game.xml for the selected game, learn the options, and
save the xml data to a cache for use when the game is started
5. As the user selects different games, we repeat step 4 as necessary.
6. As soon as "Start New Game" is clicked, we take the state of the
UI, and feed those values into the game engine to start whatever game
was selected.



> > With the current design, there are so many basic UI things that simply
> > aren't possible.
> >
> It should be possible to go back and forth until you actually start the
> game.  However, I think there is a clear order of selecting the game
> before selecting the options to play that game with.
>

Sure, the initial loading of the options can happen after a game is
selected. We could also just load all of the options for all of the
games on startup.

Either option is viable and gets us access to the data the startup UI needs.


---Brett