Re: [Rails-devel] Swing Docking Framework for Rails

[Stefan F. <ste...@we...>]

Frederick:
some quick replies and observations. Overall it seems to work without 
critical bugs, for me however it does not improve the handling so far.

* At least on my system (Linux KDE 4, Java OpenJDK/IcedTea 6) it is 
pretty easy to create a layout which is a complete messed up and it is 
nearly impossible to get back into something useful (via the UI and not 
by deleting the configuration file).

* More seriously: After closing the Map/ORWindow via the GameWindow menu 
and recreating it, only parts of the ORWindow get restored: However 
which parts can be recovered changes each time I tried that.

* It would be great if there were some pre-defined sensible layouts 
available to select from, especially if those are game dependent (for 
example taking into account how the map looks like and how many 
companies exist).

* Configuration files in general: There are now three types (my 
rails_config, Erik's rails_ini and Fredericks' DockableLayout/rails_ini) 
of configuration files saved using different mechanisms and file locations.
We should at least consider some consolidation here.

* Configuration and log-files: It would be nice if saving and opening of 
configuration files would be written to 18xx.log, which allows

* Size of the jar-files: In the long-run we should provide resource 
packages (e.g. for maps and libs), so that for updates only fewer files
should be required: The whole setup and installation mechanism is 
something we should have a look at.
However I believe that a size of 11MB is still very reasonable.

Stefan


On 02/04/2012 04:59 PM, Frederick Weld wrote:
> Erik/Stefan:
> based on your replies and my first experiences, I decided not to move
> substantially further with the adoption of the docking framework.
> There are several reasons for that:
> - I've already achieved my main goal of being able to detach panels
> from the OR window.
> - Demand beyond this is currently not clearly existing.
> - Any further adoption of the framework would be invasive and
> longer-term oriented (not being part of master).
>
> This decision means the following (already available in the repository):
>
> (1) docking framework included into master - but disabled by default
>         - option (within section "Window") for enabling dockable panels
> of the OR Window
>         - Anybody can evaluate the docking framework by activating
> option (no patch/branch need)
>
> (2) Only add a few key features in addition to the prototype
>         - the button panel can be detached
>              - e.g., I put it below the upgrade panel in my local layout
>         - the OR Window layout is persisted / restored on a per-game basis
>         - upgrade panel tiles are displayed in the same zoom step as in the map
>              - This wasn't possible before as the upgrade panel's width
> couldn't be adjusted
>
> (3) Refrain from refactoring OR window's panels
>         - supporting the configuration option renders such refactoring
> too cumbersome
>
> (4) Refrain from extending the scope of the docking framework to other
> windows/panels for the time being
>         - wait until there is the "pull" for more (based on others'
> experiences / feedback)
>
>> Erik:
>> [Docking Framework] It would release ORPanel again from its chains, but what other problems would it solve?
>
> Even for one monitor, I could perceive advantages of adopting the
> docking framework: Each round could have its own perspective which
> could be further configured by the user. Think of minimizing /
> reducing the size of the stock market / chart for ORs and the
> map/tracks during SR.
>
> -- Frederick
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel