Early Access Program

The Obeo Designer Early Access Program (EAP) provides free access to development versions (milestones) of Obeo Designer and Sirius to make it easy for early adopters to test new features and give us feedback in a more timely manner.

The versions of all the components in the milestone builds (Sirius, but also all its dependencies, including the Eclipse platform) are snapshots of work in progress, and do not correspond to official released versions. Some features might not always work as expected.

These milestone builds are provided for testing purposes and should not be used in production, as they are not supported. Note that due to the way Sirius works, opening existing Sirius projects with an EAP build may alter the files in a way that make them impossible to re-open with earlier, released versions of Obeo Designer or Sirius. When testing an EAP build, use a copy of your projects to keep the original unmodified.

Roadmap

Obeo Designer CE 11.1M1 - September 2018 (current)

Details of this milestone...

Obeo Designer CE 11.1.0 - Late October 2018

This official release will be based on Sirius 6.1.0 final.

Beside fixes and stabilisation work, the main differences with 11.1M1 will be an improved version of the DSL Workflow which was introduced in 6.0, and the move to EPLv2 for Sirius (the version now recommended by the Eclipse Foundation and progressively adopted by all Eclipse projects).

Obeo Designer CE 12.0M1 - 2018Q4

After Sirius 6.1 is released, we will focus on integrating web-based features (which are still experimental at the moment) and the large-scale refactorings needed in Sirius to support both the current RCP-based mode and the new web-based modelers. Milestone releases will be published regularly (every two or three months) to allow early adopters to test and give feedback.

Remember what came with previous official releases.

Obeo Designer change log

 

 

Obeo Designer CE 11.1M1 (current)

This version is based on Sirius 6.1.0M2 and Eclipse Photon. It features the following changes compared to Sirius 6.0. Note that the features which are still considered experimental are not pre-installed in the packages, but are available in the pre-registered update-site in the Obeo Designer Community Edition - Experimental Features (Early Access) category. This includes: Workflow DSL support, ELK integration for improved automatic layout, and the Sirius server.

New features

  • A new visibility diagram edit mode allows to see diagram elements hidden manually with some transparency. In this mode the visibility can be changed by a double click on the target diagram element. (Bug 527109)
  • It is now possible for specifiers to configure Sirius edition tables so that the header column is hidden (Bug 507887)
  • Popup Menu tools are now much more flexible. They used to only appear at the bottom of the context menus, but they can now be contributed into specific sub-menus and positions (Bug 534301).
  • In addition to the default “Select All”, “Select All Shapes” and “Select All Connections” actions, specifiers can now provide custom selection actions, for example to select elements on a diagram based on their type or properties (Bug 534302).

Notable fixes and changes

  • When creating a new Sirius-based modeler, the default font size for labels is now 12px, which is more adapted to current high resolution screens. This does not affect existing modelers (Bug 534980).
  • The Workflow DSL which was introduced in 6.0, and is still experimental at the moment, was broken under Windows in Sirius 6.0.0. This is fixed in this version and in Sirius 6.0.1 (Bug 537811).
  • The underlying version used for the experimental with Eclipse ELK (for improved automatic layout of diagrams) has been updated from 0.3.0 to 0.4.1. See the blog post about the Sirius/ELK integration for more details on this subject (Bug 538769).
  • Many changes and improvements in the (still experimental) server feature, which can be used to interact with a headless Sirius runtime through HTTP via REST and GraphQL APIs. Please refer to the corresponding documentation for the details. Note that nothing is set in stone at this point and all the server-side APIs should be considered provisional and subject to change without notice.