Re: [Rails-devel] Splitting up the OR window.

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

> >> A few years ago, someone announced to start working on an Eclipse
> version.
> >> That's the last thing I heard about that (nice) idea.
> >
> > Eclipse version means based on SWT (and potentially JFace)?

Don't know.

> > The main issue with the current approach is that in a few places it
> > contains game logic and is tight closely to the non-UI core classes.
> > This is especially true for tile/token lays and the UI classes for hexes
and
> tiles.
> > Before we add another UI this coupling should be removed, otherwise
> > there will be a code duplication. However I will not work on any of
> > this before the Rails 2.0 has stabilized.
> >
> >
> 
> I think we all agree that this part needs to be refactored, one way or
another.
> A cleaner MVC separation would make working on a lot of things easier.

Absolutely.  The decoupling is far from complete yet.

Please note, that I have always coded from the principle, that the UI would
have direct access to all *static* object properties (a separate UI would
still load the same XML). 
(I know that this is controversial, and will probably be replaced by some
way to push static info to the UI.  But that's not my cup of tea. )
In the meantime, a lot of properties that were once thought to be static
have turned into state variables, so coupling might in fact have been
increased.

Erik.