Community
Participate
Working Groups
Following the discussion from Bugzilla 239136 As we described back in Eclipse 3.2 in http://www.eclipse.org/articles/Article-Tabbed-Properties/tabbed_properties_view.html: The intent was that we add multiple tabs for a better UI for the properties. The advanced tab was intended to be the "original" table format properties view. The proposal is to add proper tabs for selections in the workbench, especially the project explorer, since the project explorer make use of the tabbed properties view. Currently on the list: - We need to create a proper Resource tab. - Follow up on the contribution for tabs for CVS Bug 164455 .
Just realized I assigned it back to yourself. Was there more you expected to happen?
(In reply to comment #1) > Just realized I assigned it back to yourself. Was there more you expected to > happen? > I think what I need to do is figure out what I want to do here and make a proposal with the platform team.
As this is already an enhancement request with a proposal in progress, may I propose that: It would be great if the new tabbed property sheet was generic, supported PropertySheetEntry as a model, and there were standard section implementations for it just like standard PropertyDescriptors for the table-based PropertySheetViewer; so clients using GEF, RCP etc. which need a more user-friendly representation of the generic property sheet could use it and benefit from it without much change in existing client code (e.g., ideally, just change the class of the returned object in getAdapter()). Is this a viable proposal? But anyway, +1 vote for this RFE.
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.
