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/Tutorial/3.8/Minicrm/New Eclipse Scout Project"
Line 28: | Line 28: | ||
{{note|Project Name, Project Alias|The project name will be used for all the '''plugins''' created. They'll get names like <tt>eclipse.org.minicrm.client</tt> and <tt>eclipse.org.minicrm.server</tt>. The project alias will be used for the '''servlet''' running on the server. Once you started the server you'll be able to contact it at <tt><nowiki>http://localhost:8080/minicrm</nowiki></tt>. Thus, the alias will be '''visible to the outside world'''.}} | {{note|Project Name, Project Alias|The project name will be used for all the '''plugins''' created. They'll get names like <tt>eclipse.org.minicrm.client</tt> and <tt>eclipse.org.minicrm.server</tt>. The project alias will be used for the '''servlet''' running on the server. Once you started the server you'll be able to contact it at <tt><nowiki>http://localhost:8080/minicrm</nowiki></tt>. Thus, the alias will be '''visible to the outside world'''.}} | ||
− | + | {{note|RAP Target|We directly pressed Finish after the second step in the project creation wizard. By doing so we accepted the default values of the third step for the RAP target creation. To learn more about the project- and RAP target creation please see the {{ScoutLink|HowTo/3.8|Create_a_new_project|Create a new Project HowTo}}}} | |
+ | |||
+ | After the project has been created the [http://wiki.eclipse.org/Scout/SDK/Explorer_View Scout Explorer] is expanded and contains nodes for ''client'', ''shared'' and ''server'' as well as nodes for the 3 user interfaces, ''ui.swing'', ''ui.swt'' and ''ui.rap''. | ||
[[Image:Scout-CreateANewScoutProject7.PNG]] | [[Image:Scout-CreateANewScoutProject7.PNG]] |
Revision as of 05:39, 22 May 2012
The Scout documentation has been moved to https://eclipsescout.github.io/.
We need to create a new Scout Project and switch to the Scout Perspective. When we're done we can run the server, verify that it is running using a web browser, and we can run the client using either the Swing or the SWT user interface.
The client will not yet contain anything, but this will demonstrate that our infrastructure is working.
Once you're done, continue on to setup a SQL service.
Contents
Create a new Eclipse Scout project
If you haven't done so yet, change to the Scout Perspective.
Right-click on the folder Scout Projects and choose New Scout Project in order to create a new Eclipse Scout project.
Use eclipse.org.minicrm as the project name in the first step, click next.
In the second step, choose the outline tree with table form application template. Confirm with Finish.
After the project has been created the Scout Explorer is expanded and contains nodes for client, shared and server as well as nodes for the 3 user interfaces, ui.swing, ui.swt and ui.rap.
Start the Server
Click on the server node. This will show two products, a production product and a development product. Click the green arrow of the development product to start it.
Test the Server
To test if the server is running properly, go to http://localhost:8080/minicrm/process. You should see a page providing information about the server.
Start the Client
Click on either the ui.swing or the ui.swt node and start the development client product by clicking on the green arrow.
You should see an empty client application:
Troubleshooting
- Port 8080 has to be free for this to work. It is also possible to use another port, to do so you have to change the line org.eclipse.equinox.http.jetty.http.port=8080 in the config.ini of the server product and the server.url= in each client interface (rap, swt ,swing).
- If you try to start the Swing Client in Mac OS X, this might fail. To fix this go to the run configuration of the Swing Client. In the tab Arguments change the following: *remove -ws ${target.ws} from the program arguments. *add --launcher.secondThread to the program arguments (if not already present). *remove -Dorg.eclipse.swt.internal.carbon.smallFonts from the VM arguments. *remove -XstartOnFirstThread from the VM arguments. For Mac OS X it is recommended to use the 32 bit Eclipse packages when working with the Swing Client. Please note: When the application is started from the .product file again (using the Launch links), this might undo the changes done to the launch configuration in the steps above!}}