Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Tigerstripe Tips-n-Tricks"
| Line 3: | Line 3: | ||
{{backlink|Tigerstripe}} | {{backlink|Tigerstripe}} | ||
__TOC__ | __TOC__ | ||
| + | |||
| + | =Tigerstripe Annotations Framework= | ||
| + | ==How-to create and register a new annotation scheme== | ||
| + | The Tigerstripe Annotation Framework is a mechanism to annotate any artifact in a Tigerstripe model to drive code generation. As opposed to typical Stereotypes, Annotations are <strong>not</strong> stored in the model itself. As a result, annotations can be kept, distributed and maintained separately from the model itself, without cluttering it. | ||
| + | |||
| + | To see an example of how you can define your own annotation scheme and use it against Eclipse resource, Java elements or Tigerstripe artifacts, read the [[Define Tigerstripe Annotations]] article. | ||
| + | |||
| + | == Integrate Tigerstripe Annotations == | ||
| + | The Tigerstripe Annotation Framework is completely generic and has no dependency on Tigerstripe itself. In fact, the Tigerstripe Annotation Feature can be installed without other Tigerstripe components and will allow to annotate Eclipse Workspace resources and Java Elements out of the box (see section above to define an annotation scheme). | ||
| + | |||
| + | Integrating the annotation framework with any other source can be done through a few steps. This article, "[[Integrating Tigerstripe Annotations]]", will highlight the details. | ||
=Tigerstripe Generation Plugins= | =Tigerstripe Generation Plugins= | ||
| − | |||
| − | |||
==Use Objects (not classes) to drive generation== | ==Use Objects (not classes) to drive generation== | ||
Since the very early nightly builds of the [[Tigerstripe 0.3 stream|0.3 Stream]], it is possible to create M0-Generation Plugins that allow to generate content based on the instances (M0-Level) of opposed to Classes (M1-Level). | Since the very early nightly builds of the [[Tigerstripe 0.3 stream|0.3 Stream]], it is possible to create M0-Generation Plugins that allow to generate content based on the instances (M0-Level) of opposed to Classes (M1-Level). | ||
Revision as of 11:38, 22 April 2008
This page hosts a set of articles about Tigerstripe Workbench.
< To: Tigerstripe
Contents
Tigerstripe Annotations Framework
How-to create and register a new annotation scheme
The Tigerstripe Annotation Framework is a mechanism to annotate any artifact in a Tigerstripe model to drive code generation. As opposed to typical Stereotypes, Annotations are not stored in the model itself. As a result, annotations can be kept, distributed and maintained separately from the model itself, without cluttering it.
To see an example of how you can define your own annotation scheme and use it against Eclipse resource, Java elements or Tigerstripe artifacts, read the Define Tigerstripe Annotations article.
Integrate Tigerstripe Annotations
The Tigerstripe Annotation Framework is completely generic and has no dependency on Tigerstripe itself. In fact, the Tigerstripe Annotation Feature can be installed without other Tigerstripe components and will allow to annotate Eclipse Workspace resources and Java Elements out of the box (see section above to define an annotation scheme).
Integrating the annotation framework with any other source can be done through a few steps. This article, "Integrating Tigerstripe Annotations", will highlight the details.
Tigerstripe Generation Plugins
Use Objects (not classes) to drive generation
Since the very early nightly builds of the 0.3 Stream, it is possible to create M0-Generation Plugins that allow to generate content based on the instances (M0-Level) of opposed to Classes (M1-Level).
For more information about this please visit the Tigerstripe M0-Based Generation article.