Bug 475159 - [Synchronization] Support for synchronization filters
Summary: [Synchronization] Support for synchronization filters
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: Diagram (show other bugs)
Version: 1.1.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-17 09:58 EDT by Christian Damus CLA
Modified: 2015-08-17 09:58 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Damus CLA 2015-08-17 09:58:13 EDT
Papyrus Mars (1.1 release)

Currently, canonical synchronization of a view results in all of its details (as determined by Papyrus's interpretation of the UML) being presented in the diagram.  However, users may wish to have finer control over the synchronization to include only the most relevant information in their diagrams.

Some filtering mechanisms are already available.  For example, in the Class diagram, CSS style rules can be employed to collapse the Operations compartments of all or select classes.  The canonical edit policy does not synchronize the contents of collapsed contents.  Note that synchronization is implemented only at the level of top shapes (in the diagram and in shape compartments), not on compartments, border items, or other such child views.

Other filtering use cases would need some new mechanism, for example suppressing the presentation of associations between classes in the Class diagram.  CSS rules can make them invisible, but they would still exist in the notation model.  This is different to the case of collapsed compartments, in which the notation does not have any views in the compartment.  Filtering the synchronized contents of a shape compartment and of border items presents similar challenges.

Options for specifying filters can include:

* boolean search builder as in the Search UI
* CSS-style selector expressions
* OCL query expressions
* canned filters provided on an extension point

and more.

The specification of synchronization filters for a view might mirror the registration of CSS stylesheets and styles:

* attachment of a filter document to the model or diagram by some named notation style
* attachment of a filter document or individual filter to a view by some named notation style
* attachment of a filter document in the project or workspace preferences
* attachment of a filter document to the viewpoint prototype for a diagram

Or we may have other new ideas that could possibly be back-ported to the CSS subsystem.