Jump to: navigation, search

Difference between revisions of "DTP Capabilities Location"

(New page: == DTP Capabilities How To == In Galileo, the DTP Capabilities plug-in was included as part of the package process. In Helios, capabilities were pulled out of that process and to be docu...)
 
Line 1: Line 1:
 
+
== DTP Capabilities How To ==
== DTP Capabilities How To ==
+
  
 
In Galileo, the DTP Capabilities plug-in was included as part of the package process. In Helios, capabilities were pulled out of that process and to be documented separately.  
 
In Galileo, the DTP Capabilities plug-in was included as part of the package process. In Helios, capabilities were pulled out of that process and to be documented separately.  
  
The goal of this document is to explain:
+
The goal of this document is to explain:  
  
# Where to find the existing Capabilities plug-in in CVS
+
#Where to find the existing Capabilities plug-in in CVS  
# Or how to implement your own Capabilities for DTP
+
#Or how to implement your own Capabilities for DTP
  
=== Existing Capabilities Plug-in ===
+
=== Existing Capabilities Plug-in ===
  
The existing Capabilities plug-in can be found in CVS...
+
The existing Capabilities plug-in can be found in CVS...  
  
Anonymous CVS server info:
+
Anonymous CVS server info:  
  
 
     * Host: dev.eclipse.org
 
     * Host: dev.eclipse.org
 
     * Repository Path: /cvsroot/datatools
 
     * Repository Path: /cvsroot/datatools
 
     * User: anonymous
 
     * User: anonymous
     * Password: <empty>
+
     * Password: &lt;empty&gt;
 
     * Connection method: pserver
 
     * Connection method: pserver
 
     * Plug-in (within org.eclipse.datatools.build): org.eclipse.datatools.capabilities
 
     * Plug-in (within org.eclipse.datatools.build): org.eclipse.datatools.capabilities
  
Really all that's in this plug-in is the org.eclipse.ui.activities extension point in the plugin.xml at this point.
+
Really all that's in this plug-in is the org.eclipse.ui.activities extension point in the plugin.xml at this point.  
  
=== Capabilities Implementation ===
+
=== Capabilities Implementation ===
  
As mentioned in the last section, really capabilities boil down to the org.eclipse.ui.activities extension. All that the extension does is shut down the DTP plug-ins:
+
As mentioned in the last section, really capabilities boil down to the org.eclipse.ui.activities extension. All that the extension does is shut down the DTP plug-ins:  
  
 
   <extension
 
   <extension
Line 40: Line 39:
 
   </extension>
 
   </extension>
  
More fine-grained disabling of particular plug-ins can be done, but this takes care of the high level "switch" to turn off DTP functionality in the workbench via Capabilities.
+
More fine-grained disabling of particular plug-ins can be done, but this takes care of the high level "switch" to turn off DTP functionality in the workbench via Capabilities.  
  
[[Category:Data Tools Platform]]
+
[[Category:Data_Tools_Platform]]

Revision as of 09:23, 6 April 2010

DTP Capabilities How To

In Galileo, the DTP Capabilities plug-in was included as part of the package process. In Helios, capabilities were pulled out of that process and to be documented separately.

The goal of this document is to explain:

  1. Where to find the existing Capabilities plug-in in CVS
  2. Or how to implement your own Capabilities for DTP

Existing Capabilities Plug-in

The existing Capabilities plug-in can be found in CVS...

Anonymous CVS server info:

   * Host: dev.eclipse.org
   * Repository Path: /cvsroot/datatools
   * User: anonymous
   * Password: <empty>
   * Connection method: pserver
   * Plug-in (within org.eclipse.datatools.build): org.eclipse.datatools.capabilities

Really all that's in this plug-in is the org.eclipse.ui.activities extension point in the plugin.xml at this point.

Capabilities Implementation

As mentioned in the last section, really capabilities boil down to the org.eclipse.ui.activities extension. All that the extension does is shut down the DTP plug-ins:

  <extension
        point="org.eclipse.ui.activities">

<activity

   	  description="%activity.description"
         id="org.eclipse.datatools.capabilities.activity"
         name="%activity.name"/>
   <activityPatternBinding
         activityId="org.eclipse.datatools.capabilities.activity"
         pattern="org\.eclipse\.datatools\..*/.*">
   </activityPatternBinding>
  </extension>

More fine-grained disabling of particular plug-ins can be done, but this takes care of the high level "switch" to turn off DTP functionality in the workbench via Capabilities.