Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Demo"
(Add MiniCRM) |
m (→MiniCRM) |
||
Line 17: | Line 17: | ||
=== MiniCRM === | === MiniCRM === | ||
− | Result of the {{ScoutLink|Tutorial/{{ScoutCurrentVersion}}|Minicrm_Step-by-Step|MiniCRM step-by-step}} tutorial. | + | Result of the {{ScoutLink|Tutorial/{{ScoutCurrentVersion}}|Minicrm/Minicrm_Step-by-Step|MiniCRM step-by-step}} tutorial. |
Path in repository: '''/minicrm''' directory ([https://github.com/BSI-Business-Systems-Integration-AG/org.eclipsescout.demo/tree/master/minicrm see on GitHub]) | Path in repository: '''/minicrm''' directory ([https://github.com/BSI-Business-Systems-Integration-AG/org.eclipsescout.demo/tree/master/minicrm see on GitHub]) | ||
[[Image:Scout.3.9.minicrm.reorganize_the_tree.client_swt.png|300px]] | [[Image:Scout.3.9.minicrm.reorganize_the_tree.client_swt.png|300px]] | ||
− | |||
=== Bahbah Chat Application === | === Bahbah Chat Application === |
Revision as of 05:49, 18 August 2013
The Scout documentation has been moved to https://eclipsescout.github.io/.
Contents
Applications
Widgets
Small Demo Application (client-side only) that displays all the fields.
Path in repository: /widgets directory (see on GitHub)
MiniCRM
Result of the The Scout documentation has been moved to https://eclipsescout.github.io/. tutorial.
Path in repository: /minicrm 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:
- 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
- Blog post: Testing Scout Applications
- Slides [1.07 MB]
- Sources on GitHub: minifigcreator
- The Scout documentation has been moved to https://eclipsescout.github.io/.
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 The Scout documentation has been moved to https://eclipsescout.github.io/..
Links:
- Blog post: TBD
- Sources on GitHub: iBug
Git Repository
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 | +---build | +---org.eclipsescout.demo.master <-- [1] preferences, version, plugin management... | +---org.eclipsescout.demo.parent <-- [1.1] extends [1] und has {[1.2], [1.3], [2], [3], [4]} as module (aggregation) | +---org.eclipsescout.demo.repository <-- [1.2] p2 update site | +---org.eclipsescout.demo.settings <-- .prefs files for demo projects | +---org.eclipsescout.demo.target <-- [1.3] Target Plattform for all projects. | +---org.eclipsescout.demo.webapp <-- Template for building the .war | +---bahbah | +---org.eclipsescout.demo.bahbah.parent <-- aggregation for bahbah +---pom.xml <-- [2] extends [1] | +---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 | +---org.eclipsescout.demo.jaxws.parent <-- aggregation for jaxws +---pom.xml <-- [3] extends [1] | +---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 +---org.eclipsescout.demo.widgets.parent <-- aggregation for widget +---pom.xml <-- [4] extends [1] +---org.eclipsescout.demo.widgets-feature +---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