These editors are in a private package outside of the
org.openide
hierarchy, so module authors should
not attempt to instantiate or otherwise customize them
directly. It is possible that NetBeans may decide to remove some
such editors if that is necessary for some reason; if this happens,
existing module code should not break (as there are no direct
references to the deleted classes), but rather properties of that
type will cease to be conveniently editable by the user (system
options will still be restored from disk correctly, however). If
this happens, the module author will need to provide an appropriate
editor for the module to be fully functional again. For properties
which are critical to a module's operation and must be edited for
basic functionality to work, module authors will likely want to
provide their own editors to begin with.
A few of these editors are for classes in the Open API packages; in such cases, the documentation for the class in question will mention that there is a property editor available. Also, the following Java platform classes currently have special NetBeans property editors which may be used via the default search path:
java.awt.Color
java.awt.Dimension
java.awt.Font
java.awt.Insets
java.awt.Point
java.awt.Rectangle
java.lang.Class
java.lang.String
java.util.Properties
javax.swing.ListModel
javax.swing.table.TableModel
A number of other editors and property editor extensions are
available in the package
org.openide.explorer.propertysheet.editors
,
but these are likely to be deprecated soon; modules are encouraged to
instead rely solely on the default editor search path, and to add needed configuration
parameters
to their
Node.Property
s
or
PropertyDescriptor
s
so as to be accessible from
PropertyEnv
as used by
smart
property editors.