Jump to: navigation, search

Scout/Demo


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitter
Bugzilla
Bugzilla


Applications

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


Widgets

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

Path in repository: /widgets directory (see on GitHub)

Bahbah Chat Application

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

Repository: http://github.com/BSI-Business-Systems-Integration-AG/org.eclipsescout.demo/tree/3.8/bahbah

Talks:


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 SmartField and ImageField

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.

Scout Minifigcreator.png

Links:

iBug Application

The iBug application displays the most recent Bugzilla bugs in the UI. The primary goal of this application is to demonstrate the Scout mobile support coming with the Kepler release. As secondary goal it can be used to show the TableField.

Ibug screeshot.png

Links:

  • Blog post: TBD
  • Sources on GitHub: iBug

Git Repository

org.eclipsescout.demo.git

The project is hosted on GitHub: scout demo project page.

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] preferences, version, plugin management...
|   +---org.eclipsescout.demo.parent <-- [1.1] extends [1] und has {[2], [3], [4]} as module (aggregation)
|   +---org.eclipsescout.demo.target <-- Target Plattform for all projects.
|
+---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


Configurations

Line Endings

We want to have Unix Line endings in the repository. Try to configure your Git client (EGit, GitExtensions, Git Bash...) in order to rewrite the windows line endings to Unix line endings on commit.

 core.autocrlf=input