Community
Participate
Working Groups
Currently the Project Explorer view is using the Tabbed Properties framework for the Properties view. If you single click on a java file in the Project Explorer, the Tabbed Properties version of the Properties view appears. When you double click the regular version of the Properties view appears. This makes things look inconsistent. I am unsure of the proper solution to this bug, potentially the Java editor needs to implement the tabbed properties as well. I would assume that is the problem, since double clicking moves the focus from the Project Explorer to the Java Editor. What are the thoughts on pushing the Tabbed Properties view to more areas in the platform?
Karen, now that's a good question! Good pickup. I'll shop this around a bit before assigning it...;-).
Just to give a little context, I found this because of some other bugs I have been attempting to get fixed. The related bugs are bug 154781 and bug 158607
Note that you can get the same effect by selecting an element in the Project Explorer (tabbed) and in the Package Explorer (non-tabbed). I think that while we might be able to get the JDT folks to adopt the tabbed style it's unlikely we can force everybody to change... I'll take this to see if there's any way I can make the 'default' PropertySheetPage use the same (or similar) tabbed property page.
Eric, was you have guessed, this is a JDT issue since the Package Explorer and the Java editor are not using the tabbed properties view.
Yes, I may have to fall back on trying to get the JDT folks involved if I can't adopt the tabbed version as the general PropertySheetPage implementation. Anthony, how would I over-ride the tab's label. Someone has pointed out that in these cases using "Advanced" (when there's only one tab) is odd. I'd like to change it to either "Info" or perhaps "General". I realize that in cases where there is an actual tab structure that "Advanced" is correct...
(In reply to comment #5) > Anthony, how would I over-ride the tab's label. Someone has pointed out that in > these cases using "Advanced" (when there's only one tab) is odd. I'd like to > change it to either "Info" or perhaps "General". I realize that in cases where > there is an actual tab structure that "Advanced" is correct... The Advanced tab comes from GMF, but is now used in many places: Advanced was originally intended to mirror the "advanced" properties in the "old" table format in the original properties view. In the table, there was a show advanced properties button, that would show "all" the properties. Now with the tabbed properties view, when something is selected, you show a bunch of tabs with interesting UI to modify the properties of the selection. The Advanced tab is shown as a final tab with the raw properties in a table format. This would be "all" the properties, essentially the "old" table format with the virtual advanced button selected. So changing the name "Advanced" in this case will cause confusion with those editors making use of the tabbed properties view properly. In the case where we have one tab and no adoption of the tabbed properties view, we may want to look at implementing Bug 175057
Actually that bug is sort of the inverse of what I'm trying to do...;-), I'm trying to -add- a tab onto the default PS. I'd like to take the 'default' property sheet (i.e. for those folks who don't even know that tabbed properties exist but who provide a PropertySource) that uses the tabbed property 'look'. Once done there would be no way (except 'custom' property page providers) to get a 'non-tabbed' property sheet. Currently the 'Advanced' tab has the implementation I want/need (i.e. a legacy PS inside a tab), just that in this case the label would be confusing.
ok, so you want to reuse the "Advanced" tab concept in another view/editor which provides a PropertySource. Simply take the org.eclipse.ui.navigator.resources plugin.xml and grab the three extensions propertyContributor, propertyTab and propertySection from the ProjectExplorer. Change the ids and change the name in the propertyTab extension to something else.
Beauty, thanks Anthony...
Moving to triage...
Changing to 'enhancement' since this is a cosmetic change only...
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
