Eclipse Community Forums: Sirius » Restricting referred objects

Help

Home

Home » Eclipse Projects » Sirius » Restricting referred objects

Show: Today's Messages :: Show Polls :: Message Navigator

Restricting referred objects [message #1750218]

Sun, 18 December 2016 22:01

Arunkumar Ramaswamy

Messages: 57
Registered: April 2014

Member

Hello

I have created a hierarchical state machine meta model and graphical editor using sirius. While creating model instance, I am selecting a reference objects in the drop down list in the properties tab. I would like to restrict the objects getting populated in the list that could be referenced. For example, state transitions should have source and target states in the same hierarchical level. How could I do this?

Any help much appreciated
Arun

Report message to a moderator

Re: Restricting referred objects [message #1750255 is a reply to message #1750218]

Mon, 19 December 2016 10:58

Felix Dorner

Messages: 392
Registered: December 2015

Senior Member

Look at IItemPropertyDescriptor.getChoiceOfValues() and its implementations. Eventually you'll get to the generated ItemProvider and see that the default descriptor it returns is an org.eclipse.emf.edit.provider.ItemPropertyDescriptor. You can subclass this, and override for example org.eclipse.emf.edit.provider.ItemPropertyDescriptor.getComboBoxObjects(Object)

Report message to a moderator

Re: Restricting referred objects [message #1750293 is a reply to message #1750255]

Mon, 19 December 2016 16:26

Arunkumar Ramaswamy

Messages: 57
Registered: April 2014

Member

Thanks Felix for your suggestion.
Is there any way to do it using OCl in Ecore. Something that I put these constraints as OCL in Ecore and the autogenerated editors with property views restrict this population of elements.

Thanks,
Arun

Report message to a moderator

Re: Restricting referred objects [message #1750296 is a reply to message #1750293]

Mon, 19 December 2016 16:50

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

I doubt you can use OCLinEcore directly today,.

In principle anything that is hand-coded in Java can have its data structures modelized so that all conversions are implementable as M2Ms and all state can be verified using constraints, perhaps implemented using OCLinEcore.

However few toolsmiths model everything, largely because the quality and so ease of use of modeling tools does not compare well with that of Java. We struggle to improve them, but there are rather more Java tooling developers than model tooling developers.

You could try to introduce a programmable layer for menu filtering and contribute it to the community. More likely you have deadlines and just need to get the job done yesterday. Hack it in Java.

Regards

Ed Willink

Report message to a moderator

Previous Topic:	I can't sort UML elements by type in model explorer or tables!
Next Topic:	ConcurrentModificationException when drop a container to another parent

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 00:20:19 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter