Add initial mylyn support to OSATE

[AaronGreenhouse]

Integrate mylyn support into OSATE.
child of #1371

[AaronGreenhouse]

Step 1: need to add the mylyn features to the OSATE build.

[AaronGreenhouse]

Added mylyn to the OSATE2 setup.

[AaronGreenhouse]

Still hunting for good mylyn developer documents.

• https://wiki.eclipse.org/Mylyn/Architecture
• https://wiki.eclipse.org/Mylyn/Integrator_Reference

So far I know that I need to create a Bridge for OSATE. Haven't figured out much beyond that.

[AaronGreenhouse]

Mylyn plug-ins don't seem to include the source code.

I have resorted to importing the source code from the Eclipse GIT repository. Instructions for this are found here: https://wiki.eclipse.org/Mylyn/Contributor_Reference#Setting_Up It's a bit of a chore, but I did finally get it to work.

• You should not be connected to the SEI VPN (Duo)
• For the versions of Mylyn and Gerrit that are current today, installing using Gerrit doesn't work, and you must install using GIT.
• I had best luck using the ssh link to the repository for mylyn all: ssh://user_id@git.eclipse.org:29418/mylyn/org.eclipse.mylyn.all.git
  • You need to use your Eclipse.org-generated username to authenticate.

[AaronGreenhouse]

The main bridge component for the JDT is JavaStructureBridge. I'm going to try to study this and it's ancestor classes to figure out how mylyn works.

[AaronGreenhouse]

JavaUiBridge is the UI bridge component for Java.

[AaronGreenhouse]

Extension points are org.eclipse.mylyn.context.core.bridges and org.eclipse.mylyn.context.ui.bridges.

Cannot find real documentation on how to use these.

[AaronGreenhouse]

Therre is not a lot of Javadoc on the AbstractStructureBridge, but it seems pretty easy. The main job is to turn model elements from the workspace into unique keys or handles as they call them. Also indicates which ones can be opened by an editor (are documents). Been looking at the JavaStructureBridge and the ResourceStructureBridde.

[AaronGreenhouse]

Not sure what the minimum required set of features is for mylyn. We initially just added org.eclipse.mylyn.context_feature to the build, but I had to add org.eclipse.mylyn.context_feature to the build target today.

Once I did this my AadlStructureBridge started to activate. Doensn't seem to do anything yet, but at least it is finally activating.

[AaronGreenhouse]

I should note that I have created a new plugin project org.osate.mylyn.aadl.ui in core.

I created AadlStructureBridge over the last few days. It's pretty simple, but I had to make some changes based on observed behavior. Been using the debugger a lot to try and figure out when and why the different methods are called. Got things so they dont' crash, and I have the bridge a child of the resource bridge (as is the Java bridge). But, I'm still not seeing any AADL elements added to the context.

I was hoping that just the structure bridge would be enough to see this, but I guess not. I am now creating AadlUiBridge. I have a minimal skeleton implementation. I plan on using the debugger again to try and understand what is going on.

[AaronGreenhouse]

Adding a UI Bridge doesn't build the context either.

It seems that was is required is an extension of AbstractUserInteractionMonitor that is registered wtih the MonitorUI:

		MonitorUi.getSelectionMonitors().add(aadlEditingMonitor);

The interaction monitor converts selected elements into handles. This does seem to cause items to be added to the task context.

But so far the AADL elements are added as :"invisiible" elements. They aren't but in the tree in the task context display. Not sure what is going on . I have verified that parents can be resolved all the way up to the project.

[AaronGreenhouse]

Going to search the mylyn source code for "invisible" to see if I can find out how a handle is classified as such.

[AaronGreenhouse]

I figured out how to get the AADL context information to show in the context tree in the task editior. The editor uses an instance of the content viewer from the navigator view framework. So we need to install the aadl-related content extensions into it:

<extension
     point="org.eclipse.ui.navigator.viewer">
	<viewerContentBinding 
        viewerId="org.eclipse.mylyn.context.ui.navigator.context">
		<includes>
			<contentExtension pattern="org.osate.ui.navigator.contributedAadl" />
		    <contentExtension pattern="org.osate.ui.navigator.aadlProjectDependencies" />
			<contentExtension pattern="org.osate.ui.navigator.aadlFileContent" />
		</includes>
	</viewerContentBinding>
	<viewerContentBinding 
		viewerId="org.eclipse.mylyn.context.ui.navigator.context.quick">
		<includes>
			<contentExtension pattern="org.osate.ui.navigator.contributedAadl" />
		    <contentExtension pattern="org.osate.ui.navigator.aadlProjectDependencies" />
			<contentExtension pattern="org.osate.ui.navigator.aadlFileContent" />
		</includes>
	</viewerContentBinding>