|Re: Model meta elements and their instances? [message #1809927 is a reply to message #1808656]
||Thu, 25 July 2019 18:48
| Matthias Steinkamp
Registered: June 2019
Hey, sorry for the late reply and sorry for my bad explanation.|
I plan an UI platform with several different Views. Every view needs different properties, different widgets, content, variables to edit etc. About 10 different view types.
Now, as I see it, I could describe every particular view with it's properties in the DSL, so that I can create concrete UI menus in the .mydsl file.
However I'm interested if I can do it a step more abstract, so that the DSL does know there can be different views with possible properties (widgets), but it shall not define the actual combinations.
That way someone should be able to 1. Describe in the .mydsl file, what views are actually possible (e.g. "numeric editor" with one property "Variable" to edit) and afterwards 2. State that there are 10 actual numeric editor instances, editing variables a, b, c, ... Another customer might want to model an editor with three variables and only 2 actual instances.
"NumericEditor" is a View
"TemperatureSetpoint" is NumericEditor
"Brightness" is NumericEditor
If this approach is way to complicated, just say so.
I hope I explained it more clear this time. As I see it, part 1. Would be the meta model and 2. The model. And normally the DSL is the meta model and the .mydsl file is the concrete model?
Btw, what are the .mydsl files called? DSL instances?
Thank you very much for your patience and time!
Powered by FUDForum
. Page generated in 0.01528 seconds