[Feature Request] Enhanced Code : Event Based System

[VinceAxe]

It might be helpful and interesting to consider all changes inside the model as Event.

Related Issue :

• [Feature Request] (optional) warning when renaming a concept or changing source/target of a relationship #464
• Feature mentioned inside the [Feature Request] (optional) warning when renaming a concept or changing source/target of a relationship #464 about the alert when an object is deleted
• Help with the Model Repository plugin
  -- [Feature Request] Commit specific diagrams / objects archi-modelrepository-plugin#98
  -- [Feature Request] Cherry Pick archi-modelrepository-plugin#99
  Probably many other things

It has a lot of impact

[Phillipus]

The code already is event based and each change to the model is one or maybe several model events that only have meaning to the user. The code can't decide what has impact or not. Impact depends on circumstances. Changes can only be surfaced to the user by UI code and code that analyses the model.

Example #464 - when there is a reconnection, then the code iterates through every diagram to look for instances of the source and target objects and tries to reconnect them. If one or other is missing then the connection is removed from the diagram so it is not orphaned. This will in fact lead to several events that all go on the undo stack. Whether event driven or not, that code had to be manually constructed to handle that.

So, in those issues, event driven or not makes no difference.

[jbsarrodie]

@VinceAxe Might be good for you to become familiar with the codebase and especially EMF. This should help you understand how all this works and why such suggestion by itself doesn't solve anything.