Some % of the users are badly affected by a bug, which I cannot seem to
reproduce, maybe this debug message will help.
Also, I accidentally shipped it with the bottom bar disabled.
Earlier we had one folder 'journal_local', when the remote would be
setup a new folder called 'journal' would be created, and each all the
files would be copied over. This meant the local history was being
destroyed.
Now, we only have 1 folder 'journal', and on 'cloning', we add the url
as a remote, and do a git fetch + merge.
This simplifies everything drastically, and opens the door for multiple
remotes.
Stop it being a singleton. This means it needs to be passed around a
lot. This sucks, but it's how it should be. I shouldn't be using a
global variable to get around this.
This is needed as Settings will soon become repo specific when we
support multiple repos.
This breaks saving the settings in a file, that feature was toggled off
anyway. It needs to be thought over again.
We now show how the bottom menu bar will look inside the settings. This
is so much nicer. Later, I can add more options to configure exactly
what icons are visible and what they do.
Configuring how the metadata should be saved really seems like more of a
basic feature as it allows you test GitJournal's compatibility with your
favorite desktop client or for static website generation.
The screenshots package had to have some override because of a
dependency conflict. Also, while the splash screen still works, I'm not
sure if I'm doing the right thing any more.
I'm calling this event gj_app_update as firebase automatically sends an
app_update event. This is being done so that I can easily remove
firebase analytics in the future.
Open Collective is better as it allows one time donations, but I don't
have the bandwidth the manage that and GitHub Sponsors. It seems easier
to just manage one, and people who want to make a one time donation can
use Paypal.
