1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90
|
flexdock 0.5.1 RELEASE NOTES:
CHANGES FROM 0.5:
Updates:
- The Skin Look and Feel migrated from 1.2.11 to 6.7.
- The JGoodies Looks migrated from 1.3.1 to 2.1.1.
Known Problems:
- FlexDock has some difficulty in supporting third-party L&F
implementations. A 0.5.0 change attempted to resolve this problem, but
caused more trouble than it was worth. That change was reverted, see the
Fixed section.
- The PerspectivesDemo and XMLPerspectivesDemo do not work when launched
from the demo application. These applications are working correctly when
run directly.
Deprecated:
- org.flexdock.view.actions.ViewAction.EMPTY_ACTION field. It is unused
and there are better ways to signify no-op actions.
- org.flexdock.util.RootWindow methods getMaximizationLayer(),
setMaximizationLayer(Integer), getMaximizedLayout(),
setMaximizedLayout(LayoutManager). These methods are unused and are
remnants of 0.2.0 code.
Fixed:
- Updated the build.xml file to produce 1.4 compatible code. The Javadoc,
however, is written for 1.5 as it uses the code tag.
- Fixed a problem with closing maximized dockables, where the window would
not refresh correctly.
- Issue 76. The Titlebar now correctly displays user-set fonts.
- Issue 87. Maximization now workings with the DefaultDockingPort. This
was accomplished by creating a createBorderManager method in
DefaultDockingPort that is called during creation. This method is
designed to be overriden by subclasses. The DefaultDockingPort creates
an EmptyBorder with 0-sized insets.
- Issue 88. There was a bug in DockingPortTracker.findByWindow(Component)
that caused a symptom where maximized dockables would not appear in the
correct port.
- Issue 90. The UIManager check required to support third-party L&Fs was
reverted. In 0.5.0 it gave the message "UIDefaults.getUI() failed:" with
some stack trace is printed to System.err. This was not a bug. This
trace is printed from the underlying Swing L&F management. The flexdock
L&F exensions could possibly exist for some L&Fs, so it was considered
preferrable to check with the UIManager before checking with the flexdock
extension manager (PlafManager). Given the ugliness of the error
messages, this code change was reverted.
- Issue 92. Users can now use JComponent subclassed status bars with the
DockBar.
CHANGES FROM 0.4:
New Features:
- release notes. Hey, this is a new feature.
- flexdock now uses Apache Commons Logging for all internal logging
operations. ACL is included in the flexdock download. The old logging
package exists, but is now deprecated.
- added PerspectiveEvents. These events now fire during various actions
with Perspectives.
- the ability to resize components by double-clicking on the divider.
- the ability to maximize a dockable.
Deprecated:
- the org.flexdock.logging package. Use the Apache Commons Logging instead.
- org.flexdock.util.Utilities.sysTrue(String) method. Use
Boolean.getBoolean(String) instead.
- org.flexdock.docking.adapter.MappingReader class. This is an
implementation detail and should be package-private.
Fixed:
- the dockbar layout when attached to the NORTH side of the frame.
- null appearing in tab text.
- a problem with the application shrinking when a L&F was changed.
- a problem where flexdock would "freeze" when the last view was closed.
- a problem where the docking ratios were not honored.
- a possible memory leak when disposing of root windows.
- a bug when a UI delegate was a member of the installed L&F and not
registered as an add-on component.
Partially fixed:
- JApplet throwing a NullPointerException when floating a dockable. The
NPE is no longer thrown and the dockables can now float; however, there
is no way to place the dockable back into the JApplet.
- Perspective drawing problem when switching between 0 and 1 view
perspectives. Switching between single view perspectives now works and
going from single view to no view also works. Changing from no view to
single view perspectives does not correctly redraw the single view
perspective.
- began the long process to upgrade the JavaDoc on classes. As classes are
touched, the documentation is being style modified and missing comments
are added. Current comments are not yet being checked for validity, but
some that were noticed to be out of date have been updated.
|