Index: openide-spec-vers.properties =================================================================== RCS file: /cvs/openide/openide-spec-vers.properties,v --- openide-spec-vers.properties 1.124 +++ openide-spec-vers.properties @@ -7,1 +7,1 @@ -openide.specification.version=4.15 --- +openide.specification.version=4.17 Index: api/doc/changes/apichanges.xml =================================================================== RCS file: /cvs/openide/api/doc/changes/apichanges.xml,v --- api/doc/changes/apichanges.xml 1.172 +++ api/doc/changes/apichanges.xml @@ -116,0 +116,43 @@ + + Removal of org.openide.explorer.propertysheet.InplaceEditor.handleInitialInputEvent + + + + + + This method was introduced post-3.5, and has proven unnecessary, as the + event may effectively be dispatched to the component using dispatchEvent(). + It will instead be the responsibility of the component to determine if + it has just been added to a container and should handle the event in some + special way because of that. + + + + + + + + Property panel rewrite, addition of set/getProperty methods and new constructors, deprecation of getPropertyEditor + + + + + + As part of the rewrite of the internals of PropertyPanel to use the new + property sheet's infrastructure, users of PropertyPanel are encouraged + to use Node.Property rather than PropertyModel objects to drive their + PropertyPanel instances. To that end, methods and constructors have been + added in order to support using Node.Property objects. The method + getPropertyEditor() has been deprecated, and the property change + PROP_PROPERTY_EDITOR will no longer be fired. As documented, in the case + of custom editors, its function has not changed, but for inline uses, + there is no particular use for holding a reference to the property editor + instance, so for inline uses it is no longer guaranteed to return the + same property editor instance as previously - this is now the sole + responsibility of the Property object. As this method was primarily used + by the old property sheet, this is a low-impact change. + + + + + Index: api/doc/org/openide/explorer/doc-files/api.html =================================================================== RCS file: /cvs/openide/api/doc/org/openide/explorer/doc-files/api.html,v --- api/doc/org/openide/explorer/doc-files/api.html 1.40 +++ api/doc/org/openide/explorer/doc-files/api.html @@ -867,0 +867,6 @@ + + suppressCustomEditor + java.lang.Boolean + If true, no custom editor button should be shown for this + property, even if its property editor supports one + @@ -1057,0 +1063,7 @@ +
  • netbeans.ps.combohack-Forces the combo box editor to use a + heavyweight popup window, used to solve a problem with some window managers.
    • +
  • netbeans.ps.forcetabs-Force each property set to be displayed + in a separate tab (normally this is done only by providing a hint from + a PropertySet via getValue("tabName").
    • +
  • netbeans.ps.nevertabs-Disable use of tabs in the property sheet + even if the property set provides a tab name via the above mentioned hint
    • @@ -1060,14 +1073,18 @@ -

    Use of the Preferences API to store property sheet settings

    -

    The property sheet uses the java Preferences API to persist some trivial -settings across sessions. They are: -

      -
    • showDescriptionArea - A boolean key for whether the last state of the - description area was shown or hidden
      • -
    • closedSetNames - A string containing a comma delimited list of property sets the user has - de-expanded and not later reopened, used to set the default expanded state - of similarly named property sets when displayed in the property sheet.
      • -
    • sortOrder - An Integer key for the sort order (as defined in - org.openide.explorer.propertysheet.PropertySheet) that should - be used by default.
      • -
    -

    --- +

    Customization of PropertyPanel

    +

    The PropertyPanel component is a generic component which will display a +property editor for a single property - rather like a single cell of the +property sheet. There are a few non-normative client properties which may +be set on it to change its behavior, via putClientProperty().

    + +
      +
    • radioButtonThreshold-Integer - display a set of labelled + radio buttons instead of a combo box if the property editor returns less + than the specified number of tags from PropertyEditor.getTabs()
      • +
    • suppressCustomEditor-Do not display a custom editor button + even if the property's associated property editor supports one
      • +
    • useLabels-Use the property's display name as the label portion + of a checkbox boolean editor, if the property is boolean, so that there + is some indication of keyboard focus. If radioButtonThreshold is in use + and a property panel will display radio buttons, this will also affect + whether a TitledBorder is used for the group of radio buttons.
      • +
    @@ -1075,0 +1092,4 @@ + + + + Index: arch/arch-openide-propertysheet.xml =================================================================== RCS file: /cvs/openide/arch/arch-openide-propertysheet.xml,v --- arch/arch-openide-propertysheet.xml 1.15 +++ arch/arch-openide-propertysheet.xml @@ -332,2 +332,2 @@ -
  • netbeans.ps.forceRadioBoolean-Use a radio button editor instead - of a checkbox for boolean values
    • --- +
  • netbeans.ps.useCheckbox-Use a checkbox editor instead + of the default radio button editor for boolean values
    • @@ -347,5 +347,0 @@ -
  • netbeans.ps.combolog-Enable diagnostic logging of resizings of - the combo box editor popup, an attempt to diagnose some (ultimately - unreproducable) problems with combo boxes on a pre-release build of KDE - on Linux
    • - @@ -387,0 +382,10 @@ +
  • PropSheet.selectionBackground-Background color for selected + properties in the property sheet, overriding the default table selection + color if present. Used to fulfil HIE color requirements on various + platforms.
    • + +
  • PropSheet.selectionForeground-Foreground color for selected + properties in the property sheet, overriding the default table selection + color if present. Used to fulfil HIE color requirements on various + platforms.
    • + @@ -389,0 +394,3 @@ + +
  • PropSheet.selectedSetForeground-Foreground color for expandable + property sets when selected in the UI
    • @@ -390,0 +398,7 @@ +
  • PropSheet.gridColor-Color for the grid of the property sheet + table
    • + +
  • PropSheet.disabledForeground-Foreground color for disabled + properties. May or may not be used, depending on the look and feel's + implementation.
    • + @@ -398,17 +413,0 @@ -

    Additionally, the property sheeet uses the Java Preferences API to store some -trivial state information based on the users actions. These are stored in the -Preferences context returned by -Preferences.userNodeForPackage(PropertySheet.class).

    -
      -
    • showDescriptionArea-Boolean, determining whether the description - area should be shown by default
      • - -
    • closedSetNames-A comma-delimited string containing the names - of property sets which the user has explicitly closed, and which presumably - they would like to see closed in the future on nodes that have similarly - named property sets
      • - -
    • sortOrder-Integer matching one of the constants described in - org.openide.explorer.propertysheet.PropertySheet to define - sort orders
      • -
    @@ -474,0 +472,5 @@ +Refelection is used to try to attach action listeners to the component supplied +by legacy (deprecated) EnhancedPropertyEditor implementations to supply their +own inline editor component. Reflection is used by the deprecated +DefaultPropertyModel to attempt to locate getter and setter methods on a +random bean. @@ -663,1 +666,1 @@ -as it paints, by reusing renderers, etc., but by and large it is --- +as it paints, by reusing renderers, etc., and by and large it is @@ -736,2 +739,1 @@ -No. It does use the Java Preferences API to store a handful of trivial -settings such as a list of closed set names and the last sort mode. --- +No.