Differences

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

--- dev:client_coding [2019/02/08 06:17] – [Plugin Development] adomasven
+++ dev:client_coding [2020/09/27 05:04] – [Zotero Client Coding] dstillman
@@ Line 1: / Line 1: @@
-<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>
 ====== Zotero Client Coding ======
   * [[dev/Source Code]]
-    * Learn where you find the Zotero source code, how to use the issue tracker and how to contribute code.
+    * Learn where you find the Zotero source code, how to use the issue tracker, and how to contribute code.
+  * [[dev/client_coding/Building the Standalone Client|Building Zotero]]
+    * Learn how to build the Zotero client from scratch.
   * [[dev/client_coding/Coding Guidelines]]
     * When you write code for the Zotero project, there are some naming and formatting preferences we ask you to follow.
-  * [[dev/Modifying Zotero Files]]
+  * Client APIs
-    * Most developers will want to work from a local copy of the Zotero codebase. However, it is also possible to make (small) code changes to your existing Zotero installation. This section will show you how.
+    * [[dev/client_coding/JavaScript API]]
-  * [[dev/client_coding/Connector HTTP Server]]
+      * The Zotero client's internal API
-    * The Connector HTTP Server in the Zotero clients talks to the Chrome, Firefox, and Safari Connector extensions.
+    * [[dev/client_coding/Connector HTTP Server]]
-  * [[dev/client_coding/Building the Standalone Client|Building the Zotero Standalone client]]
+      * The Zotero Connector for Chrome, Firefox, and Safari talk to the HTTP server in the Zotero client.
+    * Word Processor Integration API
+      * Zotero word processor plugins are [[https://developer.mozilla.org/en/XPCOM|XPCOM]] components implementing a small set of interfaces. Development guidelines for these interfaces are described for [[https://github.com/zotero/zotero-libreoffice-integration/|LibreOffice]], [[https://github.com/zotero/zotero-word-for-windows-integration|Word for Windows]], and [[https://github.com/zotero/zotero-word-for-mac-integration|Word for Mac]].
+    * [[dev/client_coding/http_integration_protocol|HTTP Citing Protocol]]
+      * The Google Docs plugin implements the HTTP citing protocol, by performing a sequence of HTTP requests in a transaction. This is the preferred way to provide citing integration with Zotero for document processors.
+    * [[dev/client_coding/LibreOffice Plugin Wire Protocol]]
+      * The LibreOffice plugin implements the word processor integration API by acting as a server for a simple TCP/IP protocol. If out-of-process communication mechanisms such as COM and AppleScript as well as HTTP messaging protocol is not available, the TCP/IP protocol can be used instead.
 ===== Changes Affecting Third-Party Developers =====
@@ Line 34: / Line 36: @@
   * Word Processor Integration API
     * Zotero word processor plugins are [[https://developer.mozilla.org/en/XPCOM|XPCOM]] components implementing a small set of interfaces. Development guidelines for these interfaces are described for [[https://github.com/zotero/zotero-libreoffice-integration/|LibreOffice]], [[https://github.com/zotero/zotero-word-for-windows-integration|Word for Windows]], and [[https://github.com/zotero/zotero-word-for-mac-integration|Word for Mac]].
-  * [[HTTP Citing protocol|dev/client_coding/http_integration_protocol]]
+  * [[dev/client_coding/http_integration_protocol|HTTP Citing Protocol]]
     * The Google Docs plugin implements the HTTP citing protocol, by performing a sequence of HTTP requests in a transaction. This is the preferred way to provide citing integration with Zotero for document processors.
   * [[dev/client_coding/LibreOffice Plugin Wire Protocol]]
     * The LibreOffice plugin implements the word processor integration API by acting as a server for a simple TCP/IP protocol. If out-of-process communication mechanisms such as COM and AppleScript as well as HTTP messaging protocol is not available, the TCP/IP protocol can be used instead.