Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Scout/Tutorial/3.7/Minicrm Step-by-Step

< Scout‎ | Tutorial‎ | 3.7
Revision as of 10:34, 19 October 2010 by Asc.bsiag.com (Talk | contribs) (Reorganize the tree and add a webservice: Split into two sections)

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

This little tutorial will show you how to create your first little application. It uses a very small sample database provided for download. The data is selected from the database and shown on the client, allowing users to browse it, search it and edit it.

Installation / Set Up

You need to get the Scout SDK and a demo database to work through this tutorial. The Scout documentation has been moved to https://eclipsescout.github.io/.

Setup a New Eclipse Scout Project

Switch to the Scout Perspective and create a new Scout Project. The Scout documentation has been moved to https://eclipsescout.github.io/.

Setup a SQL Service

We'll use Apache Derby for this tutorial. We need to tell the framework how to contact it. The Scout documentation has been moved to https://eclipsescout.github.io/.

Write The First Page

A standard Eclipse Scout application consists of pages in a tree structure. A page typically shows data in some sort of table. If you write an application, you need to start with a page. The Scout documentation has been moved to https://eclipsescout.github.io/.

You should have a tiny Eclipse Scout application running at the end of this step!

Add a search form to the table page

We created a page with a table listing all the companies in the database. Add a search form that allows users to limit the number of rows returned. The Scout documentation has been moved to https://eclipsescout.github.io/.

Add a form to edit the data

In order to edit the data in our page, we need to create a context menu to call a form, create the form and the process service it needs to actually select, insert, update (and possibly delete) the data. The Scout documentation has been moved to https://eclipsescout.github.io/.

All the examples in the tutorial were based on the company table. You should be able to do the same for the person table, now.

Write the second page

We wrote the company table page, now let's write a top-level person table page. Once we have that, we want to reuse the table page by also using it as a child page for a company. The Scout documentation has been moved to https://eclipsescout.github.io/.

You will end up with the following tree structure for your application:

Standard Outline
 │
 ├─Company Table Page
 │  │
 │  └─Person Table Page
 │
 └─Person Table Page

Reorganize the tree and add a webservice

We want to add a web service (in this case we're going to use Bing because it offers a standard interface where as Google no longer does). We'll add it under the companies table page, which will require us to add a page with nodes and reorganize the tree a bit. The Scout documentation has been moved to https://eclipsescout.github.io/.

When we're done, the result should look as follows:

Standard Outline
 │
 ├─Company Table Page
 │  │
 │  └─Company Details Node Page ← new
 │     │
 │     └─Person Table Page
 │
 └─Person Table Page

Use a webservice

We want to add a web service (in this case we're going to use Bing because it offers a standard interface where as Google no longer does). We'll add it under the companies details node page. The Scout documentation has been moved to https://eclipsescout.github.io/.

When we're done, the result should look as follows:

Standard Outline
 │
 ├─Company Table Page
 │  │
 │  └─Company Details Node Page
 │     │
 │     ├─Person Table Page
 │     │
 │     └─Bing Table Page ← new
 │
 └─Person Table Page

Back to the top