Differences

This shows you the differences between two versions of the page.

--- dev:zotero_2.1_and_zotero_standalone_for_developers [2011/02/05 19:53] – simon
+++ dev:zotero_2.1_and_zotero_standalone_for_developers [2011/02/08 23:48] – simon
@@ Line 33: / Line 33: @@
 <code>new Zotero.Translate.Web();</code>
-====== Changes in Zotero Standalone (not yet implemented) ======
+===== Locate Engines =====
+Zotero 2.1b6 and later support extensible locate engines. For further details, see [[Creating Locate Engines using OpenSearch]].
+====== Changes for Zotero Connectors (not yet implemented) ======
 ===== Changes to translators =====
 Zotero Everywhere will soon allow translators to operate outside of Firefox/XULRunner. Legacy translators can still run inside Zotero Standalone, but will require that Zotero Standalone is running to operate. This will require the following code changes:
   * Firefox-specific JavaScript must be avoided. This includes
-    * E4X
     * "for each" loops
     * array comprehensions
     * destructuring assignment
     * several other features
+  * Some E4X functionality may not be available, although as much as possible will be preserved. As of Zotero 2.1b6, Zotero also offers DOM XML interfaces to translators.
-  * Zotero.Utilities.retrieveDocument() and Zotero.Utilities.retrieveSource() should be avoided if possible. The former is unlikely to work outside of Firefox, while the latter may freeze the browser interface during operation. Zotero.Utilities.processDocuments(), Zotero.Utilities.HTTP.doGet(), and Zotero.Utilities.HTTP.doPost() will continue to be available as alternatives.
+  * Zotero.Utilities.retrieveDocument() and Zotero.Utilities.retrieveSource() should be avoided if possible. There may be workarounds that allow these to operate outside of Firefox, but they will be extremely inefficient. Zotero.Utilities.processDocuments(), Zotero.Utilities.HTTP.doGet(), and Zotero.Utilities.HTTP.doPost() will continue to be available as alternatives.
-  * Translate.getTranslatorObject() should now be called with a callback function as an argument, which will receive the translator object when it is available.
+  * Translate.getTranslatorObject() should now be called with a callback function as an argument, which will receive the translator object when it is available. This is backwards compatible with Zotero 2.1b6 and later.
-  * Zotero.selectItems() should now be called with a callback function as an argument, which will receive the list of selected items when it is available. Translators may still use Zotero.selectItems() synchronously, but this will require that the first part of the translator be executed twice.
+  * Zotero.selectItems() should now be called with a callback function as an argument, which will receive the list of selected items when it is available. Translators may still use Zotero.selectItems() synchronously, but this will require that the first part of the translator be executed twice. This is backwards compatible with Zotero 2.1b6 and later.