#9 Change to a single window interface

[Curt Cox]

Currently, the Balise user interface is based on
multiple windows. This approach doesn't scale well to
large numbers of windows. Optimally positioning
windows and finding the desired window both become
increasingly cumbersome as the number of windows grows.

FlexDock might be a possible solution, but I don't know
if it is mature enough to be useful.
https://flexdock.dev.java.net/

A single window with some thoughtful use of tabs and
splitters would solve this problem.

[francois guillet]

Logged In: YES
user_id=912357

Something to think about. See also
http://www.vlsolutions.com/en/products/docking/ . But
integrating such a component into a Buoy workframe might
take some time. Maybe for Balise 1.5 or 2.0?

[Curt Cox]

Logged In: YES
user_id=540

This simple approach might be enough:

Of Detachable Root Panes and Desktop Hopping
http://weblogs.java.net/blog/ljnelson/archive/2005/06/of_detachable_r.html

public class DetachableRootPane extends JRootPane
http://weblogs.java.net/blog/ljnelson/archive/code/ellington/DetachableRootPane.java

[francois guillet]

Logged In: YES
user_id=912357

Does the activation behavior introduced in 1.03 help
regarding editing multiple interfaces?

[Curt Cox]

Logged In: YES
user_id=540

I haven't used 1.0.3 much. I used build 06/01/2005 quite a
bit, however. Compared to 1.0.2, it was a small step
backwards on this issue. For some reason, the window that I
wanted to be active was active less often than with 1.0.2.
This would lead to me clicking someplace on the inactive
frame editor, eventually realizing that the window wasn't
active, clicking on the window's title bar to activate it,
then clicking where I originally clicked again.

1.0.3 seems to be more like build 06/01/2005 than 1.0.2.

I'm running these with Java 1.5.0 under Windows XP.