[ui] OCL Capabilities

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 273680 | | Status | CLOSED FIXED | | Importance | P3 major | | Reported | Apr 25, 2009 11:32 EDT | | Modified | May 27, 2011 02:54 EDT | | Version | 1.2.0 | | Reporter | Adolfo Sanchez-Barbudo Herrera |

Description

As discussed in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=254138

An org.eclipse.ocl.capabilities plugin is required to disable the UI related to the OCL Console example.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Apr 25, 2009 13:04

Created attachment 133224 OCL capabilities plugin

Plugin which defines the OCL capabilities.

:compression: org.eclipse.ocl.capabilities.zip

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Apr 25, 2009 13:08

Created attachment 133225 (attachment deleted)\ Patch for Galileo product

Patch for Galileo product (branding, build, features, etc).

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Apr 25, 2009 13:18

Ken,

I have followed the http://wiki.eclipse.org/Galileo_Capabilities link in order to create the patch for galileo product.

In principle, commiting the plugin to the CVS's head and applying the patch should suffice to solve the issue. However, I have a doubt Christian said that the Interpreter example is just shipped in the SDK build, but it's not done in the runtime build. I don't know if I have to do something else >.<

BTW, I have checked that the OCL appears in the capabilities preference section and the Interpreter example doesn't appear if the OCL activity is disabled ;).

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Kenn Hussey on May 22, 2009 10:53

I'm afraid it's too late to address this issue (which would involve the addition of a plug-in) at this stage of the release (post-RC). :(

Given Christian's comment (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=254138#c3) about whether this is even necessary for OCL (since the only UI is the New Example Wizard), I think the community can probably live with that this time around. We'll make sure this is done for the next release.

[eclipse-ocl-bot]

By Ed Willink on Oct 30, 2009 11:19

Adolfo: The project has changed a lot since April. This patch probably needs a minor rework.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Dec 23, 2009 06:48

Assigning to myself.

I'll face this bug again. We need some discussion, though.

• Which UI-related plugins are we shipping into Helios release ?. In which features are we doing that ?.
• I have recently heard from Ed, that this or new examples will be included into Helios, but they won't be included in the SDK. From my point of view, I'm not sure that removing the current example from the SDK is a good idea. The current OCL console should probably be improved before making it take part from the MDT-OCL UI instead of being an example plug-in. In any case, I'm inclined to keep the example as part of the SDK since the MDT-OCL is used to having the useful example there, and we could unnecessarily receive complains about that if we remove it. Any new example, could perfectly be placed out of the SDK.
• Are we including the improved OCL console example (Bug 259922) into Helios ? as a different example ? should we replace the old console by this one?.

From my point of view, and unless somebody wants to seriously face on MDT-OCL UI concerns, I would be inclined to do the following:

• Keep the current OCL Console as an example into the SDK feature.
• Include the improved console, the ocl editor, the top-cased evaluator and such as different examples included in an examples feature. I think that Ed has made a great work about gathering possible requirements for a useful MDT-OCL tool for the end user (Bug 297475). For Helios release, I think we could ship the different examples, so that we could get more feedback from the end user.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Alexander Igdalov on Dec 23, 2009 07:02

(In reply to comment #6)\ +1 to keeping the old console example as a part of SDK. Currently we don't have it in our build artifacts (bug 298459). I am working on this now.

[eclipse-ocl-bot]

By Ed Willink on Dec 23, 2009 07:28

+1 to all UI capabilities being in the Helios examples.

The Model Registry should be non-examples. The Model Registry UI will be in examples.

I would prefer to wait till at least M6 and possibly M7 before deciding whether to use the new or old console. We need to give Sebastien as much encouragement as possible.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Dec 23, 2009 11:09

1. About the OCL capabilities plugin (org.eclipse.ocl.capabilities)

I think that I'll commit the same plugin I created into MDT-OCL repository. I'll also include a new activityPatternBinding which would match any org.eclipse.ocl.ui. UI contribution so that if in the future we move any example to an official UI plugin (org.eclipse.ocl.ui.), we won't have to remember to modify the capabilities' extension point.

Apart from that we also have to agree the namespace for the examples:

• Are we mantaining the org.eclipse.emf.ocl.examples plugin's name for the current OCL Console example ?
• Are we creating a new org.eclipse.ocl.examples.* plugins to include the new examples?. Should the old old OCL console, get this namespace ?. Should we use "ui" for the plugins name ?.

I'm inclined to establish the following namespace for the example's plugins:\ org.eclipse.ocl.ui.examples."example1".\ org.eclipse.ocl.ui.examples."example2". ...

So that we should just find interesting names for the last part of the plugin's name (editor, evaluator, console, interpreter, oldconsolse, newconsole)...

If this convention is supported, the activityBindingPattern of the capabilities plugin would be reduced to match "org.eclipse.ocl.ui.*" (It currently has org.eclipse.emf.ocl.examples to match the console example).

2.About the patch with the modified files for the Helios release:

I'll create a new patch against the org.eclipse.helios projects which I'll attatch to this bug. However since I don't probably have permission for committment into callisto repository, I won't be able to do that. Alex, I guess that you will need to do it.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Dec 23, 2009 12:15

Created attachment 154982 Patch for Helios product

:notepad_spiral: ocl273680_OCLCapabilities_heliosFiles.txt

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Dec 23, 2009 12:17

OCL Capabilities plugin (3.0.0) committed to CVS HEAD.

I'll update the extension point with the proper pattern when we have agreed the namespace of the plugins which will contribute to UI.

Alex, I guess you can patch the Helios files, since the plugin is already in the CVS head.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Dec 23, 2009 12:45

PSF file updated with the new plugin.

[eclipse-ocl-bot]

By Alexander Igdalov on Dec 24, 2009 09:54

(In reply to comment #11)

Alex, I guess you can patch the Helios files, since the plugin is already in the CVS head.

Patch for Helios product committed to HEAD.

Regarding namespaces, I would leaving the old o.e.emf.ocl namespace unchanged. I don't think we should loose CVS history and perform the refactoring just for the sake of beautifying the namespaces. The old naming is not that bad too.

[eclipse-ocl-bot]

By Adolfo Sanchez-Barbudo Herrera on Jan 13, 2010 06:59

It seems that no UI contributions different to org.eclipse.emf.ocl.examples will be shipped into Helios product so I resolve as fixed.

Cheers,\ Adolfo.

[eclipse-ocl-bot]

By Ed Willink on May 27, 2011 02:54

Closing