Community
Participate
Working Groups
Sometimes I just want to see what properties a class supports and don't care about all the verbose nonsense Java makes you do in order to create a read/write/bound Java Bean property. It's just amazing how much boilerplate code you have to put into a class in order for it to support all the JavaBean property features--and all of that boilerplate code detracts from being able to easily read a class and understand what it does by simply adding a lot of noise that must be disregarded to the data stream. Although we can't change the Java language to have a more compact component programming model, we can provide ennhancements to the standard Eclipse views to make the existing one easier to deal with. One way to do this might be to be able to click a toggle button in the title bar of the /outline|package|members/ view to filter away all getters, setters, propertychangesupport, etc. (all the "noise"). In their place, abstracted property fields could be displayed along with annotated icons showing read/write/bound indicators to specify what features are available on the specified property. Navigation could be configurable to: - Go to the field - Go to the getter - Go to the setter - Go to the property change support - Pop up a menu with the above choices and allow the developer to choose.
Good suggestion. Time permitted for 2.1
Another nice feature: When the "show only selected source" button is pressed and a property is selected, display any of (user configurable choices): - The field - The getter - The setter - The propertychangesupport I suggest making these a bunch of check boxes on the config screen so that the programmer can see any permutations of the above at once.
*** Bug 36121 has been marked as a duplicate of this bug. ***
Also like this suggestion. Miss the same feature from another major editor, where it would group the getter/setter/variable together into a single item in the outline view if the name of the method and variable matched the standard getter/setter convention. Greatly cuts down on clutter.
*** Bug 80097 has been marked as a duplicate of this bug. ***
If we provide these groups we have to adapt the corresponding refactorings as well. For example renaming a property should rename the getter, setter and the property.
*** Bug 80095 has been marked as a duplicate of this bug. ***
From bug 80095 Intellij IDEA has a feature to group properties with associated field. See the attached picture for an example of the getter/setters grouped with the name field. I marked 80095 as a duplicate of this one since the technical implementation behind it would be the same.
*** Bug 147748 has been marked as a duplicate of this bug. ***
Heh, such a simple feature request and it was filed in 2002! Yet nobody has done anything remotely about it. I mean how much effort does it take to just group getters and setters as properties in the outline view?
Help is always welcome, as simple the features may be :-)
I am willing to contribute if you promise to put it in 3.2 :)
You problably meant 3.3. 3.2 is already frozen.
Of course we would add the feature for 3.3 if we get a high quality patch in time.
I guess you mean 3.2 in your last post. 3.3 is a year away. Enough time to code it yourself ;)
No, I meant what I wrote: 3.3, as said 3.2 is frozen.
