See: Description
| Package | Description |
|---|---|
| org.openide.cookies |
Cookies
are a design pattern used to add behaviors to existing data object
and nodes, or to separate implementation from the main object.
|
| org.openide.nodes |
NetBeans uses
nodes
to represent JavaBeans or other property containers, formed into a
hierarchical tree.
|
| org.openide.util.actions |
PropertySupport
received a bunch of static methods (readWrite, readOnly, and
writeOnly to allow easy property creation with Supplier and
Provider functional interfaces.
Sheet.Set set = ...
SomeObject obj = getLookup().lookup(SomeObject.class);
set.put(PropertySupport.readWrite("name", String.class, obj::getName, obj::setName));
set.put(PropertySupport.readOnly("size", Long.class, obj::getSize));
ChildFactory is useful for creating node children lazily on a background thread, and for simplifying working with Children.Keys. One oversight in the original API was providing for notification that the nodes created by the ChildFactory are no longer in use and should clean up any resources.
DestroyableNodesFactory is an abstract class which adds destroyNodes methods to ChildFactory.Detachable.
@BeanInfoSearchPath annotation
Adding @BeanInfoSearchPath annotation
to allow convenient way of registering BeanInfo search path.
@PropertyEditorRegistration and @PropertyEditorSearchPath annotations
Adding @PropertyEditorRegistration and @PropertyEditorSearchPath annotations
to allow convenient way of registering property editors.
ChildFactory.createKeys better supports incremental display
An implementation of ChildFactory.createKeys may now
use List.add a number of times and return true at the
end, while still displaying keys incrementally.
For general overview of the concepts related to nodes and explorers,
together with code samples, see chapter 7,
of NetBeans Platform for Beginners
by Jason Wexbridge and Walter Nyland.
|
|
Read more about the implementation in the answers to architecture questions.