Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Tigerstripe 0.4 stream"
(→Availability) |
(→Content Highlights) |
||
| Line 28: | Line 28: | ||
== Content Highlights == | == Content Highlights == | ||
| − | + | ||
| + | === Ganymede === | ||
| + | Tigerstripe v0.3 wasn't working with Ganymede because the code relies on a few internal APIs that had changed from Europa to Ganymede. This can easily be fixed and will be included in the first milestone build of 0.4. | ||
| + | |||
| + | In addition, we will migrate the GMF based code (Class Diagrams and Instance Diagrams) to the latest version of GMF. Currently the code was generated based on GMF 1.x and was customized to address some of the Tigerstripe-specific requirements. With the addition of "Packages" as elements of the Tigerstripe metamodel, we will need to allow the Class Diagrams to represent packages, which means we will need to re-generate the diagram code and update the customized code accordingly. | ||
| + | The first milestone 0.4 build will still have the old GMF code (using the 2.1.x runtime), the second Milestone build will have all the migrated code. | ||
| + | |||
| + | === Packages as part of Metamodel === | ||
| + | Up until now, the Tigerstripe metamodel doesn't treat "packages" as first-class citizens of the model. They are implied (as containers of artifacts) but not explicitly addressable. This means in particular that it is not possible to attach stereotypes or annotations to them. | ||
| + | |||
| + | With 0.4, we will add Packages to the underlying metamodel, offering an IPackageArtifact through the M-API. Existing projects will remain compatible. | ||
| + | |||
| + | This new artifact type will be available from the first milestone build (0.4M0) but will only be available on Class Diagrams in the 0.4M1 build as this will require a GMF re-generate of the diagram code. | ||
| + | |||
| + | === Custom Artifact Tool and Rendering === | ||
| + | |||
| + | === GMF diagram rendering of Annotations === | ||
| + | The Tigerstripe Annotation Framework (TAF) allows to define annotations (or decorations) onto models that can further be consumed during code generation in the MDE cycle. | ||
| + | |||
| + | Version 0.4 will allow to display annotations defined against specific artifacts on Class Diagrams. This will allow to further document models by showing/hiding annotations as appropriate in models. | ||
| + | |||
[[Category:Tigerstripe]] | [[Category:Tigerstripe]] | ||
[[Category:Tigerstripe Releases]] | [[Category:Tigerstripe Releases]] | ||
Revision as of 18:17, 7 July 2008
Contents
< To: Tigerstripe Release Streams
Overview
The 0.4 will build on the 0.3 path in a number of areas, in an effort to strengthen Tigerstripe as a framework, while bringing addition features/bug fixes.
In particular, we will continue the work on the Tigerstripe Annotation Framework to enable rendering of annotations on GMF diagrams, both from a generic perspective but also as an integrated solution for Tigerstripe diagrams. We will also work on robustness for the overall framework.
We are also going to progress the EMF migration by building more logic and features on the EMF-based version of the M-API (See Tigerstripe APIs). This will be part of the Tigerstripe base feature. In parallel, we will also add "model packages" as true IModelComponents in the Tigerstripe metamodel.
From a Tigerstripe workbench perspective, we will integrate the latest version of the Annotation framework to allow rendering of Annotations on both Class and Instance diagrams. We will also introduce more customizations options through the use of "Artifact Templates", basically allowing to define "cookie cutters-style templates for Artifacts, with specific stereotypes, annotations, as well as dynamic icons/labels. These templates will be available eventually as tools on the Class Diagram palette for example.
Availability
| Date | Build | Comment |
|---|---|---|
| July 23, 2008 | 0.4M0 | First stable build of 0.4 - Diagram support for annotations, Package part of metamodel. |
| Aug 15, 2008 | 0.4M1 | TBD |
| Aug 29, 2008 | 0.4 | 0.4 Release - Based on Release Review |
Content Highlights
Ganymede
Tigerstripe v0.3 wasn't working with Ganymede because the code relies on a few internal APIs that had changed from Europa to Ganymede. This can easily be fixed and will be included in the first milestone build of 0.4.
In addition, we will migrate the GMF based code (Class Diagrams and Instance Diagrams) to the latest version of GMF. Currently the code was generated based on GMF 1.x and was customized to address some of the Tigerstripe-specific requirements. With the addition of "Packages" as elements of the Tigerstripe metamodel, we will need to allow the Class Diagrams to represent packages, which means we will need to re-generate the diagram code and update the customized code accordingly. The first milestone 0.4 build will still have the old GMF code (using the 2.1.x runtime), the second Milestone build will have all the migrated code.
Packages as part of Metamodel
Up until now, the Tigerstripe metamodel doesn't treat "packages" as first-class citizens of the model. They are implied (as containers of artifacts) but not explicitly addressable. This means in particular that it is not possible to attach stereotypes or annotations to them.
With 0.4, we will add Packages to the underlying metamodel, offering an IPackageArtifact through the M-API. Existing projects will remain compatible.
This new artifact type will be available from the first milestone build (0.4M0) but will only be available on Class Diagrams in the 0.4M1 build as this will require a GMF re-generate of the diagram code.
Custom Artifact Tool and Rendering
GMF diagram rendering of Annotations
The Tigerstripe Annotation Framework (TAF) allows to define annotations (or decorations) onto models that can further be consumed during code generation in the MDE cycle.
Version 0.4 will allow to display annotations defined against specific artifacts on Class Diagrams. This will allow to further document models by showing/hiding annotations as appropriate in models.