Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "E4/Compatibility/Running the compatibility layer"

Line 1: Line 1:
 
[[Image:E4-compatibility-demo.PNG]]
 
[[Image:E4-compatibility-demo.PNG]]
−
 
−
<strong>NOTICE: This page is under construction !! don't believe anything you read below...</strong>
 
  
 
This demo shows the current state of the eclipse 3.x compatibility layer. The image above shows a workbench populated from an IPerspectiveFactory. The resulting stacks, views and Editor Area are creating by turning the API calls into changes to the modeled UI's structure.
 
This demo shows the current state of the eclipse 3.x compatibility layer. The image above shows a workbench populated from an IPerspectiveFactory. The resulting stacks, views and Editor Area are creating by turning the API calls into changes to the modeled UI's structure.
Line 9: Line 7:
 
<b>Setup:</b>
 
<b>Setup:</b>
  
−
These setup instructions are significantly different from the various e4 demos because the compatibility layer requires that we run against a <i>checked out</i> org.eclipse.ui.workbench project. The expectation is that folks that are interested in working on/with the compatibility layer are themselves eclipse developers/committers interested in checking out how well supported their particular editors/views are currently handled.
+
These setup instructions are significantly different from the various e4 demos because the compatibility layer requires that we run against a <i>checked out</i> org.eclipse.ui.workbench project.
  
 
<b>1) Install eclipse</b>
 
<b>1) Install eclipse</b>
  
−
Start with a fresh install of the latest I-build. Unlike the demos we have to sacrifice (possibly) some stability because the current fragment handling code <i>requires</i> that the workspace contains a checked out <code>org.eclipse.ui.workbench</code> project. If the base eclipse that you are running is not recent then it will fail to compile due to underlying project changes and you may end up 'pulling on a piece of thread' (i.e. checking out multiple other projects to satisfy the compilation requirements).
+
Start with a fresh install of the latest I-build. Unlike the demos, we have to sacrifice (possibly) some stability because the current fragment handling code <i>requires</i> that the workspace contains a checked out <code>org.eclipse.ui.workbench</code> project. If the base eclipse that you are running is not recent then it will fail to compile due to underlying project changes and you may end up 'pulling on a piece of thread' (i.e. checking out multiple other projects one after the other to satisfy the compilation requirements).
  
 
<b>2) Install EMF:</b>
 
<b>2) Install EMF:</b>
  
−
From eclipse go to "Help" -> "Install New Software..." -> "Models and Model Development" -> "EMF SDK - Eclipse Modeling Framework SDK", then restart Eclipse.
+
<ol>
 +
<li>"Help" -> "Install New Software..."</li>
 +
<li>Select the "http://download.eclipse.org/releases/galileo" update site</li>
 +
<li>Open "Models and Model Development"</li>
 +
<li>Check "EMF SDK - Eclipse Modeling Framework SDK"</li>
 +
<li>Hit "Next" as necessary (accepting the license agreement)</li>
 +
<li>Hit "Finish"</li>
 +
<li>Restart eclipse when prompted</li>
 +
</ol>
  
 
<b>3) Load the compatibility layer</b>
 
<b>3) Load the compatibility layer</b>
  
−
<CVS instructions go here>
+
<ol>
 +
<li>Open the CVS Repositories view</li>
 +
<li>Add a new connection to <code>dev.eclipse.org</code> with the repository path 'cvsroot/eclipse', if you are not a committer simply use 'anonymous' as the User name.</li>
 +
<li>Check out the 'e4\releng' project from HEAD</li>
 +
</ol>
 +
 
 +
Now you should have a 'releng' project in your workspace. Drill down into 'org.eclipse.e4.ui.releng', select both 'e4.ui.psf' and 'e4.ui.compatibility.psf', right-click and select 'Import Project Set...'. This will check out the porjects that you need in order to run the compatibility layer.
 +
 
 +
<b>Running the code</b>
 +
 
  
−
Check out the e4 photo demo project from CVS as follows:
 
−
# Start Eclipse with an empty workspace directory.
 
−
# Select <i>File > Import...</i> and select <i>CVS > Projects from CVS</i>, click <i>Next</i>.
 
−
# Copy the CVS repository location and paste it into the "Host" field to populate the wizard page: <i>:pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse</i>
 
−
# You should see "Host: dev.eclipse.org, Repository path: /cvsroot/eclipse, User: anonymous, Connection type: pserver".
 
−
# Click Next and select the second option <i>Use an existing module</i>.
 
−
# Drill down as follows: <i>e4 > org.eclipse.e4.ui > examples</i> and select <i>org.eclipse.e4.demo.e4photo</i>. Click <b><i>Next</i></b>.
 
  
 
The Compatibility demo will come up. Eventually it will be boring because it'll just look like eclipse 3.5. For now the demo will show the current state of the compatibility layer
 
The Compatibility demo will come up. Eventually it will be boring because it'll just look like eclipse 3.5. For now the demo will show the current state of the compatibility layer

Revision as of 11:08, 11 March 2009

E4-compatibility-demo.PNG

This demo shows the current state of the eclipse 3.x compatibility layer. The image above shows a workbench populated from an IPerspectiveFactory. The resulting stacks, views and Editor Area are creating by turning the API calls into changes to the modeled UI's structure.

The views and editors are created through the LegacyViewFactory, a specialized PartFactory that mimics the part creation protocol (creating the executable extension for the part, calling 'createPartControl'...) in eclipse 3.x.

Setup:

These setup instructions are significantly different from the various e4 demos because the compatibility layer requires that we run against a checked out org.eclipse.ui.workbench project.

1) Install eclipse

Start with a fresh install of the latest I-build. Unlike the demos, we have to sacrifice (possibly) some stability because the current fragment handling code requires that the workspace contains a checked out org.eclipse.ui.workbench project. If the base eclipse that you are running is not recent then it will fail to compile due to underlying project changes and you may end up 'pulling on a piece of thread' (i.e. checking out multiple other projects one after the other to satisfy the compilation requirements).

2) Install EMF:

  1. "Help" -> "Install New Software..."
  2. Select the "http://download.eclipse.org/releases/galileo" update site
  3. Open "Models and Model Development"
  4. Check "EMF SDK - Eclipse Modeling Framework SDK"
  5. Hit "Next" as necessary (accepting the license agreement)
  6. Hit "Finish"
  7. Restart eclipse when prompted

3) Load the compatibility layer

  1. Open the CVS Repositories view
  2. Add a new connection to dev.eclipse.org with the repository path 'cvsroot/eclipse', if you are not a committer simply use 'anonymous' as the User name.
  3. Check out the 'e4\releng' project from HEAD

Now you should have a 'releng' project in your workspace. Drill down into 'org.eclipse.e4.ui.releng', select both 'e4.ui.psf' and 'e4.ui.compatibility.psf', right-click and select 'Import Project Set...'. This will check out the porjects that you need in order to run the compatibility layer.

Running the code


The Compatibility demo will come up. Eventually it will be boring because it'll just look like eclipse 3.5. For now the demo will show the current state of the compatibility layer

Retrieved from "https://wiki.eclipse.org/index.php?title=E4/Compatibility/Running_the_compatibility_layer&oldid=143646"

Back to the top