Bug 462207 - [CSS] Support specific type mappings for Viewpoint diagrams
Summary: [CSS] Support specific type mappings for Viewpoint diagrams
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-16 05:53 EDT by Camille Letavernier CLA
Modified: 2017-09-08 09:50 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Letavernier CLA 2015-03-16 05:53:16 EDT
Currently, the CSS rely on the Diagram#type property to manipulate Diagram-specific rules, such as:

/* 1. */ ClassDiagram Class {
    //A Class in a Class Diagram...
}

However, for viewpoint-based diagrams, it may be useful to have a specific way to distinguish them, such as, either:

/* 2. */ BlockDefinitionDiagram Class{
    //A block diagram is a different diagram. Such a rule would not inherit from ClassDiagram rules
}

or

/* 3. */ ClassDiagram[viewpoint=BlockDefinition] Class{
    //A BlockDefinition is a specific kind of ClassDiagram. Such a rule would inherit from ClassDiagram rules
}

In Luna, IDGen diagrams use syntax 2., whereas Viewpoint diagrams use syntax 1.

In Mars, we'll use a lot more Viewpoint diagrams, so Syntax 2. should probably be used for all Viewpoint diagrams. Syntax 2. and Syntax 3. are currently mutually exclusive (i.e. we need to make a choice).