Email
Like
Liked ×
Save
Private Content
Embed
Loading embed code…
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.
Loading

+ Follow

L0020 - The Basic RCP Application

by Tonny Madsen on Aug 13, 2011

747 views

An overview of the code that makes up the skeleton of a basic RCP application. This includes the basics for advisors and perspectives. This module also describes the basics of how to launch and debug ...

An overview of the code that makes up the skeleton of a basic RCP application. This includes the basics for advisors and perspectives. This module also describes the basics of how to launch and debug an RCP application.

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Apple Keynote

Usage Rights

File a copyright complaint

Statistics

Likes: 0
Downloads: 12
Comments: 0
Embed Views: 0
Views on SlideShare: 747
Total Views: 747

\n
Creating a new Eclipse RCP is quite easy: just use the supplied wizard. \n
Enabling the API Analysis does not matter in this case. It is used to test for incompatible changes between releases of a plug-in.\n
Don’t use any of thee other templates – that would be cheating!\n
A launch configuration can be saved in the files system making it easy to share the configuration. Simply click the Shared option on the “Common” tab of the launch configuration and specify the name of the launch file. The shared launch configurations are automatically picked up by Eclipse IDE.\n
\n
The different advisors are described in details in the module “L0038 - The Workbench Configuration”.\n
The different advisors are described in details in the module “L0038 - The Workbench Configuration”.\n
\n
The changes made to way the application is started (and stopped), is primary due to better support servers. In server multiple applications can be running in the same process space and the start and stop methods are therefore important. \n
The generated code above is not really optional when scaling up the application. The PERSPECTIVE_ID should be moved to the Perspective class as ID.\n
\n
\n
The fact that the ActionBarAdvisor is specified by the WorkbenchWindowAdvisor means that each window will have its own set of actions, menus, etc. In most cases, this is overkill and could be avoided by some careful programming. Note though that if the windows are placed on different monitors (with different properties such as size, resolution and color-depth) then it is necessary to have different font and image resources for the different windows…\nThe configurer is used to retrieve the different managers for the menu, tool bar, status line, etc. It is also used to register global actions if needed.\n
\n
Now it’s time for the lab.\n
\n
\n
The exact possibilities when positioning views is covered in the module “L0011 - Contributing to the Eclipse User Interface”.\n
The tab can easily be avoided by using addStandaloneView(…) instead of addView(…). This is useful when certain view may never be moved or closed.\n
This is basically the same as on the previous slide – just declared instead of programmed…\n
\n
Now it’s time for the lab.\n
\n