Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351363 - [E4] Allow some of the 'standard' views to be used in E4 RCP apps without needing the compatibility layer
Summary: [E4] Allow some of the 'standard' views to be used in E4 RCP apps without nee...
Status: CLOSED DUPLICATE of bug 350251
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal with 5 votes (vote)
Target Milestone: 4.4 M6   Edit
Assignee: Platform UI Triaged CLA
QA Contact: Eric Moffatt CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-06 14:52 EDT by Eric Moffatt CLA
Modified: 2014-01-23 16:45 EST (History)
9 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Moffatt CLA 2011-07-06 14:52:44 EDT 
This is needed to make the RCP story more palatable. At the moment E4 ECP apps cannot use any of the 3.x views without dragging in the complete compatibility layer.

We should first determine which views are candidates and then refactor them into a separate bundle that has no (direct) dependencies on Workbench[Window|Page]...
Comment 1 Eric Moffatt CLA 2011-09-15 12:52:47 EDT 
M2 is done...
Comment 2 Eric Moffatt CLA 2011-10-20 14:59:21 EDT 
This will likely have to be deferred until after 4.2 ships. We simply don't have the cycles to take this on right now.

Since we don't have a 4.3 bucket yet I'll target this to M7 (then likely 4.3)
Comment 3 Fredrik Attebrant CLA 2013-03-14 05:21:11 EDT 
Any update/progress on this?
Will there be anyhing in the Kepler timeframe?
Comment 4 Eric Moffatt CLA 2013-03-14 13:46:48 EDT 
Not really, we've looked a bit more into it.

Some folks have copied some existing code over and made it work in e4. This isn't really what we want though; we want to have the 'real' implementation in 4.x apps to use the 'e4' part itself and provide a way to host that part in 3.x (i.e. using Tom Schindl's 'bridge'). 

If we just fork the code then bug fixes on one branch won't be picked up in the other which, over time, will be a mess.
Comment 5 Phil Beauvoir CLA 2013-03-28 14:09:27 EDT 
What are the realistic time-scales?
Comment 6 Eric Moffatt CLA 2013-04-25 15:18:09 EDT 
Realistically this will happen over an extended period of time. In Luna we expect to move over at least some of the views, starting with the ones with the least 3.x baggage like the Error Log view.

Some of the other views are closely tied to the eclipse 'Workspace' (Project / Resource Explorers...) so we'll likely have to provide an e4 Workspace implementation first.

One of the goals is to see if we can identify useful patterns for 'porting' existing 3.x components into a 4.x component and a 3.x component (based off of the 4.x implementation but perhaps with 3.x specific (i.e. Site...) code. That way we can help other packages to move in the same direction...in the same way.
Comment 7 Lars Vogel CLA 2013-04-25 15:33:21 EDT 
Eric, I think we can help for porting views. We only need to know how the platform can consume pure e4 parts. I would be great if the core platform team could focus on that, we will then try to port some parts.
Comment 8 Eric Moffatt CLA 2013-05-02 15:04:07 EDT 
Just to add it to the list one of the first things we might consider moving out from under the IDE are the ISharedImages... ?
Comment 9 Lars Vogel CLA 2014-01-23 16:45:20 EST 

*** This bug has been marked as a duplicate of bug 350251 ***