Jump to: navigation, search

Difference between revisions of "E4/Running the demos"

< E4
(SWT for Flex)
(e4 Photo Demo)
(27 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== e4 Photo Demo ==
+
=== e4 Photo Demo ===
  
To run the e4 photo demo (a RCP style example app), you can follow these steps:
+
See [[E4/UI/Running_the_photo_demo]].
# see [[#Project Set Files|Project Set Files]] for info on how to get the files for org.eclipse.e4.ui.releng
+
# import the PSF files 'e4.ui.psf' and 'e4.ui.examples.psf'.
+
# 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 in the old location, HEAD/e4-incubator/demos) into the album directory. You can do this while the demo application is running, it will pick up the changes in its "Library" view.
+
  
 +
=== e4 Contacts Demo ===
  
 +
See [[E4/UI/Running_the_contacts_demo]].
  
=== Project Set Files ===
+
=== XWT Demos ===
  
You can get the latest versions of the project set files from the appropriate team releng project under 'e4/releng' :pserver:anonymous@dev.eclipse.org:/cvsroot/eclipse
+
See [[E4/XWT/Running_the_demos]]
 
+
# Start with Eclipse 3.5 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, releng
+
# Right-click on the appropriate releng project, like 'org.eclipse.e4.ui.releng', and select 'Check Out'.
+
# In the Package Explorer, expand the releng project and select the file PSF file, like 'e4.ui.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.
+
  
 
=== SWT for Flex ===
 
=== SWT for Flex ===
  
The SWT port for Flex consists of the Adobe Flex environment (the ActionScript compiler), the Eclipse host environment (the plugins needed to compile and launch Java code in a Flash player) and the Eclipse target environment (the running plugins, the SWT port itself and example code).  NOTE: That the both the tools and the port are in the pre-alpha stage.  You are living on the bleeding edge.  Good luck!
+
See [[E4/SWT/Running_the_demos]].
 
+
The Eclipse target environment provides support for compiling, launching and debugging java applications in flash player.
+
 
+
'''Setup Flex environment:'''
+
 
+
# Download and install the Adobe Open Source Flex SDK (available from http://opensource.adobe.com). NOTE: The path where you install the Flex SDK must contain no spaces. This is due to a bug in FCSH.
+
# update your eclipse.ini file and add another line at the end, -Dflex.sdk=&lt;your path to the installed sdk&gt;
+
# Verify that your Flex install works by opening a command prompt, changing to the Flex SDK bin directory, typing "mxmlc" and hitting Enter. If you get a message like the following, you will need to add a JAVA_HOME environment variable that points to the home dir or edit the bin/jvm.config file in the Flex SDK.
+
 
+
  ''Error: could not find JRE''
+
  ''Error: could not find Java 2 Runtime Environment.''
+
 
+
'''Setup the Eclipse host environment:'''
+
 
+
# Create a new Eclipse Workspace. NOTE: The path were you create the workspace must contain no spaces. This is due to a bug in FCSH.
+
# Download the project set file (link above) and extract.
+
# Create a java build path variable in Preferences > Java > Classpath Variable preference page. The variable should be called FLEX_SDK and point to the root of the Flex SDK.
+
# see [[#Project Set Files|Project Set Files]] for info on how to get the files for org.eclipse.e4.swt.releng
+
# Import the 'e4.swt.as.psf' project set ("Import..." -> "Team" -> "Team Project Set").
+
# Refresh the project org.eclipse.swt.tools.actionscript.core.
+
# Create a new "Eclipse Application" launch configuration and in the Arguments tab add "-Xmx512M" to its VM arguments.  IMPORTANT: If you do not increase the amount of memory that the VM can use, the Eclipse target will fail with out of memory errors.
+
# Launch the target environment
+
 
+
'''Setup the Eclipse target environment'''
+
 
+
# Turn off auto build ('Project' -> 'Build Automatically')
+
# 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 the target Eclipse workspace.
+
# Add a new ActionScript VM. ('Window' -> 'Preferences' -> 'Java>Installed JREs').
+
## Click Add...
+
## Select ActionScript VM, click next.
+
## Click Directory... and browse to either your Firefox or IE install directory.
+
## Click OK.
+
## Click Finish
+
# Import the e4.swt.as.demo.psf project set.  IMPORTANT: You must use anonymous:anonymous when prompted for username:pwd.
+
# Change the .classpath_flex to .classpath for the following 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).
+
## org.eclipse.swt
+
## org.eclipse.swt.e4.jcl
+
## org.eclipse.swt.examples
+
 
+
# Refresh the org.eclipse.swt project to pick up the linked resources.
+
# Turn on Build Automatically (You can watch the build progress in the ActionScript Build Console, available from the Console view)
+
#  You can run any of the demos from org.eclipse.swt.e4.examples by clicking on them and Selecting "Run As>ActionScript Application". Note that for the Flickr example, you must select static linking in the launch configuration dialog.
+
 
+
'''Setup a sample SWT ActionScript project from scratch'''
+
 
+
  Note that this assumes you have gone through the steps above.
+
 
+
# Create a Java Project.
+
# Add the ActionScript nature to the project "Select Project>Popup Menu>Action Script Tools>Toogle Nature".
+
# Add the org.eclipse.swt project to the Java Build Path projects tab.
+
# Change the execution environment of the project JRE container to J2AS-1.5
+
# Add this class, save and Run as ActionScript Application
+
<source lang="java">
+
public class Main {
+
public static void main(String[] args) {
+
Display display = new Display();
+
Shell shell = new Shell(display);
+
shell.setLayout(new GridLayout(1, false));
+
 
+
Button b = new Button(shell, SWT.PUSH);
+
b.setText("Push");
+
 
+
shell.pack();
+
shell.open();
+
}
+
}
+
</source>
+
  
 
=== SWT for Dojo ===
 
=== SWT for Dojo ===
  
'''*** 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.'''
+
'''Get the SWT codebase and the demos'''
 
+
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 124: Line 44:
 
</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 150: Line 72:
  
 
=== 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 167: Line 91:
  
 
=== 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 174: Line 100:
 
# 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:

Revision as of 12:36, 21 June 2010

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.