Hi Oliver

I have tried to do that for my Model Explorer. I followed this link Have
a look http://www.eclipse.org/forums/index.php/t/230983/

But i also need to customise the ContextMenu based on the selected
Synthetic node and didnt find any facility to achieve the same.

Regards
Malai

On 7/1/2014 2:38 PM, Jonas Helming wrote:
> Hi Oliver,
>
> the UI Provider uses the content provider, which are generated by EMF
> (edit bundle). So, I would adapt the item provider in order to change
> the structure of the tree.
>
> Best regards
>
> Jonas
>
> Am 30.06.2014 19:08, schrieb Olivier Labrosse:
>> Hi,
>>
>> I wish to support synthetic items with specific child descriptors, in
>> the Model Explorer, while using EMFStore for persistence.
>>
>> Is there a proper way to extend the EMFStoreUIProvider in order to
>> override the fillContextMenu() method? The point would be to check for
>> instances of said synthetic items, and act accordingly to fetch their
>> list of child descriptors.
>>
>> From what I could find out, the provider name has to match the
>> EMFStoreProvider's in order to get share/commit/etc. functionality in a
>> 3.x application. I'm concerned about contributing my own providers with
>> a name that clashes with the EMFStore ones.
>>
>> Thanks very much once again for your much appreciated support.
>>
>> -Olivier
>>
>> P.S.: if it were proper for you to add an "else if (element instanceof
>> IChildCreationExtender)" in the
>> DefaultUIProvider#fillContextMenuForProject() method, I could submit a
>> bugzilla for it. Anyone wishing to use synthetic items could then
>> simply implement that interface.
>

Hi,

sorry, I misunderstood your question in the first place. An simple
alternative would be to add the menu entries you need using the default
Eclipse menu extension point. Have you tried that?

Best regards

Jonas

Am 01.07.2014 17:09, schrieb Olivier Labrosse:
> Thank you Malai and Jonas for your replies.
>
> Thing is, the problem is not in the tree structure. You'll notice I
> suggested a possible fix to my issue that involved changing the context
> menu; herein lies the problem.
>
> The context menu is already being filled with "create child" menu items
> (see ModelExplorerView#fillContextMenu()), and I intend to make use of
> this for synthetic items as well as EObjects, if only for consistence
> sake. As you know, synthetic items aren't EObjects, and although the
> EMF book suggests making them into full-fledged ItemProviders, they can
> be simple POJOs if the Viewer's ContentProvider is your own custom
> implementation that supports them.
>
> What I'm suggesting is that any UIProvider, or at least the
> DefaultUIProvider, should support synthetic item child descriptors.
> Maybe, instead of what I previously suggested, it's the
> ChildrenDescriptorCollector that should accept any Object, and deal with
> both EObjects and IChildCreationExtenders. All I know is that, without
> this, I would have to create my own view, which is overkill for such a
> simple requirement.
>
> So I guess my question is threefold: Am I missing something? If not,
> should we update DefaultUIProvider and/or ChildrenDescriptorCollector in
> order to support child descriptors coming from synthetic items? And if
> not that either, then is it safe to simply contribute an extension of
> EMFStoreUIProvider or will it break patterns due to identical names?
>
> Thanks again!
>
> Annamalai Chockalingam wrote on Tue, 01 July 2014 06:09
>> Hi Oliver
>>
>> I have tried to do that for my Model Explorer. I followed this link
>> Have a look http://www.eclipse.org/forums/index.php/t/230983/
>>
>> But i also need to customise the ContextMenu based on the selected
>> Synthetic node and didnt find any facility to achieve the same.
>>
>> Regards
>> Malai
>>
>> On 7/1/2014 2:38 PM, Jonas Helming wrote:
>> > Hi Oliver,
>> >
>> > the UI Provider uses the content provider, which are generated by EMF
>> > (edit bundle). So, I would adapt the item provider in order to change
>> > the structure of the tree.
>> >
>> > Best regards
>> >
>> > Jonas
>> >
>> > Am 30.06.2014 19:08, schrieb Olivier Labrosse:
>> >> Hi,
>> >>
>> >> I wish to support synthetic items with specific child descriptors, in
>> >> the Model Explorer, while using EMFStore for persistence.
>> >>
>> >> Is there a proper way to extend the EMFStoreUIProvider in order to
>> >> override the fillContextMenu() method? The point would be to check
>> for
>> >> instances of said synthetic items, and act accordingly to fetch their
>> >> list of child descriptors.
>> >>
>> >> From what I could find out, the provider name has to match the
>> >> EMFStoreProvider's in order to get share/commit/etc. functionality
>> in a
>> >> 3.x application. I'm concerned about contributing my own providers
>> with
>> >> a name that clashes with the EMFStore ones.
>> >>
>> >> Thanks very much once again for your much appreciated support.
>> >>
>> >> -Olivier
>> >>
>> >> P.S.: if it were proper for you to add an "else if (element instanceof
>> >> IChildCreationExtender)" in the
>> >> DefaultUIProvider#fillContextMenuForProject() method, I could submit a
>> >> bugzilla for it. Anyone wishing to use synthetic items could then
>> >> simply implement that interface.
>> >
>
>

