Community
Participate
Working Groups
The current compare infrastructure requires a plug-in to create a separate text editor for viewing changes between files. This is due a limitation in the workbench that prevents editors from being embedded inside views or other controls. As a consequence, the compare view's editors don't support the full set of features provided by the corresponding real content-type-specific editor, and represents a major usability problem for users switching to the real editor to make changes and then returns to the compare view to review the changes. Eclipse should be more flexible in the ways various editors can be used and reused. [Platform UI, Compare, Text]
There are lots of people already CC'ed to bug 46207.
re-assigning to Stefan as he is working on this
See also bug 87449 .
Stefan, please resolve as dupe
Developed a component framework allowing components to gain access to localized services interfaces provided by the component's containing context. This allows components to be reused in different contexts, as long as the context provides the services required by the component. This framework is a key enabler to support enhanced part nesting in the workbench, since workbench parts can then become components that need not be aware of whether they are at top-level or are nested within some other part. This model of localized services also provides enhanced safety and robustness, because localized services can also clean up after themselves when the component goes away, rather than requiring the component to be diligent about releasing any resources it acquires from its services. One service, ResourceManager, remains as API. This service allows workbench parts to allocate SWT graphics resources that will be disposed automatically when the part goes away. Parts can obtain a ResourceManager from their site like this: ResourceManager r=(ResourceManager)getSite().getAdapter(ResourceManager.class); In 3.1, we developed the component model and framework implementation, as well as specific service interfaces to support part nesting. Further work remains post-3.1 to validate this framework against specific concrete scenarios such as: PDE multi-page editors, providing full-functioned editors embedded in compare editors, and certain nested part scenarios in other Eclipse-based products. It is likely that this will entail further API changes to the framework, and for this reason the framework has been kept internal for 3.1. Marking as LATER.
This is still a duplicate of bug 46207, which is also resolved as LATER.
Re-opening to cover ongoing work in R3.2. New text for the item is: Various problems are encountered when trying to embed editors or views within other workbench parts. For example, the current compare infrastructure requires creating a separate text editor for viewing changes between files. This is due to a limitation in the workbench that prevents editors from being embedded inside views or other controls. As a consequence, the compare editor's nested editors don't support the full set of features provided by the corresponding real content-type-specific editor. This represents a major usability problem: the user must switch to the real editor to make changes and then return to the compare view to review the changes. Eclipse should be more flexible in the ways various editors can be used and reused. The UI component model should be improved to support nesting of workbench parts, and reduce the coupling of parts to particular locations in the workbench, allowing for more flexible UI configurations. [Platform UI, Compare, Platform Text]
(In reply to comment #7) Is there a locus for the ongoing work? Some proposal? Someplace to watch?
Re comment #8: Add yourself to the cc list of this bug. I will post a comment here if/when other material such as a proposal or design document is posted on the UI team's development resources web page.
Note that this work has been deferred for 3.2 due to other priorities. See http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_2.html
*** This bug has been marked as a duplicate of 46207 ***
Feel free to move your votes to the original bug report.
*** Bug 132680 has been marked as a duplicate of this bug. ***
*** Bug 51797 has been marked as a duplicate of this bug. ***
