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.
|Summary:||Enhance PropertySheet to be able to modify properties displaying in subclasses|
|Product:||guibuilder||Reporter:||Tomas Pavek <tpavek>|
|Component:||Code||Assignee:||Tomas Pavek <tpavek>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
|Bug Depends on:||29447, 29466|
Description Tomas Pavek 2001-04-26 17:31:38 UTC
I've got some enhancement suggestion for property sheet. It's useful probably only for Form Editor, but it would be nice if the properties could be visualy marked somehow (e.g. to highlight properties changed by the user). One option would be to make PropertySheet extendable in properties visualization. In the simplest form, it could have some method to be overriden in subclasses to modify the visual componenents (SheetButton, PropertyDisplayer) for individual properties. This method would be called when the sheet tab is created and when the value of property changes. Discussed on nbdev, where also Jesse wrote: Do you just want to boldface some properties? Why not set the display name of the property to e.g. "<html><b>enabled</b>"? Then Swing will paint it bold. Actually the font choice Swing uses to show HTML can be pretty ugly, but as a workaround until Swing's painting improves, the property sheet could look for this specific pattern and manually set the font to bold and display the text normally. Anything unusual would be rendered by Swing however it normally would.
Comment 1 Jan Chalupa 2001-05-06 08:10:25 UTC
Target milestone -> 3.3
Comment 2 Jan Chalupa 2001-11-27 13:02:01 UTC
Target milestone -> 3.3.1.
Comment 3 David Simonek 2002-02-05 15:35:44 UTC
Looks like this will need quite a piece of work. I'd like to wait to 4.0, and desing this change along with other visual changes of prop sheet.
Comment 4 Adam Connor 2002-02-13 14:56:33 UTC
I shouldn't have to change the fonts in a zillion different places to get the display I like. I shouldn't have to change indentation sizes in a bunch of different places unless I want them to all be different. There should be some root where I can say, "use this font at this size in this color unless I tell you otherwise!". Grrr.
Comment 5 _ tboudreau 2003-07-16 19:59:39 UTC
Fixed - property sheet rewrite integrated. Can now either use html or a custom inplace editor.
Comment 6 Tomas Pavek 2003-07-17 14:18:59 UTC
Cannot use custom in-place editor for changing display name of the property. Or yes? Surrounding property display name in <html><b> and </b> works, but if this is the supported way, the html tags should be filtered out when the property display name is used elsewhere, e.g. in custom property editor dialog title. Should I file a separate bug for this?
Comment 7 Tomas Pavek 2003-07-21 08:28:05 UTC
forgot to reopen, see above
Comment 8 Tomas Pavek 2003-07-25 15:42:38 UTC
BTW, is the bold property name the right way for marking properties set to non-default values?
Comment 9 _ tboudreau 2004-05-01 19:44:16 UTC
Reminder, I should be integrating the HTML renderer on Monday, so we can close this.
Comment 10 _ tboudreau 2004-05-03 14:50:51 UTC
Html renderer integrated, non-default properties in bold work. Tomas, passing this issue back to you to do as you wish with.
Comment 11 Tomas Pavek 2004-05-24 15:40:19 UTC
Node.Property now has getHtmlDisplayName() method that is used to highlight changed properties. Closing this as fixed.