Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
dev:zotero_2.1_and_zotero_standalone_for_developers [2011/02/08 23:48] – simon | dev:zotero_2.1_and_zotero_standalone_for_developers [2011/04/20 10:11] – rmzelle | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | See [[dev/ |
- | + | ||
- | ===== Changes to citation API ===== | + | |
- | + | ||
- | With the introduction of citeproc-js, | + | |
- | developers should use Zotero.Style.csl to acquire a citeproc-js engine instance for citation formatting. < | + | |
- | + | ||
- | ===== Changes to interface-related code ===== | + | |
- | + | ||
- | Zotero as a tab and Zotero Standalone | + | |
- | + | ||
- | < | + | |
- | + | ||
- | ===== Changes to translators ===== | + | |
- | + | ||
- | * Several functions in Zotero.Utilities have been eliminated, as they were essential duplications of built-in JavaScript methods. | + | |
- | + | ||
- | * Zotero.configure() and Zotero.displayOptions() no longer exist. Instead, translators should specify config and display options in the metadata block at the top of the translator, e.g. < | + | |
- | " | + | |
- | [...] | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | }</ | + | |
- | + | ||
- | * It is no longer necessary to specify " | + | |
- | + | ||
- | * Import and export translators now show determinate progress bars. By default, Zotero computes progress by the percentage of the file read for import, or the percentage of items retrieved using Zotero.nextItem() for export. Translators can override this by calling Zotero.setProgress(percentage) to set the percentage the progress bar displays, or Zotero.setProgress(null) to show an indeterminate indicator. | + | |
- | + | ||
- | ===== Changes to translate interface ===== | + | |
- | + | ||
- | New code should create new instances of the translate interface using type-specific constructors, | + | |
- | + | ||
- | < | + | |
- | + | ||
- | ===== 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/ | + | |
- | + | ||
- | * Firefox-specific JavaScript must be avoided. This includes | + | |
- | * "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. There may be workarounds that allow these to operate outside of Firefox, but they will be extremely inefficient. Zotero.Utilities.processDocuments(), | + | |
- | + | ||
- | * 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, | + |