Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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/Running the demos"

< E4
(→‎SWT Flex)
 
(79 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
== e4 Photo Demo ==
+
'''Historical Document: Demos still on this page never made it out of incubation'''
  
−
To run the e4 photo demo (a RCP style example app), you can follow these steps:
+
=== e4 Photo Demo ===
−
# Start with Eclipse 3.4 and an empty workspace.
+
−
# Open the CVS Repositories view (Ctrl+3 CVSR).
+
−
# Right-click in the view and select New > Repository Location.
+
−
# Copy the following string and paste it into the 'Host' field: :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse .
+
−
# (Optional: Adjust user name, password and connection method if you are a committer.)
+
−
# Expand the repository, then HEAD, e4-incubator, ui.
+
−
# Right-click on 'demos' and select 'Check Out'.
+
−
# In the Package Explorer, expand demos, then projectSets, and select the file 'ui-e4photo.psf'.
+
−
# Select 'Import Project Set' from the context menu on the the psf file
+
−
# A dialog will open asking you to create repository locations. Select each location and click 'Create', providing username 'anonymous' unless you are a committer. Click OK.
+
−
# Open the Run Configurations dialog (Ctrl+3 MRC), expand 'Eclipse Application', select 'e4 photo demo', and click Run.
+
−
# The demo app should open, looking empty. Click on "Create Album".
+
−
# Check the outer Eclipse's Console view, it should have printed a location on disk where it created the album. (It created a project in an Eclipse workspace.) Copy sample photos from your workspace (under demos/sampleData/photos) into the album directory. You can do this while the demo application is running, it will pick up the changes in its "Library" view.
+
  
−
== Demos from EclipseCon 2008 ==
+
See [[E4/UI/Running_the_photo_demo]].
  
−
=== Project Set Files ===
+
=== e4 Contacts Demo ===
  
−
Download the project set files referenced below from here: [http://wiki.eclipse.org/images/7/7b/E4-demos-psf-files.zip http://wiki.eclipse.org/images/7/7b/E4-demos-psf-files.zip]
+
See [[E4/UI/Running_the_contacts_demo]].
  
−
You can also get the latest versions of the project set files from the demos project under 'e4-incubator/ui' :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
+
=== XWT Demos ===
  
−
The demos project also includes the EMF workbench prototype.
+
See [[E4/XWT/Running_the_demos]]
  
−
=== SWT Flex ===  
+
=== SWT for Flex ===
  
−
'''*** Due to Project refactoring these instructions are out of date and this demo is broken. Stay tuned.'''
+
See [[E4/SWT/Running_the_demos]].
  
−
Common setup between the two SWT demos:
+
=== SWT for Dojo ===
  
−
# Create new Eclipse Workspace.
+
'''Get the SWT codebase and the demos'''
−
# Download the project set file (link above) and extract.
+
−
# Import the swt-e4Set.psf file into your workspace by selecting "File -> Import -> Team Project Set" and then select the swt-e4set.psf file from wherever you extracted it. (Click OK for any connection prompt).
+
−
# Click on "Window" from the menu bar and change "Preferences -> Java -> Compiler -> Building -> Build path problems -> Circular dependencies" to Warning.
+
−
 
+
−
Steps specific to Flex:
+
−
 
+
−
# Copy .classpath_flex to .classpath in both the org.eclipse.swt and org.eclipse.swt.e4 projects. (Note that in order to see the classpath files, you have to either do this in the Navigator view or turn off the resources filter in the Packages Explorer by clicking on the drop down arrow menu in the top right hand corner of the package explorer, selecting Filters and unchecking *.resources).
+
−
# Import the swt-e4Compiler.psf file into your workspace by selecting "File -> Import -> Team Project Set" and then select the swt-e4Compiler.psf file from wherever you extracted it.
+
−
# Generate the compiler JAR by running the script org.eclipse.jdt.compiler.as/scripts/export-eca.xml. To run the script, right click and select Run As>Ant Build.
+
−
# Download and install the Adobe Open Source Flex SDK (available from http://opensource.adobe.com) and add an environment variable called FLEX_SDK pointing to the root of the flex SDK ("Control Panel" -> "System" -> "Advanced" -> "Environment Variables" -> "New" under user variables). Restart Eclipse.
+
−
# Run the build script for the example you wish to run in org.eclipse.swt.e4.examples/flex/<example>/build.xml. This will generate the eclipse.swt.e4.examples/flex/<example>/bin/<example>.swf file.  To run the script, right click and select Run As>Ant Build. (You might have to edit the bin/jvm.config file in the Flex SDK if your JRE cannot be found.)
+
−
# Refresh your workspace and open the HTML file in org.eclipse.swt.e4.examples/flex/<example>/bin in a browser (embeded or system one). Note that for your browser to display the swf you must have Macromedia Flash Player 9 installed.
+
−
#For debugging, install the Adobe Flash Player 9 Debugger Version.
+
−
 
+
−
=== SWT Dojo ===
+
−
 
+
−
'''*** Due to Project refactoring these instructions are out of date and this demo is broken. Stay tuned.'''
+
−
 
+
−
Common setup between the two SWT demos:
+
  
 
# Create new Eclipse Workspace.
 
# Create new Eclipse Workspace.
−
# Import the swt-e4Set.psf file into your workspace. (Just click "OK" when it asks for "compatible locations".)
+
# Create a workspace variable in Linked Resources preference page ('Preferences' -> 'Workspace' -> 'Linked Resources'). The variable should be called WORKSPACE and point to the root of your Eclipse workspace.
−
# Change "Preferences -> Java -> Compiler -> Building -> Build path problems -> Circular dependencies" to Warning.
+
# Connect to dev.eclipse.org:/cvsroot/eclipse and browse to the e4 project. Check out the org.eclipse.e4.swt.releng project (located under the releng folder) into your workspace.
−
 
+
# Import the 'e4.swt.as.source.psf' project set into your workspace.
−
Steps specific to Dojo:
+
# Import the 'e4.swt.as.demo.psf' project set into your workspace.
  
−
# Copy .classpath_dojo to .classpath in '''both''' the ''org.eclipse.swt'' and ''org.eclispse.swt.e4'' projects. (Note that in order to see the classpath files, you have to either do this in the Navigator view or turn off the resources filter in the Packages Explorer by clicking on the drop down arrow menu in the top right hand corner of the package explorer, selecting Filters and unchecking *.resources).
+
'''Configure the projects'''
−
# Download the Google Web Toolkit for ''Linux'' (use version 1.4.62 for now). Note it is important to get the Linux download regardless of the OS you are running on.
+
# Replace the contents of the the .project file in the ''org.eclipse.swt'' project with the contents of the .project_e4 file.
 +
# Copy .classpath_dojo to .classpath in '''both''' the ''org.eclipse.swt'' and ''org.eclipse.swt.e4.jcl'' projects. (Note that in order to see the classpath files, you have to either do this in the Navigator view or turn off the resources filter in the Packages Explorer by clicking on the drop down arrow menu in the top right hand corner of the package explorer, selecting Filters and unchecking *.resources).
 +
# Refresh the workspace to pick up the links.
 +
# Download the latest Google Web Toolkit (currently 1.5.3). For the purpose of these instructions, it is assumed that the user is running on Win32.
 
# Download the Dojo Toolkit (use version 1.1.1).
 
# Download the Dojo Toolkit (use version 1.1.1).
 
# Create a Java Project, call it "DojoResources".
 
# Create a Java Project, call it "DojoResources".
Line 75: Line 46:
 
</pre>
 
</pre>
  
−
# Extract the GWT download and import "gwt-dev-linux.jar" and "gwt-user.jar" into the "gwt" folder. Your directory structure should look like this:
+
# Extract the GWT download and import "gwt-dev-windows.jar", "gwt-ll.dll", "gwt-user.jar" and "swt-win32-3235.dll" into the "gwt" folder. Your directory structure should look like this:
  
 
<pre>
 
<pre>
 
gwt
 
gwt
−
-- gwt-dev-linux.jar
+
-- gwt-dev-windows.jar
 +
-- gwt-ll.dll
 
-- gwt-user.jar
 
-- gwt-user.jar
 +
-- swt-win32-3235.dll
 
</pre>
 
</pre>
  
Line 101: Line 74:
  
 
=== Scriptable Workbench ===
 
=== Scriptable Workbench ===
 +
 +
'''*** Due to project refactoring (moving from the incubator to a fully fledged project), these instructions are out of date and the demos are broken. We are working to fix this situation. Please stay tuned.'''
  
 
Common setup between the two Platform UI demos:
 
Common setup between the two Platform UI demos:
Line 118: Line 93:
  
 
=== Eclipse Web Client ===
 
=== Eclipse Web Client ===
 +
 +
'''*** Due to project refactoring (moving from the incubator to a fully fledged project), these instructions are out of date and the demos are broken. We are working to fix this situation. Please stay tuned.'''
  
 
Common setup between the two Platform UI demos:
 
Common setup between the two Platform UI demos:
Line 125: Line 102:
 
# Create a new workspace. This is important - the demo will not run with the SWT projects from above.
 
# Create a new workspace. This is important - the demo will not run with the SWT projects from above.
 
# Download the "Mozilla XPCom for Java" feature from this update site: [http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/ http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/]
 
# Download the "Mozilla XPCom for Java" feature from this update site: [http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/ http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/]
−
# Import the ui-e4Set.psf file.
+
# Check out :extssh:bbokowski@dev.eclipse.org:/cvsroot/eclipse/e4-incubator/ui/demos as a project and then import the /demos/projectSets/ui-e4Set.psf file.
  
 
Running the "Eclipse Web Client" demo:
 
Running the "Eclipse Web Client" demo:

Latest revision as of 12:45, 20 June 2014

Historical Document: Demos still on this page never made it out of incubation

e4 Photo Demo

See E4/UI/Running_the_photo_demo.

e4 Contacts Demo

See E4/UI/Running_the_contacts_demo.

XWT Demos

See E4/XWT/Running_the_demos

SWT for Flex

See E4/SWT/Running_the_demos.

SWT for Dojo

Get the SWT codebase and the demos

  1. Create new Eclipse Workspace.
  2. Create a workspace variable in Linked Resources preference page ('Preferences' -> 'Workspace' -> 'Linked Resources'). The variable should be called WORKSPACE and point to the root of your Eclipse workspace.
  3. Connect to dev.eclipse.org:/cvsroot/eclipse and browse to the e4 project. Check out the org.eclipse.e4.swt.releng project (located under the releng folder) into your workspace.
  4. Import the 'e4.swt.as.source.psf' project set into your workspace.
  5. Import the 'e4.swt.as.demo.psf' project set into your workspace.

Configure the projects

  1. Replace the contents of the the .project file in the org.eclipse.swt project with the contents of the .project_e4 file.
  2. Copy .classpath_dojo to .classpath in both the org.eclipse.swt and org.eclipse.swt.e4.jcl projects. (Note that in order to see the classpath files, you have to either do this in the Navigator view or turn off the resources filter in the Packages Explorer by clicking on the drop down arrow menu in the top right hand corner of the package explorer, selecting Filters and unchecking *.resources).
  3. Refresh the workspace to pick up the links.
  4. Download the latest Google Web Toolkit (currently 1.5.3). For the purpose of these instructions, it is assumed that the user is running on Win32.
  5. Download the Dojo Toolkit (use version 1.1.1).
  6. Create a Java Project, call it "DojoResources".
  7. Create 2 subfolders, named "public" and "gwt". In the "public" subfolder, create another folder named "dojo".
  8. Extract the Dojo download and import the folders into the "dojo" folder. Your directory structure should look like this:
public
--dojo
	-- dijit
	-- dojo
	-- dojoX
	-- util
  1. Extract the GWT download and import "gwt-dev-windows.jar", "gwt-ll.dll", "gwt-user.jar" and "swt-win32-3235.dll" into the "gwt" folder. Your directory structure should look like this:
gwt
-- gwt-dev-windows.jar
-- gwt-ll.dll
-- gwt-user.jar
-- swt-win32-3235.dll
  1. Copy the dojoLib.gwt.xml file from org.eclipse.swt.e4\Eclipse SWT PI\dojo\build to the root of the DojoResources project.
  2. To build the example, run the script org.eclipse.swt.e4.examples\dojo\build.xml. To run the script, right click and select Run As>Ant Build... Click on the JRE tab and select "Run in the same JRE as the workspace".
  3. Copy the index.html file from /org.eclipse.swt.e4/Eclipse SWT PI/dojo/build/ to the generated controlexample folder (org.eclipse.swt.e4.examples/dojo/bin/www/controlexample).
  4. Replace the following line in the index.html file :
<!-- <script src="NAME_OF_GWT_XML_FILE.nocache.js" language="javascript"></script> -->

with this: 

<script src="controlexample.nocache.js" language="javascript"></script>
  1. Open the index.html file in a browser (embeded or system one).

Scriptable Workbench

*** Due to project refactoring (moving from the incubator to a fully fledged project), these instructions are out of date and the demos are broken. We are working to fix this situation. Please stay tuned.

Common setup between the two Platform UI demos:

  1. Download 3.4.
  2. Install XULRunner 1.8.1.3 as described in the SWT FAQ.
  3. Create a new workspace. This is important - the demo will not run with the SWT projects from above.
  4. Download the "Mozilla XPCom for Java" feature from this update site: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/
  5. Import the ui-e4Set.psf file.

Running the "Scriptable Workbench" demo:

  1. Run an inner Eclipse.
  2. Open the "Workbench Model" view by using the Quick Access (CTRL+3) and entering "Workbench Model"

Note that this is experimental code, and many things in the inner Eclipse don't work. Try and play around by changing and running the Javascript code in the right pane of the Model View.

Eclipse Web Client

*** Due to project refactoring (moving from the incubator to a fully fledged project), these instructions are out of date and the demos are broken. We are working to fix this situation. Please stay tuned.

Common setup between the two Platform UI demos:

  1. Download 3.4.
  2. Install XULRunner 1.8.1.3 as described in the SWT FAQ.
  3. Create a new workspace. This is important - the demo will not run with the SWT projects from above.
  4. Download the "Mozilla XPCom for Java" feature from this update site: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/
  5. Check out :extssh:bbokowski@dev.eclipse.org:/cvsroot/eclipse/e4-incubator/ui/demos as a project and then import the /demos/projectSets/ui-e4Set.psf file.

Running the "Eclipse Web Client" demo:

  1. Run an inner Eclipse.
  2. Create a new project (for example, the RCP Mail project)
  3. In Firefox 2, go to about:config and change the value of network.http.max-persistent-connections-per-server to 4 (default is 2).
  4. Start Firefox 2 and point it at http://localhost:8000/e4/files/workbench.html.

Note that the demo only runs in Firefox.

Retrieved from "https://wiki.eclipse.org/index.php?title=E4/Running_the_demos&oldid=365504"

This page was last modified 12:45, 20 June 2014 by Paul Webster. Based on work by Boris Bokowski, John Arthorne and Bogdan Gheorghe and others.

Back to the top