|
|
|
| Re: GraphView style grammar breaks in Xtext 2.4 [message #1037034 is a reply to message #1036843] |
Tue, 09 April 2013 05:26   |
|
Hi,
simply fix the problems doesnt work?
StyleSheet:
importSection=XImportSection?
'stylesheet' name=QualifiedName 'for' diagramMapping=[gvmapping::DiagramMapping|QualifiedName]
styles+=Style*;
Style:
'style' mappings+=[gvmapping::AbstractMapping|QualifiedName] (',' mappings+=[gvmapping::AbstractMapping|QualifiedName])*
('as' javaClass=JvmTypeReference)?
expression=XBlockExpression?;
XLiteral returns xbase::XExpression:
XClosure |
XBooleanLiteral |
XNumberLiteral |
XNullLiteral |
XStringLiteral |
XTypeLiteral |
XColorLiteral;
XColorLiteral:
color=COLOR;
terminal COLOR:
'#' ('0'..'9'|'a'..'f'|'A'..'F')
('0'..'9'|'a'..'f'|'A'..'F')
('0'..'9'|'a'..'f'|'A'..'F')
('0'..'9'|'a'..'f'|'A'..'F')
('0'..'9'|'a'..'f'|'A'..'F')
('0'..'9'|'a'..'f'|'A'..'F');
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
| Re: GraphView style grammar breaks in Xtext 2.4 [message #1037202 is a reply to message #1037034] |
Tue, 09 April 2013 09:29 |
 Stephan Herrmann
Messages: 1853
Registered: July 2009 |
Senior Member |
|
|
Christian Dietrich wrote on Tue, 09 April 2013 07:26Hi,
simply fix the problems doesnt work?
Thanks for your answer, maybe Jan is interested. As mentioned it comes too late for me.
Let me explain my experiment: while developing a zoo of DSL based tools, I thought, maybe I can use Jan's graph view plug-ins just as a 3rd party library. Sure it says it's just a prototype but for me it worked - in Xtext 2.3.
When I tried to migrate to Xtext 2.4 (in extreme a hurry due to bug 403888) I saw:
- the existing and tested binary plug-ins don't work in xtext 2.4
- the source plug-ins cannot be built with xtext 2.4
- the error message points to a grammar rule that doesn't even exist in the source
At this point the experiment was abandoned, marked unsuccessful. Does this surprise you?
I'm not sure, is the idea of 3rd party black-box xtext modules feasible?
The release version "2.4" for me raised the expectation that this comes with no breaking changes, which doesn't match my painful experience while migrating my tools.
I would strongly suggest that future releases are not published before a good migration guide is published. Doing a release before the much needed migration guide (and even without a release announcement) causes more harm than the delay ever could.
my 2c,
Stephan
PS: keep up the good work.
|
|
|
Powered by
FUDForum. Page generated in 0.03062 seconds
] 
Search
Help
Register
Login
Home
