[Rails-devel] Separation of ORWindow Dependencies.

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

Unfortunately, I haven't had a lot of time in the last week to finish
working on this.

Currently, all of the underlying methods seem to be working, the only
problem is fixing the many repaint/drawing bugs that have crept in
during this change.

I am going to commit this major change today, despite it not being
quite as seamless a change as I wanted it to be.  If anyone wants to
help squash the repainting bugs before I get to them, they're welcome
to jump on in.

I'm hoping to get some time this weekend to work on finishing off
these changes, if this damned head cold I've got allows me to do
anything.


A quick overview of what's changed:

I've removed all constructor arguments from ORWindow, ORPanel,
UpgradesPanel, and any other children of ORWindow.

I've reduced the visibility of GameUILoader's copy of MapPanel.
There's a suitable get method, but no direct access to mapPanel
anymore.

I've moved a ton of methods upward from sub-Containers into ORWindow.=20
There's still a few methods that I feel are out of place, and have
left comments on some of them, but most of the method placements seem
to fit better now.

The StatusWindow no longer "owns" the ORWindow. The ORWindow obtains
any necessary data from the game model objects rather than from the
StatusWindow.

Where possible, I've left many of the old sections of code commented
out just in case I've pruned too much and something is needed.



Right now, resizing the ORWindow correctly repaints the window.=20
Hopefully, I just need to add some more calls to repaint in the right
spots to get the ORWindow fully working again.


---Brett.