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

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

On Fri, Dec 2, 2011 at 7:19 AM, Stefan Frey <ste...@we...> wrote:
> Erik: see comments below
>
>> > A more general approach is to add a docking framework, which would allow
>> > user to drag and drop panels as they like.
>> > However from my (limited) knowledge there seems to be not a clear choice
>> > which swing docking library to select if any.
>>
>> 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)?
> However this would imply to drop Swing. A Swing docking framework allows to
> keep existing code.
>
>>
>> > And I am not even sure that I would still choose Swing for a rewrite of
>>
>> the
>>
>> > user interface. I would prefer something from the ajax/gwt/jquery et.al.
>> > world. This would ease migration to allow play on mobile devices and have
>> > the server part of the cloud (e.g. using the google AppEngine).
>>
>> Personally, I'd rather see *additional* user interfaces than a complete
>> replacement.
>>
>
> The wording "Rewrite" intended to imply a new separate UI, that implies that
> it is additional. For this to work
>
> 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.

---Brett.