Difference between revisions of "Scout/Demo"

Revision as of 23:03, 25 March 2013

The Scout documentation has been moved to https://eclipsescout.github.io/.

Applications

Under construction
A lot of the applications mentioned here are currently under construction (for example made for older scout versions...). We are working on refactoring them (single Git Repository, build with CBI, direct download from binaries).

Widget Demo

Small Demo Application (Client-side only) that displays all the fields.

Path in repository: https://github.com/BSI-Business-Systems-Integration-AG/org.eclipse.scout.example/tree/3.8/scout.examples.demo

Bahbah Chat Application

Presented at EclipseCon and EclipseCon Europe in 2012. More information in this blog article about BahBahChat

Repository: https://github.com/BSI-Business-Systems-Integration-AG/org.eclipse.scout.example/tree/3.8/bahbah

Talks:

• Eclipse Con 2012: "BahBahChat: A Chat Application based on Eclipse Scout (presented by BSI)"
• EclipseCon Europe 2012: Tutorial [1.5 MB] "A Multi-Frontend Chat Application based on Eclipse Scout".

Minifig Application

The minifig Application was created for EclipseCon 2013, to illustrate how Scout Applications could be tested. It is a small client-server application, using The Scout documentation has been moved to https://eclipsescout.github.io/. and The Scout documentation has been moved to https://eclipsescout.github.io/..

3 testing possibilities are illustrated:

• Plain JUnit tests
• JUnit test with a Scout context
• UI-Test using Jubula

The application is build with maven and tycho. Tests are executed using the Scout test runner.

Links:

• Presentation: Testing a Scout Application with JUnit and Jubula
• Slides: TODO
• Sources on GitHub: minifigcreator
• The Scout documentation has been moved to https://eclipsescout.github.io/.

Git Repository

https://github.com/BSI-Business-Systems-Integration-AG/org.eclipse.scout.example/ (Temporary name)

Branches

Working with branches should provide the possibility to work simultaneously on different Eclipse Scout versions with different Eclipse Runtime Versions.

• scout_3.8_eclipse_3.8
• scout_3.8_eclipse_4.2
• scout_3.9_eclipse_4.3

Structure

The idea of the structure is to mutalize some commons parts (CBI Build, configuration files). This is a proposal:

Git Repository: org.eclipsescout.demo
|
+---pom.xml (root pom, has [1.1] as maven module).
+---build
|   +---org.eclipsescout.demo.config <-- common files (.settings files, properties files, maven config templates..)
|   +---org.eclipsescout.demo.master <-- [1] Einstellungen, Version, plugin management...
|   +---org.eclipsescout.demo.parent <-- [1.1] extends [1] und hat {[2], [3], [4]} als module (aggregation)
|   +---org.eclipsescout.demo.target <-- Target Plattform für alle Projekte.
|
+---bahbah
|   +---pom.xml <-- [2] extends [1] and has [2.1] as maven module
|   +---org.eclipsescout.demo.bahbah.parent <-- [2.1] aggregation for bahbah
|   +---org.eclipsescout.demo.bahbah.client
|   +---org.eclipsescout.demo.bahbah.security
|   +---org.eclipsescout.demo.bahbah.server
|   +---org.eclipsescout.demo.bahbah.shared
|   +---org.eclipsescout.demo.bahbah.ui.rap
|   +---org.eclipsescout.demo.bahbah.ui.swing
|   \---org.eclipsescout.demo.bahbah.ui.swt
|
+---jaxws
|   +---pom.xml <-- [3] extends [1] and has [3.1] as maven module
|   +---org.eclipsescout.demo.jaxws.parent <-- [3.1] aggregation for jaxws
|   +---org.eclipsescout.demo.jaxws.client
|   +---org.eclipsescout.demo.jaxws.database
|   +---org.eclipsescout.demo.jaxws.server
|   +---org.eclipsescout.demo.jaxws.shared
|   +---org.eclipsescout.demo.jaxws.ui.swing
|   \---org.eclipsescout.demo.jaxws.ui.swt
|
\---widgets
    +---pom.xml <-- [4] extends [1] and has [4.1] as maven module
    +---org.eclipsescout.demo.widgets.parent <-- [4.1] aggregation for widget
    +---org.eclipsescout.demo.widgets.client
    +---org.eclipsescout.demo.widgets.shared
    +---org.eclipsescout.demo.widgets.ui.rap
    +---org.eclipsescout.demo.widgets.ui.swing
    \---org.eclipsescout.demo.widgets.ui.swt