Skip to main content
Jump to: navigation, search

Difference between revisions of "Riena/Getting Started"

m
m (Set up target platform for Riena apps)
Line 31: Line 31:
 
* In the project "RienaSetup", select the launch configuration "SWT ExampleApplication E4" and add required plug-ins, then Run it. For Riena on 3.x or RAP, use the appropriate launch configuration.
 
* In the project "RienaSetup", select the launch configuration "SWT ExampleApplication E4" and add required plug-ins, then Run it. For Riena on 3.x or RAP, use the appropriate launch configuration.
 
* Now explore the code and plugin.xml in the example project
 
* Now explore the code and plugin.xml in the example project
* The isolated ridget usage of some aspects of Riena
+
* Some specific techniques are demonstrated in the snippets project.
  
 
== Manual target platform setup ==  
 
== Manual target platform setup ==  

Revision as of 10:57, 7 June 2013

{{#eclipseproject:rt.riena}}


For a Riena-based application to compile, a certain set of bundles (plug-ins) must be available at compile time. This set of bundles is known as a target platform. Follow the steps outlined in either of the following two sections to set up the target platform for Riena applications (based on Riena 4.0.0). Windows users can just download the complete targetplatform, unzip it and activate it under Window => Preferences => Plugin Development => Target Platform.


Set up target platform for Riena apps

  • Download the RienaSetup project and import it into your workspace.

Import project RienaSetup.png


  • In the imported project, open the file "Riena_on_4x.target" and set the target platform. If you want to use Riena on an Eclipse 3.x or RAP basis, select the appropriate target platform.

Target platform editor RienaSetup.png


  • Open the "Plug-Ins" view and import as source project:
    • org.eclipse.riena.example.client
    • org.eclipse.riena.sample.snippets (not relevant for Riena on RAP)

Import source project RienaSetup.png


  • In the project "RienaSetup", select the launch configuration "SWT ExampleApplication E4" and add required plug-ins, then Run it. For Riena on 3.x or RAP, use the appropriate launch configuration.
  • Now explore the code and plugin.xml in the example project
  • Some specific techniques are demonstrated in the snippets project.

Manual target platform setup

  • Create a new target platform under Window => Preferences => Target Platform => Add => Nothing: Start with an empty target platform => Next
  • Provide a name like Riena 4.0.0
  • Click Add => Software Site
  • Select the repository: http://download.eclipse.org/eclipse/updates/3.8
  • Uncheck "Group by Category" otherwise you can't see all components.
  • Uncheck "Include required software" and select following components:
    • Eclipse RCP
    • Eclipse RCP Plug-in Developer Resources
    • Eclipse RCP SDK
    • Equinox Target Components

The result should look like this:

Riena Targetplatform RCP.png

  • Activate the platform.
  • Done.

Next Step

Now you are ready to start writing Riena applications. To get a feeling of the Riena framework, take a look at Riena's Example Applications and Code Templates.


Set up Riena Toolbox

For more details about the Riena Toolbox, look here http://wiki.eclipse.org/Riena/Toolbox.

Build your own Riena-Targetplatform

Riena provides a tycho-build to build a targetplatform from cvs head. Follows these steps:

Prerequisites:

Start the build:

  • Checkout the bundle org.eclipse.riena.build.tycho from cvs (:pserver:anonymous@dev.eclipse.org:/cvsroot/rt)
  • Open a shell and go to the directory org.eclipse.riena.build.tycho
  • Checkout the sources by executing: ant -f checkout.xml -DCHECKOUT_DIR=checkout -DTARGET_DIR=target
  • Go to target/org.eclipse.riena.build.tycho
  • Execute: mvn clean install -P all-modules -Dmaven.test.skip=true

At the moment Tycho can't handle the package import to javax.servlet, so we had to replace this with a dependencie. We accomplished this by patching the MANIFEST.MF from the bundle org.eclipse.communication.core after the checkout. There may be other issues with the result of this build or the buildprocess itself, so be aware that this is not yet production ready.

Back to the top