Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[papyrus-rt-dev] Default language framework

Hi,

I was wondering about the status of the default language framework, https://bugs.eclipse.org/bugs/show_bug.cgi?id=487187, and how it is being used in practice. 

When I tested https://bugs.eclipse.org/bugs/show_bug.cgi?id=479635, it worked in a rather different way then what I had expected, i.e. instead of simply creating a type-less parameter, the same kind of popup as when creating ports and capsule parts appeared, asking for an existing type or a new type.

Anyway, after letting this "sink in a bit", this approach is probably a good approach (since we don't have multiple parameters supported in the same way in the legacy tooling, I don't have anything to compare with). 

But if we should keep this popup (instead of simply creating a type-less parameter as I had envisioned from the beginning), then it should also include both the '*' case (leaving the parameter untyped), and the primitive types from the primitive type library (in the corresponding way as we have said that the system protocols for example shall be included in the corresponding popup when creating a port).

But then I realized that I have never understood how and in what way that I activate a specific default language for a model. If I want to start testing functionality that are supposed to fetch system protocols, primitive types and so on, registered via the default language framework, how do I do that? How is the default language framework activated and how is the default language for a model set?

/Peter Cigéhn

Back to the top