This doesn't seem to move it to the SD card, but it does move it to a
public location. This is an Android specific feature.
Not sure if this is allowed with Android 11
Related to #99Fixes#154
Left over from an experiment. Logs only stay on the device, so this
wasn't a problem, but it stays constant on Android across installs. It
would be nice to use this ID instead the random ID that we generate, but
that could be counted as personally identifyable info. I'm not too sure.
We now infer this by checking if the directory exists, and by reading
the git config. It's a bit slower, but it's a far better method. I can
add a cache later, if it turns out to be too slow.
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.
