Summary: | [TabbedProperties] Standard Tabs for the platform | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Anthony Hunter <ahunter.eclipse> |
Component: | UI | Assignee: | Anthony Hunter <ahunter.eclipse> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | Kevin_McGuire, remy.suen, thsoft |
Version: | 3.4.1 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Anthony Hunter
2008-09-23 17:20:13 EDT
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. 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. |