Firefox add-on for Hatch

[Galen Charlton]

It would be nice to have a Firefox add-on for Hatch, similar to the Chrome extension, that is available from the FF add-on store.

Tasks include:

- writing the extension (which hopefully will mostly be a matter of porting the Chrome extension)
- setting up a developer account (see https://addons.mozilla.org/en-US/developers/)
- creating FF versions of the logo and images if the ones devised for the Chrome extension won't do

[Terran McCanna (tmccanna)]

+1

[Chris Sharp (chrissharp123)]

I've done some work on this today, available at http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/csharp/lp1731922_firefox_hatch. Hoping to get some other eyes on this and make some progress towards a publishable add-on for the Firefox site.

[Jason Boyer (jboyer)]

I have done battle with Firefox Native Messaging support and have finally found myself on the other side. Here is a branch that modifies the batch file, installer, and adds a new manifest for the NativeMessagingHosts entry. The latter is necessary because FF flames out if you try to mix Chrome and FF support in a single manifest while Chrome just Does The Thing. :-/

http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/jboyer/lp1731922_ff_support

Note it also makes some minor changes to the extension code, so the FF extension currently in place will need to be updated. The Chrome version isn't as urgent but should also be kept in sync. Chrome gives a warning when loading an extension manifest with the (required by FF) applications key, so if that's a showstopper on the Chrome side then we'll ALSO need to have separate extension manifests. :(

Finally, Firefox has no way to auto-install a regular extension from the addon site through the Windows registry the way Chrome does. (If you install an extension through the registry it has to be locally installed and can't be auto-updated). For that reason we should probably include links to both extensions on the Hatch workstation admin page so users can find them with a minimum of hassle. But that's for another LP...

[Chris Sharp (chrissharp123)]

Signoff branch here:

http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/csharp/lp1731922_ff_support_signoff

[Bill Erickson (berick)]

Removing pullrequest pending icon updates and Linux install doc updates demonstrating how to copy the org.evergreen_ils.hatch.*.json to the/correct/path/org.evergreen_ils.hatch.json -- Chrome at least requires the name of the .json file to match the name of native messaging extension ("org.evergreen_ils.hatch") on Mac/Linux.

[Jason Boyer (jboyer)]

I've updated the branch with the new Evergreen icon and the install doc explains that the manifest file name should be changed as part of the install. I haven't updated the FF extension with the final images and new toolbar icon because I wasn't sure what the final version number update would be and there's no point in submitting rapid fire updates that have no actual changes.

http://git.evergreen-ils.org/?p=working/Hatch.git;a=shortlog;h=refs/heads/user/jboyer/lp1731922_ff_support working/user/jboyer/lp1731922_ff_support

[Bill Erickson (berick)]

I can do a round of Chrome testing to make sure nothing broke, but my preference is someone else sign off on the Windows + Firefox bits before I merge to Hatch.

[Geoff Sams (gsams)]

After testing, the file does indeed work for Firefox on Windows. However, it also introduces a change to the extension file name for chrome. The current webstore version of the chrome hatch extension is looking for org.evergreen_ils.hatch.json and this introduces a change to org.evergreen_ils.hatch.chrome.json. This would either require the web store version to be updated to account for that, or to leave it as the older filename.

In either case, the Firefox part works, and I can sign off on that part with my name and email. Geoff Sams, <email address hidden>

[Bill Erickson (berick)]

My tests all succeeded.

* I merged the code to Hatch master.
* Posted a new Windows build at:

https://evergreen-ils.org/downloads/Hatch-Installer-0.2.0.exe

* Posted a new extension build to the Chrome store. Should be available within the hour.

Thanks Chris, Jason and Geoff!