-
Notifications
You must be signed in to change notification settings - Fork 304
Komodo 9 Add on Changes
Some existing Komodo 8 add-ons will need to be updated in order to work in Komodo 9. These type of add-ons that will require changes in order to function correctly in Komodo 9.
Extensions that use a UDL lexer (i.e. the extension contains an lexers directory), you'll need to use an explicit xpcom category in the chrome.manifest file to register the lexer(s). If your using the Komodo koext sdk tool - then this will be done for you automatically. The format of the xpcom category entry is:
category udl-lexers extension_id 1
Where extension_id is the add-on id name (from the install.rdf file) and 1 is just an unused category parameter.
Here is an example:
category udl-lexers [email protected] 1
Extensions that provide a toolbox (i.e. extension contains a tools directory), you'll need to use an explicit xpcom category in the chrome.manifest file to register the toolbox. If your using the Komodo koext sdk tool - then this will be done for you automatically. The format of the xpcom category entry is:
category toolbox extension_id 1
Where extension_id is the add-on id name (from the install.rdf file) and 1 is just an unused category parameter.
Here is an example:
category toolbox [email protected] 1
Extensions that have codeintel api catalogs (i.e. the extension contains an apicatalogs directory), you'll need to use an explicit xpcom category in the chrome.manifest file to register the catalog(s). If your using the Komodo koext sdk tool - then this will be done for you automatically. The format of the xpcom category entry is:
category apicatalogs extension_id 1
Where extension_id is the add-on id name (from the install.rdf file) and 1 is just an unused category parameter.
Here is an example:
category apicatalogs [email protected] 1
Extensions that have xml api catalog (i.e. the extension contains an xmlcatalogs directory), you'll need to use an explicit xpcom category in the chrome.manifest file to register the catalog(s). If your using the Komodo koext sdk tool - then this will be done for you automatically. The format of the xpcom category entry is:
category xmlcatalogs extension_id 1
Where extension_id is the add-on id name (from the install.rdf file) and 1 is just an unused category parameter.
Here is an example:
category xmlcatalogs [email protected] 1
Unit test harnesses now require an explicit xpcom category in the chrome.manifest file to register themselves. Format of the xpcom category entry is:
category unittest-harness relpath extension_id
Where extension_id is the add-on id name (from the install.rdf file) and relpath is the relative path of the Python file under the add-on base directory.
Here is an example:
category unittest-harness harness/nose/as_node_harness.py [email protected]