I've tested the latest patch-set regarding the default language framework (as part of testing Christians latest changes related to the protocol message parameters). I have some feedback regarding the new "Language" tab in the properties view on the root element of a model.
The property is now simply "Language" which I feel might be a bit to ambiguous. I was actually from before thinking about the same ambiguous use of "Languages" on the new Welcome Page in the model editor. Originally I was actually expecting "C++" to be included in the "Languages" section on the Welcome Page, since I did not understand what kind of "languages" it was referring to. When we switched over to Neon, I understood that the "Languages" section on the Welcome Page was more related to "Model Languages", i.e. UML, UML-RT and so on. Maybe the "Languages" secion on the Welcome Page in the model editor actually should be renamed to "Model Languages"? Or?
But what should we call the "Language" property for the default language, to make things more clear? Should it be "Default Target Language"? This might be applicable for cases like C++, C, Java and so on, but what about the case if and when we use Alf? Is it then better with "Default Action Language" or something like to make things more clear?
In the legacy tooling the corresponding property is named just "Default Language", and currently you can select "Analysis", "C", "C++", "Java", "OCL", "UAL" (which is the predecessor to Alf).
Any opinions how we can make both the use of "Languages" on the Welcome Page as well as on the new "Language" tab in the properties view?
/Peter Cigéhn
PS. I also think that we should make the new "Real Time" tab in the properties view for packages to be even more simplified. I am not sure that Visibility is specifically of interest in UML-RT models. I guess that it could be sufficient to include only "Name" to start with. DS.