|
|
| (3 intermediate revisions by one other user not shown) |
| Line 1: |
Line 1: |
| − | {{ScoutPage|cat=HowTo 4.0}}
| + | The Scout documentation has been moved to https://eclipsescout.github.io/. |
| − | | + | |
| − | == Scout Explorer view ==
| + | |
| − | [[Image:Scout.3.9.howto.createproject.01.png]]
| + | |
| − | | + | |
| − | In the {{ScoutLink|SDK|Explorer View|Scout Explorer view}} select ''New Scout Project...'' in the context menu of the ''Scout Projects'' folder.
| + | |
| − | | + | |
| − | == Step 1 ==
| + | |
| − | [[Image:Scout.3.9.howto.createproject.02.png]]
| + | |
| − | | + | |
| − | In this step, it is possible to choose:
| + | |
| − | * The Project Name: Base name of the project and the plugins that belong to the project.
| + | |
| − | * The Project Postfix: An optional postfix to add to the plugin names.
| + | |
| − | * The Eclipse Platform: Choose which Eclipse version should be used as target platform for the new project.
| + | |
| − | * The JDT Preferences: If checked the Scout default Java development settings are copied. Otherwise you start with no settings and can apply your own template.
| + | |
| − | * The Project Alias: The short name to use for the application. The client executables and server servlet names will use this shortname.
| + | |
| − | | + | |
| − | | + | |
| − | The plug-ins (e.g. {{ScoutLink|Concepts|UI Plug-Ins|UI Plug-Ins}}, {{ScoutLink|Concepts|Client Plug-In|Client}}, {{ScoutLink|Concepts|Shared Plug-In|Shared}}, {{ScoutLink|Concepts|Server Plug-In|Server}}) are named using the pattern:
| + | |
| − | <project name>.<plug in>.<project postfix>
| + | |
| − | | + | |
| − | In the checkbox list you can choose which plugin-ins need to be created. A Scout application must not always be a client/server application.
| + | |
| − | | + | |
| − | You can also create [[{{BASEPAGENAME}}/Create_a_Standalone_Client_with_DB_Access|client only]] or server only applications.
| + | |
| − | But in any case you must include the shared plug-in in the project.
| + | |
| − | | + | |
| − | Because of the {{ScoutLink|Concepts|Separation_UI_and_GUI|separation of the UI and GUI}} it is possible to choose the UI Plug-ins that will render the application.
| + | |
| − | | + | |
| − | == Step 2 ==
| + | |
| − | [[Image:Scout.3.9.howto.createproject.03.png]]
| + | |
| − | | + | |
| − | This steps allows to choose {{ScoutLink|Concepts|Type of application|the type of application}} that should be created.
| + | |
| − | | + | |
| − | == Step 3 (Optional) ==
| + | |
| − | [[Image:Scout.3.9.howto.createproject.04.png]]
| + | |
| − | | + | |
| − | This step is only available if the RAP UI has been checked in [[{{BASEPAGENAME}}/{{SUBPAGENAME}}#Step_1|Step 1]].
| + | |
| − | | + | |
| − | Because the RAP runtime cannot be installed into the running Eclipse instance a separate target platform must be created. This target platform must contain all plugins to run the Scout RAP UI. There are several possibilities to create such a target platform:
| + | |
| − | *'''Create new RAP Target'''<br>This option is only available on an Eclipse with the ''Scout RAP Target'' Feature installed in the running Eclipse instance.<br>When choosing this option a new RAP target platform will be created at the location specified. This target platform is then defined by all plugins available to the running Eclipse and the RAP target platform extracted to the given directory.
| + | |
| − | *'''Download RAP Target'''<br>When choosing this option the target platform will be downloaded into the running workspace. This download will then only be available to the active workspace! There are two download types:
| + | |
| − | ** Only download the RAP plugins (checkbox not ticked, default)<br>The target platform will be defined by the plugins available to the running Eclipse instance and the downloaded RAP plugins. This download is smaller.
| + | |
| − | ** Download a new Kepler Eclipse platform as well (checkox ticked)<br>A complete, new Kepler target platform will be downloaded and used. This option can be used when you want to ensure that no plugins of the running Eclipse should be in the target platform or if you are not running Eclipse Kepler but want to use Kepler features in your project.<br>Be aware that the developer tools in your runnig Eclipse must be compatible with the Kepler platform that will be used then!
| + | |
| − | *'''Existing RAP Target'''<br>An existing RAP target location can be specified. The wizard then tries to detect whether the given location contains a complete target platform or only the RAP target plugins. If a complete platform is detected, only the directory specified will be part of the target platform. Otherwise the given directory together with the plugins available to the running Eclipse will define the target platform.
| + | |
| − | *'''I'll do it later'''<br>When choosing this option the Scout SDK does not create a RAP target platform for you. The platform must be created manually after the Scout project has been created. The created project will not compile before a complete target platform has been created!
| + | |
