Community
Participate
Working Groups
Actually, the save and saveAs implementation is done in the CoreMultiDiagramEditor. But, other parts (like model explorer) need to be able to perform save and saveAs and to show the dirtyState. I propose to put the save, saveAs and dirtyState implementations in a separate class and to register it as a Papyrus service. This service will centralize the save and saveAs actions. This service will be available to any parts wishing to use it.
Service ISaveAndDirtyService is created and registered in the ServiceRegistry. It can be retrieved and used from various parts.