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"
(→Start the Client) |
|||
Line 56: | Line 56: | ||
{{note|A Different Language|If you want to run the client in a different language than your system's default, you might have to fiddle with the ''configuration''. From the ''Run'' menu, choose ''Debug Configurations...'' and switch to the ''Arguments'' tab. There, replace <tt>-nl ${target.nl}</tt> with <tt>-nl en_US</tt> (if you're working with a German locale and need to make screen shots for the wiki, for example). Click the ''Apply'' button and the ''Debug'' button. Eclipse will remember this setting as long as you keep reusing the Run and Debug menus (using the two green buttons in the tool bar to run products). If you use the ''Scout Object Properties'' tab, this language setting will revert to the default.}} | {{note|A Different Language|If you want to run the client in a different language than your system's default, you might have to fiddle with the ''configuration''. From the ''Run'' menu, choose ''Debug Configurations...'' and switch to the ''Arguments'' tab. There, replace <tt>-nl ${target.nl}</tt> with <tt>-nl en_US</tt> (if you're working with a German locale and need to make screen shots for the wiki, for example). Click the ''Apply'' button and the ''Debug'' button. Eclipse will remember this setting as long as you keep reusing the Run and Debug menus (using the two green buttons in the tool bar to run products). If you use the ''Scout Object Properties'' tab, this language setting will revert to the default.}} | ||
− | + | '''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 <tt>-ws ${target.ws}</tt> from the ''program arguments''. *add <tt>--launcher.secondThread</tt> to the ''program arguments'' (if not already present). *remove <tt>-Dorg.eclipse.swt.internal.carbon.smallFonts</tt> from the ''VM arguments''. *remove <tt>-XstartOnFirstThread</tt> 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!}} |
Revision as of 02:29, 23 April 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.
If you expand the project tree it will have nodes for client, shared and server as well as nodes for the three 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!}}