| [solved] Missing whitespace after XText serialization [message #725622] |
Thu, 15 September 2011 11:20  |
|
Hello,
I have (more or less) successfully integrated the FolwerDSL example with a GMF editor.
A statemachine like
state State1
end
state State2
end
leads to the expected diagram. But adding a third state using the GMF editor, leads to a corrupt textual representation like
state State1
end
state State2
endstate State3 end
As one can see, there is some whitespace missing between the 'end' keyword of State2 and the 'state' keyword of the new State3.
I guess something is "wrong" (or let say missing) within the serialization. Can somebody give me a hint?
I have played around with the formatter, but I guess the formatter cannot fix this issue, because 'endstate' is not a valid keyword any more. What is the right way to fix such a problem?
Thanks,
Jonatan
[Updated on: Fri, 16 September 2011 11:50] Report message to a moderator |
|
|
|
| Re: Missing whitespace after XText serialization [message #725705 is a reply to message #725632] |
Thu, 15 September 2011 14:55  |
|
Hello Jan,
I am using Eclipse Indigo with XText 2.0 and a development snapshot of GMF SDK 2.4.
I have read the integration docs, but that did not help so far.
My actual result is like Stage 1 in the docs. Except the missing whitespaces.
I can insert new states in both of the editors (XText and GMF). As soon as I press save, the changes propagate to the other editor. Inserting a new state using the textual XText editor works quite well. But adding a state using the graphical GMF editor leads to the described serialization error. The same problem exists for new transitions inserted using the GMF editor.
Btw: Changes to already existing elements work in both directions, state renaming for instance.
For me it looks like the serialization does not insert the needed whitespace. Do you have any ideas where this comes from? And how it may be fixed?
Thanks,
Jonatan
|
|
|
|
| Re: Missing whitespace after XText serialization [message #726005 is a reply to message #725991] |
Fri, 16 September 2011 11:49 |
|
Hello Moritz,
indeed I was still using XText 2.0.0 as it is shipped with the Eclipse Indigo release.
After updating XText to 2.0.1 all the problemes are gone.
Now it works quite well, and it looks great at the first glance. I guess I have to investigate to GMF in detail to make the graphical part really usable.
Many thanks,
Jonatan
Btw: I am using the new SerializerFragment within my workflow as it comes with the fowler example.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03592 seconds
] 
Search
Help
Register
Login
Home