Hello Jonas

Then i have a question, i have overriden fillContextMenu when i was
extending ModelExplorerView and i have given my own actions to it.

But my synthetic nodes that i introduced in my itemprovider like for
example in ECP Example, user > tasks[Synthetic Element] > task

Now when i right click on tasks, i cannot add Task. I still need to
right click on User to create a Task.

I would want to know how to i contribute a Right Click on a Synthetic
element using the Item Providers. Coz you are generating the ContextMenu
for new item creation using the NewChildDescriptors in the Item providers.

Correct me if i am wrong.

Regards
Malai

On 7/2/2014 2:17 PM, Jonas Helming wrote:
> Hi,
>
> sorry, I misunderstood your question in the first place. An simple
> alternative would be to add the menu entries you need using the default
> Eclipse menu extension point. Have you tried that?
>
> Best regards
>
> Jonas
>
> Am 01.07.2014 17:09, schrieb Olivier Labrosse:
>> Thank you Malai and Jonas for your replies.
>>
>> Thing is, the problem is not in the tree structure. You'll notice I
>> suggested a possible fix to my issue that involved changing the context
>> menu; herein lies the problem.
>>
>> The context menu is already being filled with "create child" menu items
>> (see ModelExplorerView#fillContextMenu()), and I intend to make use of
>> this for synthetic items as well as EObjects, if only for consistence
>> sake. As you know, synthetic items aren't EObjects, and although the
>> EMF book suggests making them into full-fledged ItemProviders, they can
>> be simple POJOs if the Viewer's ContentProvider is your own custom
>> implementation that supports them.
>>
>> What I'm suggesting is that any UIProvider, or at least the
>> DefaultUIProvider, should support synthetic item child descriptors.
>> Maybe, instead of what I previously suggested, it's the
>> ChildrenDescriptorCollector that should accept any Object, and deal with
>> both EObjects and IChildCreationExtenders. All I know is that, without
>> this, I would have to create my own view, which is overkill for such a
>> simple requirement.
>>
>> So I guess my question is threefold: Am I missing something? If not,
>> should we update DefaultUIProvider and/or ChildrenDescriptorCollector in
>> order to support child descriptors coming from synthetic items? And if
>> not that either, then is it safe to simply contribute an extension of
>> EMFStoreUIProvider or will it break patterns due to identical names?
>>
>> Thanks again!
>>
>> Annamalai Chockalingam wrote on Tue, 01 July 2014 06:09
>>> Hi Oliver
>>>
>>> I have tried to do that for my Model Explorer. I followed this link
>>> Have a look http://www.eclipse.org/forums/index.php/t/230983/
>>>
>>> But i also need to customise the ContextMenu based on the selected
>>> Synthetic node and didnt find any facility to achieve the same.
>>>
>>> Regards
>>> Malai
>>>
>>> On 7/1/2014 2:38 PM, Jonas Helming wrote:
>>>> Hi Oliver,
>>>>
>>>> the UI Provider uses the content provider, which are generated by EMF
>>>> (edit bundle). So, I would adapt the item provider in order to change
>>>> the structure of the tree.
>>>>
>>>> Best regards
>>>>
>>>> Jonas
>>>>
>>>> Am 30.06.2014 19:08, schrieb Olivier Labrosse:
>>>>> Hi,
>>>>>
>>>>> I wish to support synthetic items with specific child descriptors, in
>>>>> the Model Explorer, while using EMFStore for persistence.
>>>>>
>>>>> Is there a proper way to extend the EMFStoreUIProvider in order to
>>>>> override the fillContextMenu() method? The point would be to check
>>> for
>>>>> instances of said synthetic items, and act accordingly to fetch their
>>>>> list of child descriptors.
>>>>>
>>>>> From what I could find out, the provider name has to match the
>>>>> EMFStoreProvider's in order to get share/commit/etc. functionality
>>> in a
>>>>> 3.x application. I'm concerned about contributing my own providers
>>> with
>>>>> a name that clashes with the EMFStore ones.
>>>>>
>>>>> Thanks very much once again for your much appreciated support.
>>>>>
>>>>> -Olivier
>>>>>
>>>>> P.S.: if it were proper for you to add an "else if (element instanceof
>>>>> IChildCreationExtender)" in the
>>>>> DefaultUIProvider#fillContextMenuForProject() method, I could submit a
>>>>> bugzilla for it. Anyone wishing to use synthetic items could then
>>>>> simply implement that interface.
>>>>
>>
>>
>