- Feb 15 '11 Allow custom painted background in the main IDE window.
There's a new Boolean property NbMainWindow.showCustomBackground
in javax.swing.UIManager
. When the property value is TRUE
then the window system will turn off opacity for most of the main window
components - menu bar, toolbars, status bar, sliding bars and the main
desktop area component. That means that the main window background will
be showing through these components. It can be used to paint some watermark
or logo or gradient on the main window background, especially when using
custom main window implementation, see change id reuse.existing.frame.as.the.main.window
- Nov 30 '10 Register default TopComponent location via annotations
Use TopComponent.Registration,
TopComponent.Description and
TopComponent.OpenActionRegistration
to register default location of a
TopComponent,
some of its properties and action to open it.
- Nov 23 '10 Reuse existing JFrame instance (if any) as IDE's main window.
When window system loads it checks for existing Frames (java.awt.Frame.getFrames()) and
if there is a JFrame whose name is "NbMainWindow" then it is reused as the main window.
Main menu, toolbars and content pane will be put into this existing JFrame.
If there isn't such a JFrame instance then a new empty JFrame is created
and used for the main window - the same way as before this change.
- Jan 14 '10 Annotation to retain the location of non-persistent TopComponents
if the user drags them to another location on the screen.
Added an annotation, org.openide.windows.RetainLocation
which can be applied to TopComponents whose
persistence type is PERSISTENCE_NEVER. There has been a long-term
problem that such components can be defined as singleton components,
and the first time they are opened, they appear in the correct place.
However, on restart or after the first time they are closed, their
persistence information, including the containing Mode, is lost, and
thereafter they open in the editor area.
This patch does not affect the current behavior of such components.
However, if you add this annotation to the component, it will remember
(storage in NbPreferences) the ID of its last known parent mode. A
minor patch to the window system's code for deciding if a Mode should
be persistent causes it to now interpret any Mode containing a
TopComponent annotated with RetainLocation
as being one
it should persist, so that if the user creates a transient Mode by
dragging the window to a new location on screen, the data about that
location is not lost on shutdown.
- Jul 15 '09 New method to retrieve the list of TopComponents opened in a Mode.
Added new a method to WindowManager to retrieve the list of TopComponents
opened in a given Mode. This method does not iterate through all the TopComponents
in the Mode so it prevents already closed TopComponents from being deserialized
from disk.
This table lists all of the module exported APIs
with
defined stability classifications. It is generated
based on answers to questions about the architecture
of the module.
but it is not generally done.