Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dev:zotero_2.1_and_zotero_standalone_for_developers [2011/02/07 03:57] – simon | dev:zotero_2.1_and_zotero_standalone_for_developers [2017/11/12 19:53] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Changes in Zotero | + | < |
+ | in the process of updating the documentation for | ||
+ | <a href=" | ||
+ | may be outdated in the meantime. Thanks for your understanding.</ | ||
- | ===== Changes to citation API ===== | ||
- | With the introduction of citeproc-js, | + | See [[dev/client_coding/Changes in Zotero |
- | 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 have required us to further abstract the interface layer. While the code for the interface has changed little, and most overlays should continue to work, as of the present Zotero trunk, plug-ins and add-ons should now overlay zoteroPane.xul instead of browser.xul or overlay.xul in chrome.manifest, | + | |
- | + | ||
- | < | + | |
- | + | ||
- | ===== Changes | + | |
- | + | ||
- | * Several functions | + | |
- | + | ||
- | * Zotero.configure() | + | |
- | " | + | |
- | [...] | + | |
- | " | + | |
- | " | + | |
- | " | + | |
- | }</ | + | |
- | + | ||
- | * 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, | + | |
- | + | ||
- | < | + | |
- | ====== 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, | + |