| Summary: | [E4] Allow some of the 'standard' views to be used in E4 RCP apps without needing the compatibility layer | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Eric Moffatt <emoffatt> |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED DUPLICATE | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | normal | ||
| Priority: | P3 | CC: | bugs.eclipse.org, CraigFoote, falko.schumann, fredrik.attebrant, Lars.Vogel, michael.dehoog, ptotiger1, pwebster, remy.suen |
| Version: | 4.1 | ||
| Target Milestone: | 4.4 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Eric Moffatt
M2 is done... 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) Any update/progress on this? Will there be anyhing in the Kepler timeframe? 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. What are the realistic time-scales? 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. 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. Just to add it to the list one of the first things we might consider moving out from under the IDE are the ISharedImages... ? *** This bug has been marked as a duplicate of bug 350251 *** |