dsl-course
commented
4 years ago Daniel, thank you for the comment!
I agree that the first part of the book should be titled "MPS as a UI front-end"; this is much better than my original formulation.
I also agree on your proposal on the second part. I chose Entities Language since I would like to discuss language engineering aspects (e.g., type system of a language) and focus less on a domain [modelling] per se.
As for the third part, I definitely see your point, but still I tend to keep the current title ("MPS as a tool for extending existing languages"): I only cover the topic very briefly (essentially about extending BaseLanguage) and talking about modular DSL stacks would be a bit far-fetched :)
In my oppinion this is misleading because:
My proposal would be: 1) MPS as a UI front-end for a "simple app" - the front-end can be "pure text", or more like a web-form containing lines, graphical widgets, icons, etc 2) MPS as domain specific modeling tool - (I do not know about the "Entities Language" - I would model persons or genealogic trees, books in a library, etc) 3) MPS for building modular DSLs stacks and environments
In our experience, the domain experts (non programmers) often need a special concrete syntax (e.g. tables, math formula, etc) and IMO the freedom to combine concrete syntaxes is central to MPS.