This patch removes a few restriction about when the Android build
workflows run. In particular, we want to run workflows…
- If the workflows themselves change because that could mean that the
output changes.
- If the deployment page template changes because that would mean that
the published page needs to be updated.
We could still exclude a few specific files if we wanted to, but they
should rarely change and it's probably not worth the effort of keeping
those lists updated.
This page automatically builds the Android app from the latest commit on
the branch master, generates a test page and publishes it to GitHub
Pages as a nice way for non-developers to get the latest app version for
testing without having to build it themselves.
This page might need the pages source set to GitHub Actions at
Settings → Pages → Build and deployment → Source.
This patch adds a GitHub Actions workflow which will automatically run
through all steps to build the Android version of the app. This is an
easy way of catching major build errors in pull requests or pushed
commits.
Additionally, this uploads the Android APK as build artifact. This
allows anyone to easily download any build for a while. That will make
it much easier for non-developers to participate in testing a new
version or a specific test since the no longer have to wait for a new
release.
The build artifacts are a bit tricky to find, but they are easy to point
out if anyone asks.
The account setting list the connection name which is the server address
directly followed by the username. This is then followed by a field
repeating the username again.
This duplication of information is nor really helpful, which is why this
patch replaces this with two fields containing just the two information:
host address and username.
This patch implements a generic way of re-opening the player for the
book you last listened to. This is especially handy when first opening
the app and you can restart playback with a single click.
The player is opened only if no other book is already open in the
player. It will not overwrite or replace playbacks or player already in
progress.
The player is opened paused. No automatic playback since that could be
really annoying.
This closes#494
This patch improves word wrapping for the description text in book
details by justifying the text block and allowing for words to be
wrapped by automatically inserting hyphens if necessary.
This causes the description box to look far less ragged on the right
edge which I think helps the overall cleanliness of the look.
Unfortunately the app's/browser's aren't as good as e.g. the TeX
algorithm for hyphening and there are JavaScript libraries which seem to
reimplement that. But this is already a significant step up and far less
work for something which is not the main focus of this app.
This patch adds a heavily blurred version of the cover image as
background to the cover image area in the book details.
This looks especially nice on larger devices like tablets.
Running `npm ci` you always get a warning about an old lock-file format
being used:
```
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
```
This patch simply re-generates the file by removing the old one and
running`npm install`. That gets rid of the warning.
This patch is a follow up to the discussion from #559 about potentially
simplifying progress interactions.
This patch essentially reduces the interactions to two simple options
which allow users to always marks books as finished or discard the
progress and thus mark them as not yet started with a single
interaction:
- If users have already listed to the book, regardless of the state of
the progress (finished, half way through, …), they get an option to
discard the progress. This replaces the additional “mark as not
finished” option but it should still be clear to users what happens.
- If a book is not yet finished, regardless of the state of the progress
(not yet started, half way through), users get a “mark as finished”
option which sets the progress to 100%.
This is hopefully a bit simpler than what we have now but also doesn't
require a user to figure out that you need to first mark a book as
finished to be able to discard the progress.
