l0o0 / zotero-addon-template-1

An addon/plugin template for Zotero.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Zotero Addon Template

This is an addon/plugin template for Zotero.

Documentation(Chinese, provides English translation)

πŸ‘You are currently in bootstrap extension mode. To use overlay mode, plsase switch to overlay branch in git.

πŸ‘ Watch this repo so that you can be notified whenever there are fixes & updates.

Features

  • TypeScript support;
  • Build addon settings and versions automatically;
  • Build and reload code in Zotero automatically;
  • Release to GitHub automatically(using release-it);
  • Extensive skeleton;
  • Some sample code of UI and lifecycle.
  • ⭐Compatibilities for Zotero 6 & Zotero 7.(using zotero-plugin-toolkit)

Quick Start Guide

  • Fork this repo;
  • Git clone the forked repo;
  • Enter the repo folder;
  • Modify the settings in ./package.json, including:
  version,
  author,
  description,
  homepage,
  config {
    releasepage,
    updaterdf,
    addonName,
    addonID,
    addonRef
  }

Be careful to set the addonID and addonRef to avoid confliction.

  • Run npm install to set up the plugin and install dependencies. If you don't have NodeJS installed, please download it here;
  • Run npm run build to build the plugin. The xpi for installation and the built code is under builds folder.

Plugin Life Cycle

  1. When install/enable/startup triggered from Zotero, bootstrap.js > startup is called
    • Wait for Zotero ready
    • Prepare global variables ctx. They are available globally in the plugin scope
    • Load index.js (the main entrance of plugin code, built from index.ts)
    • Register resources if Zotero 7+
  2. In the main entrance index.js, the plugin object is injected under Zotero and events.ts > onInit is called.
    • Initialize anything you want, including notify listeners, preference panes(initPrefs), and UI elements(initViews).
  3. When uninstall/disabled triggered from Zotero, bootstrap.js > shutdown is called.
    • events.ts > onUninit is called. Remove UI elements(unInitViews), preference panes(uninitPrefs), or anything created by the plugin.
    • Remove scripts and release resources.

Examples

See https://github.com/windingwind/zotero-plugin-toolkit for more detailed API documentations.

Menu (file, edit, view, ...) & Right-click Menu (item, collection/library)

File Menu

image

https://github.com/windingwind/zotero-addon-template/blob/574ce88b9fd3535a9d062db51cf16e99dda35288/src/views.ts#L52-L60

Item Menu

image

https://github.com/windingwind/zotero-addon-template/blob/574ce88b9fd3535a9d062db51cf16e99dda35288/src/views.ts#L23-L51

insertMenuItem resolved the input object and inject the menu items.

You can choose an anchor element and insert before/after it using insertPosition and anchorElement. Default the insert position is the end of the menu.

Preference, for both Zotero 6 and Zotero 7 (all in bootstrap)

Zotero 6 doesn't support preference pane injection in bootstrap mode, thus I write a register for Zotero 6 or lower.

You only need to maintain one preferences.xhtml which runs natively on Zotero 7 and let the plugin template handle it when it is running on Zotero 6.

Zotero 7
Zotero 6

https://github.com/windingwind/zotero-addon-template/blob/574ce88b9fd3535a9d062db51cf16e99dda35288/src/views.ts#L63-L82

Call registerPrefPane when it's on Zotero 6.

Note that <preferences> element is deprecated. Please use the full pref-key in the elements' preference attribute. Like:

<checkbox label="&zotero.__addonRef__.pref.enable.label;" preference="extensions.zotero.__addonRef__.enable"
/>

The elements with preference attributes will bind to Zotero preferences.

Remember to call unregisterPrefPane() on plugin unload.

https://github.com/windingwind/zotero-addon-template/blob/574ce88b9fd3535a9d062db51cf16e99dda35288/src/views.ts#L88-L90

Create Elements API

The plugin template provides new APIs for bootstrap plugins. We have two reasons to use these APIs, instead of the createElement/createElementNS:

  • In bootstrap mode, plugins have to clean up all UI elements on exit (disable or uninstall), which is very annoying. Using the createElement, the plugin template will maintain these elements. Just removeAddonElements on exit.
  • Zotero 7 requires createElement()/createElementNS() β†’ createXULElement() for remaining XUL elements, while Zotero 6 doesn't support createXULElement. Using createElement, it switches API depending on the current platform automatically.

There are more advanced APIs for creating elements in batch: creatElementsFromJSON. Input an element tree in JSON and return a fragment/element. These elements are also maintained by this plugin template.

Extra Column in Library

Using Zotero Plugin Toolkit:ItemTreeTool to register an extra column in src/views.ts.

this._Addon.toolkit.ItemTree.registerExample();

