React widget + preparing for a new backend

In this version, the widget goes now to react (at last), and there's a bunch of changes in the backend. The changes are the following:

• The widget has been rewritten from CoffeeScript to JS (JSX with React).
• The backend does not return songChanged attribute anymore, the API consumer should detect this manually (see code below for an example of detecting this in TypeScript).
• The player artwork and all players artwork now redirect to a new artwork endpoint, and also updates the artwork cache item if it should be updated.
• The artwork cache item now does not depend on the player.
• A new endpoint was added: the artwork endpoint. Receives an album and artist (or album artist) and checks in the cache for this item and returns the artwork.

I'm preparing a change to the backend using Swift and Vapor, compatible with Linux. Future versions will have two options to choose: Objective-C backend and Swift backend. The Objective-C backend will only maintained for bug fixes.

const hasMetadataUpdated = (current: SongMetadata?, previous: SongMetadata?) => (
  (!current && previous) ||
  (current && !previous) ||
  current.name !== previous.name ||
  (current.albumArtist || current.artist) !== (previous.albumArtist || previous.artist) ||
  current.album !== previous.album
);

Fix cache for images

v1.5.1

Fix some caching bugs

Show only one player, or all

Big refactor in the service daemon that allows to have an HTTP API with different methods. And this allows you to show only one player instead of the three supported. Even you could have twice the widget to show the first one player and the second other player :)

You will find the option to change that at the beginning of the index.coffee file, named playerApp.

Remeber to update the service daemon by installing it with the install script.

Support for Mojave

In Mojave, the service stopped working due to a hidden bug. Now it is fixed for every macOS version, and doesn't crash on 10.14.

More stable backend

There's not much to describe but the new approach to run the backend. Now it will be a daemon (or Launch Agent in the mac terminology) that will run when your user logs in.

To simplify the installation of the daemon, but giving you control about the process, a script is provided to install the daemon. It's easy: when installed, go to Playbox.widget and you'll see the script install_service.command. If you open it, a terminal will show and the script will install the daemon. Should go fine. And now, you have the backend properly installed.

Have fun :)

Stability and bug fixes

v1.3.1

Update README for background service

Better getting of the metadata

v1.3

My work, to GitHub