Bug 393785 - [Navigator & Editor Sockets] Finish up Sphinx editor socket for Graphiti-based graphical editors
Summary: [Navigator & Editor Sockets] Finish up Sphinx editor socket for Graphiti-base...
Status: CLOSED WONTFIX
Alias: None
Product: Sphinx
Classification: Automotive
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Stephan Eberle CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 392424
Blocks: 392431
  Show dependency tree
 
Reported: 2012-11-07 11:24 EST by Stephan Eberle CLA
Modified: 2024-05-07 00:52 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Eberle CLA 2012-11-07 11:24:31 EST
The org.eclipse.sphinx.graphiti.workspace and org.eclipse.sphinx.graphiti.workspace.ui plug-ins provide a Sphinx-integrated editor socket that refers to the applicable Sphinx-managed shared workspace editing domain/resource set instead of operating on its own editing domain/resource set. It enables models to be edited graphically and all modifications to be instantaneously propagated to other views or editors that display the same model instance.

However, the current implementation has still many shortcomings that should be fixed. These shortcomings include but are not necessarily limited to:

	•  Grubby usage of Sphinx EcorePlatformUtil API for loading/saving diagrams
	* Logic that is dedicated to synchronizing diagram editor with resource changes in the workspace that should be eliminated as this sort of service is subject to the Sphinx workspace management
	* Inconsistent repartition of logic Graphiti persistency and update behavior
	
In addition, we must investigate if we have to implement/override other delegate behaviors of the Graphiti diagram editor.
Comment 1 Balazs Grill CLA 2024-05-07 00:52:54 EDT
Closed stale issue before migration