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

Difference between revisions of "Scout/HowTo/3.8/Create a new project"

< Scout‎ | HowTo‎ | 3.8
(New page: {{ScoutPage|cat=HowTo}} == Scout Explorer view == Image:New scout project.png In the {{ScoutLink|SDK|Explorer View|Scout Explorer view}} select ''New Scout Project...'' in the contex...)
 
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{ScoutPage|cat=HowTo}}
+
{{ScoutPage|cat=HowTo 3.8}}
  
 
== Scout Explorer view ==
 
== Scout Explorer view ==
[[Image:New scout project.png]]
+
[[Image:Scout.3.8.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.
 
In the {{ScoutLink|SDK|Explorer View|Scout Explorer view}} select ''New Scout Project...'' in the context menu of the ''Scout Projects'' folder.
  
 
== Step 1 ==
 
== Step 1 ==
[[Image:New scout project step1.png]]
+
[[Image:Scout.3.8.howto.createproject.02.png]]
  
 
In this step, it is possible to choose:
 
In this step, it is possible to choose:
Line 17: Line 17:
 
   <project name>.<plug in>.<project postfix>
 
   <project name>.<plug in>.<project postfix>
  
It is possible to choose which plugin-ins need to be added. A Scout application is not necessary a client/server application. In this case It makes sense to include the shared plug-in in the project (eg client/shared or server/shared). Because of the {{ScoutLink|Concepts|Separation_UI_and_GUI|separation of the UI and GUI}} it is possible to choose the UI Plug-in that will render the application.
+
It is possible to choose which plugin-ins need to be added. 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. <br>
 +
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 ==
 
== Step 2 ==
[[Image:New scout project step2.png]]
+
[[Image:Scout.3.8.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.8.howto.createproject.04.png]]
 +
 
 +
This step is only available if the RAP UI has been checked in [[{{BASEPAGENAME}}/{{SUBPAGENAME}}#Step_1|Step 1]].
  
This steps allows to choose the type of application that should be created.
+
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 3.8 or 4.2 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 Juno Eclipse platform as well (checkox ticked)<br>A complete, new Juno 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 Juno but want to use Juno features in your project.<br>Be aware that the developer tools in your runnig Eclipse must be compatible with the Juno 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!

Latest revision as of 13:28, 4 May 2012

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

Scout Explorer view

Scout.3.8.howto.createproject.01.png

In the The Scout documentation has been moved to https://eclipsescout.github.io/. select New Scout Project... in the context menu of the Scout Projects folder.

Step 1

Scout.3.8.howto.createproject.02.png

In this step, it is possible to choose:

  • The project name (mandatory)
  • The project postfix
  • The project alias (mandatory)

The plug-ins (The Scout documentation has been moved to https://eclipsescout.github.io/., The Scout documentation has been moved to https://eclipsescout.github.io/., The Scout documentation has been moved to https://eclipsescout.github.io/., The Scout documentation has been moved to https://eclipsescout.github.io/.) are named using the pattern:

 <project name>.<plug in>.<project postfix>

It is possible to choose which plugin-ins need to be added. A Scout application must not always be a client/server application. You can also create client only or server only applications. But in any case you must include the shared plug-in in the project.
Because of the The Scout documentation has been moved to https://eclipsescout.github.io/. it is possible to choose the UI Plug-ins that will render the application.

Step 2

Scout.3.8.howto.createproject.03.png

This steps allows to choose The Scout documentation has been moved to https://eclipsescout.github.io/. that should be created.

Step 3 (Optional)

Scout.3.8.howto.createproject.04.png

This step is only available if the RAP UI has been checked in 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
    This option is only available on an Eclipse 3.8 or 4.2 with the Scout RAP Target Feature installed in the running Eclipse instance.
    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
    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)
      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 Juno Eclipse platform as well (checkox ticked)
      A complete, new Juno 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 Juno but want to use Juno features in your project.
      Be aware that the developer tools in your runnig Eclipse must be compatible with the Juno platform that will be used then!
  • Existing RAP Target
    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
    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!

Back to the top