| --- | --- |
| Bugzilla Link | 521810 |
| Status | NEW |
| Importance | P3 normal |
| Reported | Sep 04, 2017 05:19 EDT |
| Modified | Feb 08, 2018 07:23 EDT |
| Version | 1.7.0 |
| Reporter | Gabor Bergmann |
Description
Inspired by the concept of managed query (engines), the list of active queries in the Query Explorer / Results View and the "magic green start button" to initiate a query, we should implement something analogous for Viatra transformations as well.
This is imagined as an opt-in feature: we still should not mandate all transformations to be externally manageable. However, transformation designers should be able to make (a) their transformation definition, and in case of live transformations, (b) its long-living transformation instances provide some kind of "managed transformation" interface, and immediately gain the following benefits:
Conforming transformation definitions shall be listed in a registry that can be browsed through API and on the UI.
Conforming transformation definitions shall be instantiable for concrete models (i) through their API, as well as on the UI (ii) via a "magic green start button" that identifies a live model in an open editor, or (iii) by selecting a model file in Project / Package Explorer.
The set of live transformations instantiated in the above manner (specifically for live models in open editors) shall be listed on the UI, offering appropriate management functionality, including "dispose", "suspend", "fire all"/"run to completion" when suspended, "resume" when suspended.
| --- | --- | | Bugzilla Link | 521810 | | Status | NEW | | Importance | P3 normal | | Reported | Sep 04, 2017 05:19 EDT | | Modified | Feb 08, 2018 07:23 EDT | | Version | 1.7.0 | | Reporter | Gabor Bergmann |
Description
Inspired by the concept of managed query (engines), the list of active queries in the Query Explorer / Results View and the "magic green start button" to initiate a query, we should implement something analogous for Viatra transformations as well.
This is imagined as an opt-in feature: we still should not mandate all transformations to be externally manageable. However, transformation designers should be able to make (a) their transformation definition, and in case of live transformations, (b) its long-living transformation instances provide some kind of "managed transformation" interface, and immediately gain the following benefits:
Conforming transformation definitions shall be listed in a registry that can be browsed through API and on the UI.
Conforming transformation definitions shall be instantiable for concrete models (i) through their API, as well as on the UI (ii) via a "magic green start button" that identifies a live model in an open editor, or (iii) by selecting a model file in Project / Package Explorer.
The set of live transformations instantiated in the above manner (specifically for live models in open editors) shall be listed on the UI, offering appropriate management functionality, including "dispose", "suspend", "fire all"/"run to completion" when suspended, "resume" when suspended.