Attachment #12369 for bug #37626

This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

View | Details | Raw Unified | Return to bug 37626
Collapse All | Expand All

Line 7 Link Here

(-)openide-spec-vers.properties (-2 / +1 lines)
7	openide.specification.version=4.15	7	openide.specification.version=4.17
8	--




     <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>
    




        <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>

<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>

<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>






Lines 332-333 Link Here

(-)arch/arch-openide-propertysheet.xml (-30 / +29 lines)
332	<li><code>netbeans.ps.forceRadioBoolean</code>-Use a radio button editor instead	332	<li><code>netbeans.ps.useCheckbox</code>-Use a checkbox editor instead
333	of a checkbox for boolean values</li>	333	of the default radio button editor for boolean values</li>
334	--
Lines 347-351 Link Here
347	<li><code>netbeans.ps.combolog</code>-Enable diagnostic logging of resizings of
348	the combo box editor popup, an attempt to diagnose some (ultimately
349	unreproducable) problems with combo boxes on a pre-release build of KDE
350	on Linux</li>
351
Line 387 Link Here
		382	<li><code>PropSheet.selectionBackground</code>-Background color for selected
		383	properties in the property sheet, overriding the default table selection
		384	color if present. Used to fulfil HIE color requirements on various
		385	platforms.</li>
		386
		387	<li><code>PropSheet.selectionForeground</code>-Foreground color for selected
		388	properties in the property sheet, overriding the default table selection
		389	color if present. Used to fulfil HIE color requirements on various
		390	platforms.</li>
		391
Line 389 Link Here
		394
		395	<li><code>PropSheet.selectedSetForeground</code>-Foreground color for expandable
		396	property sets when selected in the UI</li>
Line 390 Link Here
		398	<li><code>PropSheet.gridColor</code>-Color for the grid of the property sheet
		399	table</li>
		400
		401	<li><code>PropSheet.disabledForeground</code>-Foreground color for disabled
		402	properties. May or may not be used, depending on the look and feel's
		403	implementation.</li>
		404
Lines 398-414 Link Here
398	<p>Additionally, the property sheeet uses the Java Preferences API to store some
399	trivial state information based on the users actions. These are stored in the
400	Preferences context returned by
401	<code>Preferences.userNodeForPackage(PropertySheet.class)</code>.</p>
402	<ul>
403	<li><code>showDescriptionArea</code>-Boolean, determining whether the description
404	area should be shown by default</li>
405
406	<li><code>closedSetNames</code>-A comma-delimited string containing the names
407	of property sets which the user has explicitly closed, and which presumably
408	they would like to see closed in the future on nodes that have similarly
409	named property sets</li>
410
411	<li><code>sortOrder</code>-Integer matching one of the constants described in
412	<code>org.openide.explorer.propertysheet.PropertySheet</code> to define
413	sort orders</li>
414	</ul>
Line 474 Link Here
		472	Refelection is used to try to attach action listeners to the component supplied
		473	by legacy (deprecated) EnhancedPropertyEditor implementations to supply their
		474	own inline editor component. Reflection is used by the deprecated
		475	DefaultPropertyModel to attempt to locate getter and setter methods on a
		476	random bean.
Line 663 Link Here
663	as it paints, by reusing renderers, etc., but by and large it is	666	as it paints, by reusing renderers, etc., and by and large it is
664	--
Lines 736-737 Link Here
736	No. It does use the Java Preferences API to store a handful of trivial	739	No.
737	settings such as a list of closed set names and the last sort mode.
738	--

Return to bug 37626

Line 116 Link Here

