Page History

...

This procedure is designed to help you create the files that are needed to install your plug-in within IGB. The first section contains the steps needed to modify your local copy of the IGB code in order to generate the needed files. You should have an updated, local copy of the IGB code or check out the most recent version from Sourceforge.

...

Step 5. Update Activator.java: Expand the sample plugin / src folder until you see Activator.java (and SamplePlugin.java).

...

Open Activator.java and update the code with your package declaration as well as occurrences of your plug in class name. The sample code implements an annotation operation, so Activator.java registers service for Alignment, Annotation and ProbeSet means this plugin is designed only for these 3 types of annotations. Actually this SamplePlugin derives from the existing IGB plugin named OverlapAnnotationOperator which you can find it in the plugins folder.

There are also many other different types of operation for annotation and graph created as a plugin or not, such as MergeAnnotationOperator plugin and XorOperator in core folder then com.affymetrix.genometryImpl.operator package.

Your plugin class name is inserted in the file as shown in the following code, as "MyPlugin".

@Override
protected ServiceRegistration<?>\[\] registerService(IGBService igbService) throws Exception {
	return new ServiceRegistration\[\] {
		bundleContext.registerService(Operator.class, new MyPlugin(FileTypeCategory.Alignment), null),
		bundleContext.registerService(Operator.class, new MyPlugin(FileTypeCategory.Annotation), null),
		bundleContext.registerService(Operator.class, new MyPlugin(FileTypeCategory.ProbeSet), null)
	};
}

Step 6. Update SamplePlugin.java: Open SamplePlugin.java in the same /src directory with Activator.java. Start by updating the class with your plugin name (e.g. MyPlugin), your package declarations and constructor(s). Overriding getDisplay() sets the display name in IGB (e.g. "My Operation"). We recommend overriding getName() with a descriptive name (string).

This sample code inherits AbstractAnnotationOperator and implements Operator interface to work as a new annotation operation. For more options refer to the Extension Points section.

public class MyPlugin extends AbstractAnnotationOperator implements Operator {

	// Constructor
	MyPlugin(FileTypeCategory category){
		super(category);
	}

	// Method to determine the internal plugin name
	@Override
	public String getName() {
		return this.category.toString().toLowerCase() +"_my_plugin";
	}


	// Method to determine the display name for the operation
	@Override
	public String getDisplay() {
		return "My Operation";
	}


	// Private method to check if two symmetries are overlapped used by the operate()
	private boolean overlap(BioSeq aseq, SeqSymmetry s0, SeqSymmetry s1) {
		return s0.getSpan(aseq) != null && s1.getSpan(aseq) != null && s0.getSpan(aseq).getMax() > s1.getSpan(aseq).getMin() && s0.getSpan(aseq).getMin() < s1.getSpan(aseq).getMax();
	}


	// Core code for the operation which loops over input symmetries and return the overlapped ones
	@Override
	public SeqSymmetry operate(BioSeq aseq, List<SeqSymmetry> symList) {
		SimpleSymWithProps result = new SimpleSymWithProps();
		result.setProperties(new HashMap<String,Object>());
		TypeContainerAnnot t0 = (TypeContainerAnnot)symList.get(0);
		TypeContainerAnnot t1 = (TypeContainerAnnot)symList.get(1);
		result.setProperty("type", t0.getType() + " " + getName());

		for (int i = 0; i < t0.getChildCount(); i++) {
			SeqSymmetry s0 = t0.getChild(i);
			for (int j = 0; j < t1.getChildCount(); j++) {
				SeqSymmetry s1 = t1.getChild(j);
				if (overlap(aseq, s0, s1)) {
					result.addChild(s0);
					result.addSpan(s0.getSpan(aseq));
					break;
				}
			}
		}
		return result;
	}

You can refer more operations in plugins or com.affymetrix.genometryImpl.operator package in core folder.

Step 7. Update MAINFEST.BASE: Directly under the template /src (close /com) [MyPlugin] folder, update the following highlighted fields in for MAINFEST.BASE.

• Bundle-Name - change to your plugin name
• Bundle-SymbolicName - change to your package path
• Bundle-Version - change to your plugin version
• Bundle-Activation - change to your Activator path (e.g. com.myorg.myplugin.Activator)
• Import-Package - include all the classes your are using in your source code

Step 8. Update ant.properties: Also found under the template /src [MyPlugin] folder, update the highlighted fields as follows.

...

• name=\[your plugin name\]unmigrated-wiki-markup
• project=\[your plugin name\]
• classpath is updated with the necessary paths; refer to the project build.xml for the actual paths listed, i.e. the path for igb_service, windows_service, etc.

Step 9. Update build.properties for the project: Under the IGB project folder(not the build.properties file in your plugin folder), open the build.properties file:

...

• Next, using a command line prompt, navigate to the plugins IGB_HOME folder and run the following command (Enter your svn password as necessary.):

...

*Step 4. Move the .jar and .xml files to your plugin directory:* There should be 2 generated files in IGB_HOME/plugins/ext, _\[MyPlugin\].jar_ and _repository.xml_. Move these files to your plugin repository folder (local or remote HTTP server). Make sure to cut these files from from the IGB_HOME/plugins/ext folder, or delete after copying.

Step 5 (optional): Revert IGB code: You can now revert all of the code changes you have made, if you wish, or simply change the name of the plugin in all appropriate code locations to create files for another plugin.

...