From Stairway to Heaven onto the Highway to Hell with Xtext
•
0 recomendaciones•965 vistas
This talk was given at EclipseCon Europe 2016. It is an experience report about difficulties we experience in our projects when working with Xtext.
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (15)
Destacado
Destacado (20)
Similar a From Stairway to Heaven onto the Highway to Hell with Xtext
Similar a From Stairway to Heaven onto the Highway to Hell with Xtext (20)
Más de Karsten Thoms
Más de Karsten Thoms (6)
Último
Último (20)
From Stairway to Heaven onto the Highway to Hell with Xtext
- 1. KarstenThoms
- 2. EASY TO LEARN FLEXIBLE GOOD DOCS HIDES COMPLEXITY USES XTEND GOOD SUPPORTFAST PROTOTYPING GOOD DEFAULTS MATURE SOURCE QUALITY
- 3. FLEXIBILITY Who says you can’t play golf with apples? https://pixabay.com/de/apple-natur-green-garten-947674/
- 5. GRAMMAR • Assign ‚name=ID‘ attribute for non-referable elements • Tweaking grammar to optimize non syntax related stuff • generated meta model structure • content assist (e.g. whitespace in combined keywords) • scoping DESIGN SMELLS
- 6. GRAMMAR • Too few / too much keywords • Trying to solve too much with terminal rules • Unordered groups for multivalued assignments • Using Xcore for small metamodels • Enable backtracking to „solve“ a grammar ambiguity issues DESIGN SMELLS
- 7. GRAMMAR • Too few / too much keywords • Trying to solve too much with terminal rules • Unordered groups for multivalued assignments • Using Xcore for small metamodels • Enable backtracking to „solve“ a grammar ambiguity issues DESIGN SMELLS
- 8. GRAMMAR • Too few / too much keywords • Trying to solve too much with terminal rules • Unordered groups for multivalued assignments • Using Xcore for small metamodels • Enable backtracking to „solve“ grammar ambiguity issues DESIGN SMELLS
- 9. AMBIGUITY
- 10. SCOPING • Use declarative scope provider • Navigate cross-references while computing scope • Compute stuff in scope provider which could be put into IEObjectDescription’s user data • „Optimize“ scope to tweak content assist • Check for proxies, resolve proxies • Instantiate unnecessary objects • Access node model and assume that it is complete DESIGN SMELLS
- 11. VALIDATION • Don’t use semantic validation at all • Use @Check without CheckType => Default is CheckType.FAST • Provide check methods for child-elements which traverse sibling elements (e.g. uniqueness check) • Many fine grained check methods • Loading the world again DESIGN SMELLS
- 12. COMPLEXITY
- 13. IDENTIFYINGTHE RIGHT PLACETO FIX AN ISSUE https://pixabay.com/de/nadel-im-heuhaufen-nadel-heuhaufen-1752846/
- 18. OVER ENGINEERING
- 19. DSL OVERLOAD Entity DSL Config DSL Frontend DSL Rule DSL Style DSL Behavior DSL Requirements DSL Cool DSL Yet Another DSL Personal Favorite DSL MyDSL Database DSL Sample DSL The Only Right DSL
- 20. EXPRESSIONS
- 21. DSL != NATURAL LANGUAGE
- 22. NON-TECHIE USERS
- 24. CODE WASTE
- 25. PROTOTYPES
- 26. TESTING
- 29. WRONG TOOL
- 30. PROBLEM SOLUTION
- 31. • Evaluate if Xtext is the right tool to solve a problem [ it often is :-) ] • Get experts on board when starting ambitious projects • Learn underlying technologies (EMF, ANTLR, …) • Continuously develop DSL projects • Write extensive tests • Invest into user experience AVOIDING TROUBLE
- 32. KEEP INFORMED itemis.com / Blogs / Xtext @kthoms @holgerschill @itemis @chrdietrich @franzbecker_io