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.

Bug 163542 - [67cat] [tools] Change default behavior of names properties in editor
Summary: [67cat] [tools] Change default behavior of names properties in editor
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: Other Other
: P3 blocker with 1 vote (vote)
Assignee: issues@guibuilder
Depends on:
Reported: 2009-04-24 04:29 UTC by esmithbss
Modified: 2009-04-24 11:37 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2009-04-24 04:29:42 UTC
[ BUILD # : 200904210201 ]
[ JDK VERSION : 1.6.* ]

Originally filed as issue

The Swing GUI Editor's Properies panel has 2 separate name fields
that are disconnected by default.  The  default operation in other
IDE's (example: Visual Studio) starts each instance variable with
these two values tied together.

For example, in NetBeans, if you change the Name property on the
first panel, this doesn't change the instance variable name.  This
requires a developer to go to the Code panel to change the variable
name.  This is not apparent, particularly since the property pane
does not appear as a Tabbed pane.

This ENH requests the following changes be made to assist the
developer and make NB more familar to people transiting from other

1) Place a large, non-editable item at the top of the property panel.
 This would use bold text to identify the instance variable and type
of the item.  This would replace the text in the title of the
property panel as the property panel title is not apparent and
appears smaller on some machines.

2) By default, link the two name fields (instance variable name and
bean name) such that:

   a) If the bean name is changed before the instance variable name,
         both values are changed.

   b) If the instance variable name is changed before the bean name,
         both values are changed.

   c) If the instance variable name has been changed,
       and the bean name is subsequently changed,
         then the bean name is changed.

   d) If the bean name is changed and the instance variable name is 
       subsequently changed, then the instance variable name 
          is changed.

3) The Name properties should be treated as special properties and 
  displayed in a prominent fashion.  Either using bold text, or as 
  the first property in the list, or both.
Comment 1 Michel Graciano 2009-04-24 11:37:04 UTC
AFAIK and if I understand correctly, the IDE already do what you want, perhaps partially. BTW, I agree that Name
property must not trigger filed rename refactoring. For many frameworks, Name property for components is important and
need to be different from field name.
I don't know your form files, but take a look at 'Set Component Names' property of your form. It keeps the Name property
and field name linked and the property is updated if field name changes.
Another think that should be looked is that just changed properties has its names in bold in Properties view, what is a
interesting behaviour that I like so much, and I think if Name property could be placed in the top of Properties view,
it would be nice.