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 "TigerstripeF2F 20080616"
(→Diagram Rendering) |
(→Custom Property Rendering) |
||
Line 52: | Line 52: | ||
== Custom Property Rendering == | == Custom Property Rendering == | ||
+ | * IN case of dynamic multi-value values, use String[] and read-in the list of labels. | ||
== Diagram Rendering == | == Diagram Rendering == |
Revision as of 19:01, 17 June 2008
Contents
< To: Tigerstripe Face2Face Meetings
0.3 Release
- Finalizing for tag v200806161700
- Documentation to be updated in Wiki
- Release Review scheduled for June 26th, 2008
- Asked for IPLog review
Metamodel Changes
Packages as Artifacts
Adding packages as artifacts of the metamodel means:
- Addressing Persistence
- persisted as ".package" in each package directory
- contains a dummy Class without body, we're only interested in the comment so we can re-use parsing/persistence velocity templates in place
- will be hidden from Tigerstripe Explorer
- IPackageArtifact as an extension of IAbstractArtifact
- no additional stuff, but turn off Abstract and others possibly through inheritence
- Add to IModelComponent
Collection<IModelComponent> getContainedComponents() IModelComponent getContainingComponent()
- Editor
- No major issue
- Maybe a bit of refactoring (extends, e.g.)
- Appearance
- in Explorer
- .package is not visible
- right-click to open in editor
- enhance content provider to show dependencies ends (as well as association ends for other artifacts)
- in Class Diagrams
- Show package on diagram
- Allow to "draw" dependencies
- Dependency Diagrams
- in Explorer
- Auditor
- no specific auditing rule
- Appropriate extension points to checked to allow for validation of explicit dependencies against implicit dependencies.
Note: package dependencies are captured directly through DependencyArtifacts as they currently exist.
Whiteboard
Annotation Rendering
The TAF framework supports a few annotations in the .ecore for specifics, but more would be needed. Some of the examples in CVS contain additional rendering (calendar for date, e.g).
Custom Property Rendering
- IN case of dynamic multi-value values, use String[] and read-in the list of labels.
Diagram Rendering
- Ability to change the rendering of artifacts/relationships labels on diagrams based on annotations.
- Provide extension points to delegate the labels (Stereotype compartment and Name Compartments).
- Warning: associations have 1 single compartments, whereas Artifacts have 2 compartments. We need one single API (extension point).
- If label is delegated thru extension point, need to disable action to hide/show package names.
- Similarly, the "visibility" is handled through label, and would need to be properly implemented by any contributed extension.