Evaluate the need to use the XText/Sirius bridge from Altran

[mypsycho]

Altran developed a bridge to integrate Sirius and Xtext.

This bridges solves some issues.
We must check that POOSL also deals with those.
Otherwise we can integrate it.

For example, as model has no xmi:id maybe renaming model element may cause diagram corruption.

[mypsycho]

As each poosl text work on it own ResourceSet, it could be interesting to have an AIRD for each file (instead of 2 per project).
With such mechanism, user could control when a resource is loaded and avoid conflict.

[mypsycho]

Ideas to improve xtext/sirius interconnection:

• limit conflict with 1 AIRD/file : Session is loaded and unloaded on demand (representation opening) instead of being always loaded. Not all conflict are avoided but at least user has a way to do.
• provide a custom fragmentProvider in XtextResource: the provider use 'name' instead of list index for containment will limit refactoring impact.
  • Fragment should encode name + index to maximize recognition ?
  • Illegal construction would (no name or name conflict) would still corrupt diagram.
  • Provide a tool to fix representation ? when a representation target is not found, provide a reconciler.
• Use properties view in Sirius