Bug 511783 - Initialize tool operation with no-op operation
Summary: Initialize tool operation with no-op operation
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: Next   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on: 496019
Blocks:
  Show dependency tree
 
Reported: 2017-02-06 12:12 EST by Laurent Fasani CLA
Modified: 2018-08-21 09:56 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Fasani CLA 2017-02-06 12:12:19 EST
Each time the specifier create a tool, he has to create a initial operation and most of the time create a changeContext operation.

This ticket is to consider that the InitialOperation and the ChangeContext(var:self) should be done automatically at the tool creation.

This ticket aim to generalize what have been done specifically to have navigate tool in properties view. https://bugs.eclipse.org/bugs/show_bug.cgi?id=496019.
Comment 1 Laurent Fasani CLA 2017-02-06 12:27:58 EST
This ticket should be handled simultaneously with https://bugs.eclipse.org/bugs/show_bug.cgi?id=508256 as the solution may be very similar.

A possible alternative is to superclass all the xxxItemProviderFactory with an implementation that could overload createChildParameter(Object feature, Object child). See providerRootExtendsClass attribute in edit part of xxx.genmodel.

Another alternative to study is to use ChildCreationExtender(on package
in genmodel)to extend ItemProviderFactory for a given package. It allows
to overload createChildParameter(Object feature, Object child). Then
overloading can be targeted on only the VSM packages.