# 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 ==

+

=== e4 Contacts Demo ===

−

=== Project Set Files ===

+

See [[E4/UI/Running_the_contacts_demo]].

−

Download the project set files referenced below from here: [http://wiki.eclipse.org/images/9/97/E4-demos-psf-projects.zip E4-demos-psf-projects.zip]. (NOTE: This project set contains all of the EclipseCon demos. You will be instructed in the steps below as to which one are needed for Flex, Dojo and the other demos).

+

=== XWT Demos ===

−

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

+

See [[E4/XWT/Running_the_demos]]

−

The demos project also includes the EMF workbench prototype.

+

=== SWT for Flex ===

−

=== SWT for Flex ===

+

See [[E4/SWT/Running_the_demos]].

−

+

−

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!

+

−

+

−

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.

+

−

# 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). IMPORTANT: Set this variable first before running the Eclipse host or target environment or it will be undefined.

+

−

# 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 path variable in Linked Resources preference page (Preferences>Workspace>Linked Resources). The variable should be called FLEX_SDK and point to the root of the Flex SDK.

+

−

# Import the swt-e4Plugins.psf project set ("Import..." -> "Team" -> "Team Project Set"). IMPORTANT: You must use anonymous:anonymous when prompted for username:pwd.

+

−

# 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.

## Click Directory... and browse to either your Firefox or IE install directory.

+

−

## Click OK.

+

−

## Click Finish

+

−

# Import the swt-e4Demos 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.

# 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.

# 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.

e4 Photo Demo

e4 Contacts Demo

XWT Demos

SWT for Flex

SWT for Dojo

Get the SWT codebase and the demos

Create new Eclipse Workspace.

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.

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.

Import the 'e4.swt.as.demo.psf' project set into your workspace.

Configure the projects

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).

Create a Java Project, call it "DojoResources".

Create 2 subfolders, named "public" and "gwt". In the "public" subfolder, create another folder named "dojo".

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

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:

Copy the dojoLib.gwt.xml file from org.eclipse.swt.e4\Eclipse SWT PI\dojo\build to the root of the DojoResources project.

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".

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.

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.