| Summary: | "same file for diagram and model" not enforced? | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Yijun Yu <y.yu> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Yijun Yu
Same file for diagram and model cannot be supported, as there is no Xtext grammar for the GMF node model. Thus, the diagram information cannot be persisted. It could work only for so called purely canonical diagrams, i.e. diagrams whose graphical information can be completely restored from the semantic model using the default mappings. There have been lots of problems with GMF in this area recently, see e.g. #314670, so I am pretty certain this is a GMF issue. Please try again with a plain GMF solution and reopen if this tourns out to be an Xtext issue. (In reply to comment #1) > Same file for diagram and model cannot be supported, as there is no Xtext > grammar for the GMF node model. Thus, the diagram information cannot be > persisted. True, the title of my report was misleading. Initially I thought it was the reason, but now I believe it is due to something else. > It could work only for so called purely canonical diagrams, i.e. diagrams whose > graphical information can be completely restored from the semantic model using > the default mappings. There have been lots of problems with GMF in this area > recently, see e.g. #314670, so I am pretty certain this is a GMF issue. Seems the bug #314670 is not yet resolved :-( > Please try again with a plain GMF solution and reopen if this tourns out to be > an Xtext issue. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |