Skip to main content

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

Hi Remi,

Thanks for the feedback. Well I guess it is fine that the framework so far is "hard-coded" to C++ (since that is the only language we initially will support). But what is needed for the framework to return the primitive types and system protocols via the internal API (from what I have understood, the tooling should be able to ask the default language framework and get back the list of primitive types and system protocols, for further presentation and selection in various menus and similar)? Do you manually have to add some package import of the primitive types library and the run-time model library (I really hope that the default language framework does not require that you *must* have the package import, and that they only are for convenience of the user chooses to keep them in the model)? Or is it sufficient that the framework is hard-coded to returning C++? I am not fully sure I have understood how the internal API is supposed to work.

I started to test properties view for a protocol message and the new parameters table, but I cannot see any primitive types from the primitive types library to be available for selection. And I am not sure either where to look for them. See also my comments here https://bugs.eclipse.org/bugs/show_bug.cgi?id=476984#c28 But if we already have integrated this type selection with the default language framework, what is needed from me to get the primitive types to be included? If it is hard coded to C++, then I assume that nothing as an end-user is needed, or?

Yes, eventually we probably should have profile with some stereotype that is applied on the root element with a property indicating the selected default language for this model. In my opinion is should be sufficient to only support one default language per model. You need to break up your model into multiple models in case you want to have different default languages for different parts of your model. It feels a bit too complex to support that you can have different default languages for smaller parts of one model

/Peter Cigéhn

On 20 May 2016 at 11:31, SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> wrote:

Hi Peter,

 

For now, the default language framework always returns the same value, for any kind of element: cpp. This work is awaiting in a pending gerrit, that was stopped because of the various refactoring / build issues of the tool.

Next work to be integrated is the ability for a given model (sub-part of?) to give a specific default language, as ‘none’, or ‘Cpp’, or any language later when we will have more languages supported. This was expected to be handled in a specific annotation (profile?), to track the information for a specific model element.

The work was initiated in the review https://git.eclipse.org/r/#/c/67560/, but the way to identify the current default language has not been done yet.

 

Regards,

Rémi

 

 

 

-------------------------------------------------------

 

Rémi SCHNEKENBURGER

+33 (0)1 69 08 48 48

CEA Saclay Nano-INNOV

Institut CARNOT CEA LIST

 

Description : PapyrusLogo_SmallFormatwww.eclipse.org/papyrus

 

De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Peter Cigéhn
Envoyé : vendredi 20 mai 2016 10:56
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [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


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev



Back to the top