Re: [Rails-devel] Game Options

[Brett L. <wak...@gm...>]

On Fri, 2007-08-03 at 21:09 +0200, Erik Vos wrote:
> 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.
> 


Yep, that's the problem I'm talking about.


> 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.
> 


I do agree that is a simpler way of getting some of the things I want
without needing to rework the initialization code much.

However, doing that would cause a couple of different issues. Adding
more XML files means blurring the definitions of what information goes
into each file, which is a potential headache for managability. Also,
this forces us to create a UI that works around this problem to the
detriment of usability. And finally, it doesn't really solve the
underlying problem, it just means that when we do get around to fixing
this problem, we've got a much larger amount of code that is impacted by
the change.

I think that in this case, it would be much better to work on solving
this problem before it gets any worse.

I'm going to start looking at what it will take to start separating the
game engine from the data loading.


 ---Brett.


Paranoia is simply an optimistic outlook on life.