Community
Participate
Working Groups
There is still work to be done in the diagram components to completely adopt the new EMF-Transaction API so we do not need the compatibility layer. Specifically: - How refreshSemanticChildren() and the CanonicalEditPolicy should be reworked so that any model changes (i.e. creation of new views) is done in response to a pre-commit event notification and refreshing of the UI (editparts, figures) is done in response to a post-commit event notification. - Remove compatibiliy layer and make sure everything still works.
Also to do: - Move the code in DiagramEventBroker where the view is persisted to be in response to a pre-commit event.
There is still changes that need to be done to NotationMetaModelProvider, NotationAdapterFactoryManager, etc. I believe all this can be removed but there may be code in there that needs to be moved elsewhere. Need to investigate.
Fixed : the persist element handling had been moved to the pre-commit no other changes are required caus ethe diagram editing domain noew allows starting write actions on the post=commit handling
[target cleanup] 1.0 M6 was the original target milestone for this bug
[GMF Restructure] Bug 319140 : product GMF and component Runtime Diagram was the original product and component for this bug