|Re: Include Xtext document formating as model elements [message #1730310 is a reply to message #1730289]
||Sun, 24 April 2016 09:44
| Stephan Seifermann
Registered: March 2015
thanks for your fast response. You are right, my motiviation for including such information did not become clear.
What I would like to realize is storing the Xtext model in a CDO repository, so I can use its abilities such as change notifications. In order to achieve this, it is necessary to store the Xtext model as model and not as text file (which is also supported by CDO). The approach of Stefan Winkler for incremental model upgrades seems promising. Nevertheless, the approach lacks support for restoring the formatting of the document from CDO as this is not part of the model and therefore not stored.
Obviously, I could store the Xtext file as text resource in addition to the model in CDO and apply some synchronization mechanisms but this could become quite hard if the underlying model has been modified in CDO by a mechanism different from the Xtext editor. This is, however, crucial for my use case. Instead, I would like to be able to completely reconstruct the textual representation from the model stored in CDO.
As far as I understand your answer, the data structure containing the information about the textual representation is only available temporarily and not stored in a EMF-like model. I would have to serialize the node model and feed it back to Xtext when the regular model is loaded. I will have a look at this.
Powered by FUDForum
. Page generated in 0.01904 seconds