Add annotation support in use case editor

[GoogleCodeExporter]

Annotations should be represented as child nodes of the step or condition. They 
should be probably visually distinct from use case steps or conditions.

Original issue reported on code.google.com by jiri.vin...@gmail.com on 12 Nov 2011 at 9:40

[GoogleCodeExporter]

- annotations show as child nodes of the use case.
TODO - add annotations also to scenario condition ? Model allows this.

Original comment by jiri.vin...@gmail.com on 1 Jan 2012 at 5:28

• Changed state: Accepted

[GoogleCodeExporter]

In the current version, annotations are rendered as a last child nodes of a 
step. If a step has got multiple extensions/variations together with 
annotations, it is a little confusing.

What might help?
- rendering annotations before extensions
- adding layout modifier, which would move extensions to a separate section 
similar to Procasor's layout
- adding distinct icons for annotations and extensions

Original comment by viliam.s...@gmail.com on 9 Jan 2012 at 7:44

• Added labels: Component-UI, Milestone-Release1.0, Type-Enhancement, Usability

[GoogleCodeExporter]

- annotations rendered before extensions and variations
- added distinct icons for annotations, extansions and variations.

Original comment by jiri.vin...@gmail.com on 4 Mar 2012 at 11:13

• Changed state: Fixed