(-)api/doc/changes/apichanges.xml (+43 lines)
	116	<api name="explorer"/>
	117	<summary>Removal of org.openide.explorer.propertysheet.InplaceEditor.handleInitialInputEvent</summary>
	118	<version major="4" minor="17"/>
	119	<date day="3" month="12" year="2003"/>
	120	<author login="tboudreau"/>
	121	<compatibility addition="yes" />
	122	<description>
	123	This method was introduced post-3.5, and has proven unnecessary, as the
	124	event may effectively be dispatched to the component using dispatchEvent().
	125	It will instead be the responsibility of the component to determine if
	126	it has just been added to a container and should handle the event in some
	127	special way because of that.
	128	</description>
	129	<class package="org.openide.explorer.propertysheet" name="InplaceEditor"/>
	130	<issue number="37626"/>
	131	</change>
	132
	133	<change>
	134	<api name="explorer"/>
	135	<summary>Property panel rewrite, addition of set/getProperty methods and new constructors, deprecation of getPropertyEditor</summary>
	136	<version major="4" minor="16"/>
	137	<date day="3" month="12" year="2003"/>
	138	<author login="tboudreau"/>
	139	<compatibility addition="yes" />
	140	<description>
	141	As part of the rewrite of the internals of PropertyPanel to use the new
	142	property sheet's infrastructure, users of PropertyPanel are encouraged
	143	to use Node.Property rather than PropertyModel objects to drive their
	144	PropertyPanel instances. To that end, methods and constructors have been
	145	added in order to support using Node.Property objects. The method
	146	getPropertyEditor() has been deprecated, and the property change
	147	PROP_PROPERTY_EDITOR will no longer be fired. As documented, in the case
	148	of custom editors, its function has not changed, but for inline uses,
	149	there is no particular use for holding a reference to the property editor
	150	instance, so for inline uses it is no longer guaranteed to return the
	151	same property editor instance as previously - this is now the sole
	152	responsibility of the Property object. As this method was primarily used
	153	by the old property sheet, this is a low-impact change.
	154	</description>
	155	<class package="org.openide.explorer.propertysheet" name="PropertyPanel"/>
	156	<issue number="31896"/>
	157	</change>
	158

Line 867 Link Here

(-)api/doc/org/openide/explorer/doc-files/api.html (-15 / +35 lines)
		867	<TR>
		868	<TD>suppressCustomEditor</TD>
		869	<TD>java.lang.Boolean</TD>
		870	<TD>If true, no custom editor button should be shown for this
		871	property, even if its property editor supports one</TD>
		872	</TR>
Line 1057 Link Here
		1063	<li><code>netbeans.ps.combohack</code>-Forces the combo box editor to use a
		1064	heavyweight popup window, used to solve a problem with some window managers.</li>
		1065	<li><code>netbeans.ps.forcetabs</code>-Force each property set to be displayed
		1066	in a separate tab (normally this is done only by providing a hint from
		1067	a PropertySet via getValue("tabName").</li>
		1068	<li><code>netbeans.ps.nevertabs</code>-Disable use of tabs in the property sheet
		1069	even if the property set provides a tab name via the above mentioned hint</li>
Lines 1060-1073 Link Here
1060	<h4><a name="preferences">Use of the Preferences API to store property sheet settings</a></h4>	1073	<h3><a name="customps">Customization of PropertyPanel</a></h3>
1061	<p>The property sheet uses the java Preferences API to persist some trivial	1074	<P>The PropertyPanel component is a generic component which will display a
1062	settings across sessions. They are:	1075	property editor for a single property - rather like a single cell of the
1063	<UL>	1076	property sheet. There are a few non-normative client properties which may
1064	<LI><B>showDescriptionArea</B> - A boolean key for whether the last state of the	1077	be set on it to change its behavior, via <code>putClientProperty()</code>.</P>
1065	description area was shown or hidden</LI>	1078
1066	<LI><B>closedSetNames</B> - A string containing a comma delimited list of property sets the user has	1079	<ul>
1067	de-expanded and not later reopened, used to set the default expanded state	1080	<li><code>radioButtonThreshold</code>-Integer - display a set of labelled
1068	of similarly named property sets when displayed in the property sheet.</LI>	1081	radio buttons instead of a combo box if the property editor returns less
1069	<LI><B>sortOrder</B> - An Integer key for the sort order (as defined in	1082	than the specified number of tags from <code>PropertyEditor.getTabs()</code></li>
1070	<code>org.openide.explorer.propertysheet.PropertySheet</code>) that should	1083	<li><code>suppressCustomEditor</code>-Do not display a custom editor button
1071	be used by default. </LI>	1084	even if the property's associated property editor supports one</li>
1072	</UL>	1085	<li><code>useLabels</code>-Use the property's display name as the label portion
1073	</p>	1086	of a checkbox boolean editor, if the property is boolean, so that there
1074	--	1087	is some indication of keyboard focus. If radioButtonThreshold is in use
		1088	and a property panel will display radio buttons, this will also affect
		1089	whether a TitledBorder is used for the group of radio buttons.</li>
		1090	</ul>
Line 1075 Link Here
		1092
		1093
		1094
		1095