Motivation

Stunner based editors,such as the SWF Editor, are (historically) designed for achieveing a comlete editor's lifecycle for every Workbench editor call to setContent. It implies DOM nodes, references and heap being reserved also destroyed on every single setContent call.

Due to new requirements in SWF Editor, the user is able to author the workflow by using the text based editor (at west side), and display the updates on the diagram (visual) based editor (at east side).

It results on the need for changing the lifecycle for the diagram editor, in order to consdier an initial setContent call, followed by multiple updates also relying on setContent.

Goal

Need for editor lifecycle change in order to assume:

• An initial content being set
• Potential further content updates
• Handle setContent promise rejection (actually we're never rejecting it, only diagram edior shows an error icon)

Condierations: TBD

Actions: TBD