Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "XQuery Development Tools/Where to Start"
Line 50: | Line 50: | ||
* <code>ZorbaSemanticValidator</code> | * <code>ZorbaSemanticValidator</code> | ||
* <code>MarkLogicSemanticValidator</code> | * <code>MarkLogicSemanticValidator</code> | ||
− | |||
|- | |- | ||
! URI Resolving | ! URI Resolving | ||
Line 65: | Line 64: | ||
* <code>ZorbaUriResolver</code> | * <code>ZorbaUriResolver</code> | ||
* <code>MarkLogicUriResolver</code> | * <code>MarkLogicUriResolver</code> | ||
+ | |- | ||
+ | ! Vendor code templates | ||
+ | | | ||
+ | * Vendors can provide their own templates (code snippets) to be added to the default set of templates shipped with the core of XQDT. | ||
+ | | | ||
+ | * org.eclipse.wst.xquery.ui.<b><i>your_own_plugin</i></b> | ||
+ | | | ||
+ | * <code>ScriptCompletionProposalComputer</code> | ||
+ | * add the <code>org.eclipse.dltk.ui.scriptCompletionProposalComputer</code> extension point in <b><i>your_own_plugin</i></b> and provide a reference to your implementation of <code>ScriptCompletionProposalComputer</code>. See the Zorba implementation for the complete extension point implementation. | ||
+ | * <code>ScriptTemplateCompletionProcessor</code> | ||
+ | * <code>ScriptTemplateAccess</code> (reads and caches the templates from disk) | ||
+ | * <code>ScriptTemplateContextType</code> | ||
+ | * add your <code>ScriptTemplateContextType</code> to the <code>org.eclipse.ui.editors.templates</code> extension point in <b><i>your_own_plugin</i></b>. In the same extension point, provide also the .xml and .properties files where the templates will be read from. See the Zorba implementation for the complete extension point implementation. | ||
+ | * <code>ScriptTemplateContext<code> (allows you to resolve template variables) | ||
+ | | | ||
+ | * plug-in <code>org.eclipse.wst.xquery.ui.zorba</code> | ||
+ | * <code>ZorbaTemplateProposalComputer</code> | ||
+ | * <code>ZorbaTemplateCompletionProcessor</code> | ||
+ | * <code>ZorbaTemplateAccess</code> | ||
+ | * <code>ZorbaTemplateContentType</code> | ||
+ | * <code>ZorbaTemplateContext<code> | ||
|- | |- | ||
|} | |} |
Revision as of 09:03, 28 May 2010
What is the "Where to Start" page?
This page gathers a list of features of XQDT and the place in the project where this feature is implemented or where the developer should first look and start understanding and debugging the functionality.
Feature table
NOTE: For all the classes below we have omitted the fully qualified name to keep the descriptions shorter. For example, XQDTInterpreterInstallType
refers to org.eclipse.wst.xquery.launching.XQDTInterpreterInstallType
. Eclipse helps you find these types with the "Open Type" dialog (available under the "Navigate" menu or by pressing the key combination: Ctrl-Shift-T). In case you find more classes having the same name (though not the case so far), just choose the one from our project, that is, having a package name starting with: org.eclipse.wst.xquery
.
Feature name | Feature description | Plug-ins involved | Need to implement | Sample implementation |
---|---|---|---|---|
New XQuery Processor Type |
|
|
|
|
Semantic Checker |
|
|
|
|
URI Resolving |
|
|
|
|
Vendor code templates |
|
|
|
|