Medical Imaging Interaction Toolkit
2016.11.0
Medical Imaging Interaction Toolkit
|
There are two possible forms of product extension, static and dynamic. Static product extensions directly contain all relevant information about the product. Dynamic product extensions identify a class (an IProductProvider
) which is capable of defining one or more products when queried.
<!ELEMENT extension ((product | provider))>
<!ATTLIST extension
point CDATA #REQUIRED
id CDATA #IMPLIED
name CDATA #IMPLIED>
<!ELEMENT product (property*)>
<!ATTLIST product
application CDATA #REQUIRED
name CDATA #REQUIRED
description CDATA #IMPLIED>
<!ELEMENT property EMPTY>
<!ATTLIST property
name CDATA #REQUIRED
value CDATA #REQUIRED>
details of a product provider
<!ELEMENT run EMPTY>
<!ATTLIST run
class CDATA #REQUIRED>
<extension id="coolProduct" point="org.blueberry.core.runtime.products"> <product name="%coolName" application="coolApplication" description="%coolDescription"> <property name="windowImages" value="window.gif"/> <property name="aboutImage" value="image.gif"/> <property name="aboutText" value="%aboutText"/> <property name="appName" value="CoolApp"/> <property name="welcomePage" value="$nl$/welcome.xml"/> <property name="preferenceCustomization" value="plugin_customization.ini"/> </product> </extension>The following is an example of a dynamic product (product provider) declaration: Following is an example of an application declaration:
<extension id="coolProvider" point="org.blueberry.core.runtime.products"> <provider> <run class="me::CoolProvider"/> </provider> </extension>
IProductProvider
are supplied.
Copyright (c) 2004, 2005 IBM Corporation and others.
All rights reserved. This program and the accompanying materials are made
available under the terms of the Eclipse Public License v1.0 which
accompanies
this distribution, and is available at
http://www.eclipse.org/legal/epl-v10.html