Skip to main content

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.

Jump to: navigation, search

Mylyn/Context/Modeling Bridge

Proposal

In order to enhance the productivity, integration and traceability benefits of Mylyn, and the task-focused interface, Tasktop technologies proposes to create Mylyn Modeling Integration for UML models in open source Papyrus. This section provides an overview of the scope of the integrations and screenshots are provided as rough examples of the functionality to be provided. The generic term “task” is used to refer to application lifecycle management artifacts such as defects, user stories and feature requests. Estimates include design, implementation, testing and release engineering.

Context Bridge for EMF Models

In order to bring the productivity benefits of the task-focused interface to engineers using Eclipse-based modeling technologies, Tasktop will create a “Context Bridge” for EMF-based models and diagram editors. The result of this will be a focused mode for diagrams that shows only the elements related to the task-at-hand, dramatically reducing information overload for engineers working on large models. In addition, the task-focused interface extensions will provide Mylyn’s one-click multitasking facilities for working with models, ensuring that engineers can instantly recover from interruptions, and share model-specific expertise, when working with models in addition to what Mylyn already provides for engineers working with source code. Model context.png

This feature is a new technology, that to date has only been discussed in Kersten’s PhD thesis and implemented by David Green, Tasktop’s VP of Engineering, for model-driven development diagrams based on a model similar to, but not based on, EMF.[1]

EMF Context Bridge

Integration between the EMF Ecore model with the Mylyn Context degree-of-interest model.

  • EMF-1: identity of Ecore elements is integrated with task context
  • EMF-2: relationships and containment are mapped to the degree-of-interest graph
  • EMF-3: degree-of-interest model elements updated on refactoring of model, for active task
  • EMF-4: contexts with refactored model elements are updated when loaded, eg, using refactoring history

Model project explorer.png


GEF Diagram Focusing

Support for user interface focusing and one-click multitasking facilities for models and diagrams[2] .

  • FOCUS-1: creation of figure filter, highlighter and layout for focused diagrams
  • FOCUS-2: degree-of-interest based view updated and model change notification integration
  • FOCUS-3: Ecore model focusing for Common Navigators
  • FOCUS-4: APIs for GEF figure focusing for downstream editors
  • FOCUS-5: usage tracking for Ecore model and GEF diagram editing and navigation
  • FOCUS-6: editor mementos are restored on task-reactivation
  • FOCUS-7: quick/in-place view of model elements in context
  • FOCUS-8: focus support for EMF models in GMF for UML models in Papyrus.


  1. http://greensopinion.blogspot.com/2008/12/mylyn-context-driven-domain-diagram.html.
  2. Degree-of-interest diagram highlighting can be applied to arbitrary diagrams, while degree-of-interest filtering only applies to diagrams where positioning does not have a semantic relevance (eg, works for UML class diagrams, but not for a pipe-and-filter diagram without additional support for displaying elided elements). For more information see 5.4.1 and related sections of Kersten’s PhD thesis: http://www.tasktop.com/docs/publications/2007-01-mik-thesis.pdf

Back to the top