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.
Now with the latest git_bindings we no longer use git_pull which would
do a fetch + merge. It's good that these two actions are separated as
I can then easily replace the git_merge with a smarter version
implemented in git.
Also, that way in the future, the git_bindings plugin will only be used
for git_fetch and git_push for SSH. Everything else can be handled by
dart_git.
This way we can swap the merge out easily for our own custom merge code.
Also, this makes it easier to do a merge as a way of migrating.
This commit probably breaks stuff on ios
It makes the entire code base far more complicated and the round trip to
get the directory really isn't that much. This is a massive
micro-optimization for very little benefit.
Nodes which have a pos < 0, are no longer force directed. This make the
graph behave strangely. It's better to just push it a little further
from the edge.
The one in the current stable branch is buggy and the scaling doesn't
work reliably.
This is from the beta branch.
This breaks selecting a node and being able to move it easily.