This will register a column with dataKey test. Looks like:

image

Remember to unregister it when exiting.

this._Addon.toolkit.ItemTree.unregister("test");

Directory Structure

This section shows the directory structure of a template.

  • All .js/.ts code files are in ./src;
  • Addon config files: ./addon/chrome.manifest, ./addon/install.rdf;
  • UI files: ./addon/chrome/content/*.xul. The overlay.xul also defines the main entrance;
  • Locale files: ./addon/chrome/locale/[*.dtd, *.properties];
  • Resource files: ./addon/chrome/skin/default/__addonRef__/*.dtd;
  • Preferences file: ./addon/chrome/defaults/preferences/defaults.js;

    Don't break the lines in the defaults.js

β”‚  .gitignore
β”‚  .release-it.json # release-it conf
|  tsconfig.json    # https://code.visualstudio.com/docs/languages/jsconfig#
β”‚  build.js         # esbuild
β”‚  LICENSE
β”‚  package.json     # npm conf
β”‚  README.md        # readme
β”‚  update.rdf       # addon update
β”‚
β”œβ”€.github           # github conf
β”‚
β”œβ”€addon             # addon dir
β”‚  β”‚  chrome.manifest  #addon conf
β”‚  β”‚  install.rdf   # addon install conf
β”‚  β”‚  bootstrap.js  # addon load/unload script, like a main.c
β”‚  β”‚
β”‚  └─chrome
β”‚      β”œβ”€content    # UI
β”‚      β”‚  β”‚  preferences.xhtml
β”‚      β”‚  β”‚
β”‚      β”‚  β”œβ”€icons
β”‚      β”‚  β”‚      favicon.png
β”‚      β”‚  β”‚      favicon@0.5x.png
β”‚      β”‚  β”‚
β”‚      β”‚  └─scripts
β”‚      └─locale     # locale
β”‚         β”œβ”€en-US
β”‚         β”‚      overlay.dtd
β”‚         β”‚      addontemplate.properties
β”‚         β”‚
β”‚         └─zh-CN
β”‚         |      overlay.dtd
β”‚         β”‚      addontemplate.properties
β”‚
β”œβ”€builds            # build dir
β”‚  └─.xpi
β”‚
└─src               # source code
    β”‚  index.ts     # main entry
    β”‚  module.ts    # module class
    β”‚  addon.ts     # base class
    β”‚  events.ts    # events class
    β”‚  views.ts     # UI class
    β”‚  locale.ts    # Locale class for properties files
    └─ prefs.ts     # preferences class

Build

# A release-it command: version increase, npm run build, git push, and GitHub release
# You need to set the environment variable GITHUB_TOKEN https://github.com/settings/tokens
# release-it: https://github.com/release-it/release-it
npm run release

Alternatively, build it directly using build.js: npm run build

Build Steps

  1. Clean ./builds
  2. Copy ./addon to ./builds
  3. Esbuild to ./builds/addon/chrome/content/scripts
  4. Replace __buildVersion__ and __buildTime__ in ./builds/addon
  5. Zip the ./builds/addon to ./builds/*.xpi

Debug

  1. Copy zotero command line config file. Modify the commands.
cp zotero-cmd-default.json zotero-cmd.json
  1. Setup addon development environment following this link.

  2. Build addon and restart Zotero with this npm command.

  3. Launch Firefox 60

  4. In Firefox, go to devtools, go to settings, click "enable remote debugging" and the one next to it that's also about debugging(or press shift+F8).

  5. In Zotero, go to setting, advanced, config editor, look up "debugging" and click on "allow remote debugging"

  6. In Firefox, click the hamburger menu in the top right -> web developer -> Connect...

  7. Enter localhost:6100

  8. Connect

  9. Click "Inspect Main Process"

npm run restart

You can also debug code in these ways:

Development

Search for a Zotero API
Zotero docs are outdated or incomplete. Searching the source code of Zotero is unavoidable.
Clone https://github.com/zotero/zotero and search the keyword globally. You can search the UI text in .xul/.dtd files, and then search the keys of the text value in .js/.xul files.

⭐The zotero-types provides most frequently used Zotero APIs. It's included in this template by default.

Disclaimer

Use this code under AGPL. No warranties are provided. Keep the laws of your locality in mind!

If you want to change the license, please contact me at wyzlshx@foxmail.com

Part of the code of this repo refers to other open-source projects within the allowed scope.

  • zotero-better-bibtex(d.ts)

Zotero Addons Build with the Template

About

An addon/plugin template for Zotero.

License:GNU Affero General Public License v3.0


Languages

Language:TypeScript 60.6%Language:JavaScript 33.7%Language:HTML 5.7%