Community
Participate
Working Groups
Extracted from Bug 487187: Another possibility should be to select a default/active language after a model has been created (for which no language were selected). This could for example be done via the properties view for the root element of a model. Then the applicable libraries shall be imported (possibly optional by having a dialog asking if any missing libraries really shall be imported) and profiles be applied be applied automatically. Currently (pre-0.8.0), the libraries are simply loaded when switching to a new language. No package import is created. When the model is loaded, the libraries referenced by the current default language get loaded by the language service. It could be possible to have a popup menu when switching from one language to another: it should ask if the package imports for current language should be removed, and if the new required libraries should be simply loaded or a package import should be created.
Just to clarify: The creation of the package imports for the libraries should be purely optional. From a tooling perspective, e.g. when providing primitive types or system protocols in pop-up menus, the assigned default language of the current model should be what is used. The package imports shall only be added for the convenience of those users that want them explicitly imported. Thus when (re-)selecting a language the choice of creating the package imports must be optional by presenting a popup asking the user what to do.
I guess we should add Bug 502547 on the See Also since that one is related to a current inconsistency where the default language framework only loads a subset of the libraries related to a specific default language.
Moved to future until more information is received, enabling proper assignment.
