Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ease-dev] Popup in Papyrus Model Explorer view

Hi Christian, thanks for your answer, and sorry for my delayed-one.

I fully understand the choice to provide a simplified way to define popup menus, as the targeted users are indeed not Eclipse GUI experts.

That also makes sense in our context, as we would like in the future to provide a simple way to test UML specific features like stereotype applications.

It would give us a preference for the custom keyword approach.

We are just starting to experiment EASE integration with Papyrus and we need to consolidate our strategy. But if confirmed, we would be happy to contribute to modeling module maintenance.

 

Best regards,

 

Sebastien

 

 

 

 

 

 

De : ease-dev-bounces@xxxxxxxxxxx <ease-dev-bounces@xxxxxxxxxxx> De la part de Christian Pontesegger
Envoyé : mardi 3 avril 2018 08:53
À : ease-dev@xxxxxxxxxxx
Objet : Re: [ease-dev] Popup in Papyrus Model Explorer view

 

Hi Sébastien, David,

we once supported expressions for keywords like popup, menu. However experience showed that they were too complicated to write for users. So we simplified these expressions for the time being. One possible solution might be an UI based _expression_ builder similar to what we have in the plugin editor/extension tab. We do show keywords in the properties view already, this would be the perfect place to hook in such an editor. If you would like to spend that time, this would be the perfect solution.

In case you want to go with a custom keyword, this is also fine and I guess the modeling modules would be the best place for it. Exporting the keywordhandler package could be done along with implementing your feature. Please note that no one is actively developing the modeling bundles. In case that dependencies break due to eclipse updates (eg oxygen -> photon) I might have to  remove them from the build if no one steps up to fix them.

cheers
Christian

 

On 30.03.2018 15:40, REVOL Sébastien wrote:

 

Hello EASE-devs,

 

We are from the Papyrus team, and we have a great interest in using EASE with one of the Papyrus components. We particularly appreciate the work done in the modeling modules.

 

However, we would like to add the possibility of executing scripts from a popup originated on the Model Explorer (a very important part of the papyrus perspective).

 

The popup 'enableFor' semantics allows us to add menus for EObjects, by doing "enableFor(org.eclipse.emf.ecore.EObject)", but we'd like to be more specific and check for the effective type of the selected object e.g. o.e.uml2.uml.Class.

 

Browsing through the code we found that  we can’t use the _expression_ framework. As an alternative, we thought we could create a new papyrus specific scripting keyword extending the existing "popup" but adapting the selected element as an  EObject first and then checking if it's instance of the class passed as parameter to the “enableFor”.

 

Do you think this is the best solution? or maybe do you have another suggestion?

 

Now, the thing is the package "org.eclipse.ease.ui.scripts.keywordhandler" is not being exported, so in our tests we had to copy paste several classes to get our PopupHandler working.

 

Do you think it would be possible to export the package?

Also if you think that our code could interest other people, we are really open to directly contribute to the project, maybe as part of the modeling module.

 

Cheers,

 

Sébastien Revol.

David López.




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

 

Back to the top