Index: openide-spec-vers.properties
===================================================================
RCS file: /cvs/openide/openide-spec-vers.properties,v
retrieving revision 1.124
diff -r1.124 openide-spec-vers.properties
7c7
< 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
retrieving revision 1.172
diff -r1.172 apichanges.xml
115a116,158
>      <api name="explorer"/>
>      <summary>Removal of org.openide.explorer.propertysheet.InplaceEditor.handleInitialInputEvent</summary>
>      <version major="4" minor="17"/>
>      <date day="3" month="12" year="2003"/>
>      <author login="tboudreau"/>
>      <compatibility addition="yes" />
>      <description>
>      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.
>      </description>
>      <class package="org.openide.explorer.propertysheet" name="InplaceEditor"/>
>      <issue number="37626"/>
>     </change>
> 
>      <change>
>      <api name="explorer"/>
>      <summary>Property panel rewrite, addition of set/getProperty methods and new constructors, deprecation of getPropertyEditor</summary>
>      <version major="4" minor="16"/>
>      <date day="3" month="12" year="2003"/>
>      <author login="tboudreau"/>
>      <compatibility addition="yes" />
>      <description>
>      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.
>      </description>
>      <class package="org.openide.explorer.propertysheet" name="PropertyPanel"/>
>      <issue number="31896"/>
>     </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
retrieving revision 1.40
diff -r1.40 api.html
866a867,872
>         <TR>
>             <TD>suppressCustomEditor</TD>
>             <TD>java.lang.Boolean</TD>
>             <TD>If true, no custom editor button should be shown for this 
>                 property, even if its property editor supports one</TD>
>         </TR>
1056a1063,1069
> <li><code>netbeans.ps.combohack</code>-Forces the combo box editor to use a 
>     heavyweight popup window, used to solve a problem with some window managers.</li>
> <li><code>netbeans.ps.forcetabs</code>-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(&quot;tabName&quot;).</li>
> <li><code>netbeans.ps.nevertabs</code>-Disable use of tabs in the property sheet
>     even if the property set provides a tab name via the above mentioned hint</li>
1060,1073c1073,1090
< <h4><a name="preferences">Use of the Preferences API to store property sheet settings</a></h4>
< <p>The property sheet uses the java Preferences API to persist some trivial
< settings across sessions.  They are:
< <UL>
< <LI><B>showDescriptionArea</B> - A boolean key for whether the last state of the
<    description area was shown or hidden</LI>
< <LI><B>closedSetNames</B> - 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.</LI>
< <LI><B>sortOrder</B> - An Integer key for the sort order (as defined in 
<    <code>org.openide.explorer.propertysheet.PropertySheet</code>) that should
<    be used by default.  </LI>
< </UL>
< </p>
---
> <h3><a name="customps">Customization of PropertyPanel</a></h3>
> <P>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 <code>putClientProperty()</code>.</P>
> 
> <ul>
> <li><code>radioButtonThreshold</code>-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 <code>PropertyEditor.getTabs()</code></li>
> <li><code>suppressCustomEditor</code>-Do not display a custom editor button
>     even if the property's associated property editor supports one</li>
> <li><code>useLabels</code>-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.</li>
> </ul>
1074a1092,1095
> 
> 
> 
> 
Index: arch/arch-openide-propertysheet.xml
===================================================================
RCS file: /cvs/openide/arch/arch-openide-propertysheet.xml,v
retrieving revision 1.15
diff -r1.15 arch-openide-propertysheet.xml
332,333c332,333
< <li><code>netbeans.ps.forceRadioBoolean</code>-Use a radio button editor instead
<     of a checkbox for boolean values</li>
---
> <li><code>netbeans.ps.useCheckbox</code>-Use a checkbox editor instead
>     of the default radio button editor for boolean values</li>
347,351d346
< <li><code>netbeans.ps.combolog</code>-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</li>
<     
386a382,391
> <li><code>PropSheet.selectionBackground</code>-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.</li>
>     
> <li><code>PropSheet.selectionForeground</code>-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.</li>
> 
388a394,396
> 
> <li><code>PropSheet.selectedSetForeground</code>-Foreground color for expandable
>     property sets when selected in the UI</li>
389a398,404
> <li><code>PropSheet.gridColor</code>-Color for the grid of the property sheet
>     table</li>
>     
> <li><code>PropSheet.disabledForeground</code>-Foreground color for disabled 
>     properties.  May or may not be used, depending on the look and feel's
>     implementation.</li>
>         
398,414d412
< <p>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 
< <code>Preferences.userNodeForPackage(PropertySheet.class)</code>.</p>
< <ul>
< <li><code>showDescriptionArea</code>-Boolean, determining whether the description
<     area should be shown by default</li>
<     
< <li><code>closedSetNames</code>-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</li>
<     
< <li><code>sortOrder</code>-Integer matching one of the constants described in
<     <code>org.openide.explorer.propertysheet.PropertySheet</code> to define
<     sort orders</li>
< </ul>
473a472,476
> 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.
663c666
< 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,737c739
< 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.