Papyrus-RT/User/User Guide/Which installation for me
There are three ways for users to install Papyrus-RT:
Each of these methods have their pros and cons and typically used by a different user profiles. The first (RCP) and second (Papyrus-RT Installer) installation methods are designed to be easy to use by users new to Eclipse, while providing slight differences in capabilities. The third installation method is for the experienced Eclipse user.
The pros and cons of each installation method are described below.
Eclipse Papyrus-RT RCP
The RCP (Rich Client Platform) is an all-inclusive self-contained archive of a Papyrus-RT "executable".
- Pro: simple three-step process: download, extract, start working with Papyrus-RT!
- Con: larger file to download
To install using this approach, follow the instructions at Installing Papyrus for Real Time Using the Papyrus-RT RCP
The Papyrus-RT installer is a Papyrus-RT-specific standalone installer powered by Oomph, the same technology used by the Eclipse Installer.
- Pro: Support for all the goodies provided by Oomph, e.g., bundle pooling, managed workspaces, and automatic updates, in a single package.
- Con: You have to answers a few simple questions.
To install Papyrus-RT using this method, follow the instructions at Installing Papyrus for Real Time Using the Papyrus-RT Installer
Eclipse Installer and update sites
This approach is for the Eclipse veterans who are not afraid of the Eclipse Installer, understand what we mean a "p2", and need to install Papyrus-RT with other Eclipse projects!
- Pros: Complete control of what will be part of the installation, including other Eclipse projects!
- Cons: Increased complexity in the installation process with boxes to check and more, more difficult questions to answer.
To install Papyrus-RT using this method, follow the instructions at Installing Papyrus-RT using the Eclipse Installer and update sites
Eclipse Installer - Tester Installation
This installation procedure provides testers with the latest development build of the tool, and it is not unusual to have more than one such builds during the day. This is required for our testers to quickly validate new functionality in order to move forward.
Once installed, the tool will not change unless you explicitly update it.
Installation instructions are found in the Tester installation of Papyrus for Real Time
We consider the following as being the state of the tool:
Structure modeling is at a satisfactory point. This means that the user experience is good and that you can accomplish all tasks related to capsule structure and protocol definition. You may encounter a few isolated usability issues, which we encourage you to report. Note that we do not yet have an implementation of capsule or protocol inheritance.
State machine modeling is probably still at an “expert-friendly” level in many areas. However, this is currently a focus for part of the development team and there will be big improvements in the upcoming weeks. There are also still usability issues and some state machine diagram artefact rendering issues (e.g., with external self-transition after a restart of the tool).
Hierarchical state machines are not currently supported, but you can use sub-states in state machines to achieve similar capabilities (with obvious limitations).
Code generation and the accompanying runtime is currently working well. If a problem is encountered in this area, doing a “make clean” in the CDT project where the code is generated and a “regenerate” is likely to solve any lingering issues.
All other capabilities, e.g., sequence diagrams and activities, are still at the Papyrus UML level and have not yet been adapted to UML-RT.
If you have any further questions, please do not hesitate to contact us. Evaluating a new, complex tool like Papyrus-RT can be a difficult exercise and we would like to help you getting through it.
Thank you for your interest in this technology.