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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:translator_best_practices [2008/11/11 05:38]
dev:translator_best_practices [2017/11/12 19:53] (current)
Line 1: Line 1:
-When writing translators,​ using the [[/support/debug_output|debug console]] is essentialAny output from the translator can be dumped to the debug console using <code>Zotero.Utilities.debug("​hello world!"​);​</code>+<​html><​p id="​zotero-5-update-warning"​ style="​color:​ red; font-weight:​ bold">​We’re 
 +in the process of updating the documentation for 
 +<a href="​https:​//www.zotero.org/​blog/​zotero-5-0"​>​Zotero ​5.0</a>Some documentation 
 +may be outdated in the meantime. Thanks for your understanding.</​p>​</html>
-The functions ''​Zotero.Utilities.HTTP.doGet'' ​and ''​Zotero.Utilities.processDocuments''​ run asynchronously. ​ In order to allow them to complete before moving along, follow either function with ''​Zotero.wait()''​ and include ''​Zotero.done()''​ as the onDone in order to signal the translator that it has completed its asynchronous operations.+ 
 +See [[dev:​translators#​recommendations_for_translator_authors|Recommendations for translator authors]] ​and [[dev:​translators:​coding|Translator Coding]].
dev/translator_best_practices.txt · Last modified: 2017/11/12 19:53 (external edit)