Summary: | [Outline][PropertiesView] Multi-page editor support for separate property and outline pages (1GCBWEG) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Nick Edgar <n.a.edgar> | ||||
Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> | ||||
Status: | ASSIGNED --- | QA Contact: | |||||
Severity: | enhancement | ||||||
Priority: | P5 | CC: | andreas.salzborn, cernst, daniel_megert, douglas.pollock, ebelisar, kmaster_2k, remy.suen, rolf.theunissen, thatnitind, twolf, wassim.melhem | ||||
Version: | 2.0 | Keywords: | helpwanted | ||||
Target Milestone: | --- | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Nick Edgar
2001-10-10 22:22:14 EDT
PRODUCT VERSION: 0.044 Defer Reopened for investigation As this is an internal request I am going to mark it WONTFIX. Nick please re- open if yout think this is useful Hello, i would like to comment this "bug". I need to implement a form based multi page editor (FormEditor) wich has only one editor input. The input is a remote file from an RMI server, which will allready be cached lazily in local workspace by the input itself, if some document provider requests the source file of the input. One page is a nested Text-Editor which shows the "raw" text-data. It would be very usefull if a standard mechanism would give the ability to contribute multiple outline pages for an multi-page-editor, maybe something like a container of pages for every nested editor or form-page. ...Or in common, the workbench should (optional) request outline-pages from every form-page/editor-part and provide a standard implementation which handles the switch between the inner-outline-pages. Best regards A. Salzborn, Germany ProDevelop Reopening. I still think this scenario is pretty common. Wassim, does this crop up in PDE at all? The MPE would need to delegate the getAdapter implementation for the IOutlinePage.class case to the active nested editor, but there would also need to be some kind of (indirect) notification back to the outline view when the nested page changes so it can re-request the page to show. Also, currently the Outline view assumes that a given part (i.e. outer editor) supplies only a single page, and caches this. So either this assumption needs to be relaxed, or it needs to know about the nested editor. It may also be the case that you want to show an outline for a tab that is not editor-based. yes, we certainly have that problem in PDE but we worked around it in FormEditor which subclasses MPE. In our implementation of FormEditor#pageChange(), we explicitly update the outline view. FormEditor#getAdapter() returns an appropriate outline view for IContentOutlineView.class I see, so you return a single outline page for the outer editor, but it knows about sub-outline-pages to show for corresponding sub-editor-pages? yes. however, we don't update the outline with every page switch. For example,the same outline page appears for all form pages, but every source page has its own. *** Bug 38641 has been marked as a duplicate of this bug. *** There are currently no plans to work on this feature. PW Changes requested on bug 193523 Created attachment 111910 [details]
firefox file
Comment on attachment 111910 [details]
firefox file
This attachment is viral and should be deleted.
If somebody is interested in looking into this bug, MultiPageMinimapPage is a good starting point. This page uses multiple sub-pages for different editors. I have done some experiments with that, but I think my code got (partially) lost. (In reply to Rolf Theunissen from comment #16) > If somebody is interested in looking into this bug, MultiPageMinimapPage is > a good starting point. This page uses multiple sub-pages for different > editors. There's also org.eclipse.egit.ui.internal.commit.MultiPageEditorContentOutlinePage and its companion NestedContentOutlinePage that may serve as inspiration. Used in CommitEditor, DiffEditorPage, and DiffEditorOutlinePage. |