From: Erik V. <eri...@hc...> - 2007-08-03 19:09:47
|
It just occurs to me, that as things currently work, once the Game.xml of one game has been parsed, there is no way back. The game has been started. Options setting can only postpone finishing initialisation of that one game, but not revert it. To change that, quite some rework may be needed. Of course it can be done, but I can't currently assess what it would take. And that is why I think we should separate the simple game options from the rest of the whole XML. The game options in Game.xml can then be read without firing off the whole irreversible Components parsing. That would make the approach that you favour much easier. Erik. > > > > This would also allow us to add a property to define > the number of > > > > minimum and maximum players, and have the Options() > > dialog dynamically > > > > add or subtract name boxes based on this data. > > > > > > In that case, the game selection should precede player entry. > > > > > > > > > No. Starting a game must not happen in forced steps. This is > > simply not > > an acceptable approach. > > I would say that things that are game-dependent can't be displayed > before a game is selected... > > That refers to min/max # of players, game options, > and other things that you are talking about. > > ---- > > Well, while you are thinking about how the UI should really > look like and > work, > I'll finish the basic version I'm doing now, and then leave it to you. > > Just a warning that the order in which things are presented to > the game engine *is* critical. |