The RTist development team has been busy finalizing RTist 11.1, and today we are happy to announce its general availability for download.

The full version number is 11.1 2021.16, and at the same time we also release 11.0 2021.16, which is planned to be the last delivery on the 11.0 release track.

All new features in the 11.0 release are also present in the 11.1 release. The only exception is the OneTest Embedded integration which we will make available in the next release of RTist 11.1 (expected to arrive mid-June). Let’s have a look at the new features.

Code Preview

It’s now possible to get a preview of what generated code will look like for an individual model element. This feature can be used for understanding how changes made in the model will affect the generated code. It can also be used as a means to compare two versions of a model at code level. Simply generate a code preview for each of the model element versions and compare them.

You can also use this feature on transformation configurations to get a preview of all code and/or make files that it will generate. This can be of great help for troubleshooting build problems and to compare versions of an RTist application at code level.

 

code-preview

 

OneTest Embedded Integration

The integration with HCL OneTest Embedded allows you to compute and visualize the run-time coverage of state machines in your application. For example, it can be used for finding states and transitions of a state machine that are not covered by current tests.

In this release a number of usability improvements were made, in particular in the Model Coverage viewer. For example, you can now choose to show coverage graphically in only some of the state chart diagrams.

 

model-coverage-viewer

 

Again, remember that the OneTest Embedded integration currently only supports Eclipse 2019.06 and hence it’s not yet included in RTist 11.1.

Support for Internal Transitions in Tracing

The model debugger now correctly handles internal transitions when tracing. When an internal transition runs, the active state remains unchanged and this is now reflected in the trace.

Eclipse Improvements

As always, one of the main benefits with a new major version of RTist is a full year’s accumulated improvements in Eclipse that now can be used in RTist. In addition to core Eclipse improvements in 2020.06 there are also new versions of CDT and EGit with some significant improvements. See the first few slides of the What’s New presentation for links to information about all these improvements (they are too many to list here).

Finally, note that RTist 11.1 now supports being run with Java 11. Java 8 is still supported, but since newer versions of Eclipse only will support Java 11 we recommend that you switch to using Java 11 as soon as possible. Overall the performance of Java 11 is also better compared to Java 8.

Comment wrap
Further Reading
article-img
Secure DevOps | March 4, 2021
Storing Code in Model Files Using CDATA
RTist models are stored in XML files (.emx and .efx). If you have ever opened such a file in a text editor you have probably noticed that code snippets stored in the model can be quite difficult to read due to the encoding of certain characters that is mandated by XML. Here is an example:     Some code snippets are stored as attributes in XML and they can look even worse, since newlines also will be encoded so that the whole code snippet appears on a single line:     Starting with RTist 11.0 2020.33 it's now possible to set a preference so that code snippets will be saved in CDATA sections in the XML file. Thereby the code does not need to be escaped which greatly improves its readability. The preference is called Use CDATA when saving model files and is located on the Modeling preference page. In addition to code snippets, it also affects how documentation texts are stored.     After setting this preference, the code snippets in the examples above will look like this:       Note that older versions of RTist can still read model files that use CDATA. In that sense this feature is backwards compatible. Note, however, that if you edit and save the model in such an old tool version the code snippets will once again be stored without usage of CDATA.  If you decide to start using CDATA in your model files it can be a bit tedious to manually re-save all files in the workspace to use the new format. To simplify you can run a model fixup which will automatically convert all your model files to use CDATA.     Watch this video for more information.
article-img
Secure DevOps | February 8, 2021
New RTist Deliverables Now Available for Download
As a result of our Sprint 2021.04, there are now two deliveries available for download: HCL RTist 11.0 2021.04 and experimental version 11.1 2021.04. Although the experimental version is not yet recommended for production use, we would greatly value any feedback you may have on it. Feel free to reach out to the development team. For now, let’s take a look at what’s new: Single-command Scripted Installation Installation of HCL RTist has never been easier! Just download the script from this page in Utilities section and after a simple configuration, given a product zip file it will automatically download corresponding Eclipse version and depending on RTist version being installed will perform all necessary configuration and installation steps to get you going in minutes. Visualization of Event Routing Complex UML RT models often have many levels of nested capsules, making it difficult to analyze how events are travelling through these structures. In Sprint 2021.04 HCL RTist provides experimental Event Routing Visualization feature, which generates a read-only view of all possible communication paths and relevant parts with respect to a certain port. Despite the new view cannot be used to change the model, you can pan and zoom the diagram, filter to only show paths for In or Out events and switch root capsule context with "Go Inside" and "Go Outside" commands. Please keep in mind that to try this feature you should first activate it in Experimental Features Preferences page. Simpler Qualified Names In many places in RTist like e.g. Properties view you could see fully qualified names of UML elements. Qualified Name of an element includes names of all owning model elements up to the model's root separated by ::. However Capsule Development viewpoint simplifies model representation by hiding some types of elements in Project Explorer view, for example Regions in statemachines. Starting from Sprint 2021.04 fully qualified...
Close