A note has a parent which is the physical folder it is inside, and a
parent folder which it is being displayed inside. It's useful to have
the latter as that can be used to display the next note - in the case of
the Journal Editor, and open the graph view as well.
This allows you to long press on a note and select it, thereby allowing
you to perform actions on it, without opening the note.
This is disabled for note, as it isn't completely implemented. I'm not
sure how to pass down the informatin on which Note is selected.
Expose the noteTapped and noteLongPressed functions from all the views.
This will be required in the future as we support selecting a note (or
multiple notes) in order to perform some action on it.
Right now selecting a note means opening the Note Editor.
This reverts commit 303192d9d575b26a77a00f7a62212f310ec1e329.
This reverts commit cd9d128b47ed523036f7ae1232ec7adcf04ed8a9.
GitJournal is used by non-English speakers (a lot in China and Russia)
and while we don't support those languages completely, we do support
them a little bit. I don't want to loose this functionality. It would be
better for us to fix the bug in intl.
https://github.com/dart-lang/intl/issues/266
This is strange since Intl.getLocale() returns 'en_US' in my case.
Currently, GitJournal only supports 'english' anyway, so this shouldn't
be a big problem.
This basically asserts if we move to a route without a name. This way
I'll always catch when a route doesn't have a name, and I can start
getting better analytics on which screens are used most frequently.
Just with a fixed height card. This way we save on lots of code
duplication, specially as each of these views will become more complex
as we add dismissable, animations and selectable notes.
This contains the default editor / view / sortingMode / etc. For now the
folder settings are shared among all Folders. But the idea is that we
should be able to set different settings per folder (real or virtual)
It still has a long way to go to being usable. But I rather have in
integrated so I can slowly keep improving it, and for some users to try
it out. It is clearly marked as experimental.
The customization screen is very ugly and this entire thing feels
extremely hacky with the abstractions leaking out everywhere. However,
it does work.
I'll clean it up another day.
I need to merge it into the StandardView. The more I think about it, the
more this view doesn't make sense. Specially since I need to add the
same extra configuration options in both views.
Otherwise we get an exception. This happens when a note has not loaded
and we're trying to render it. Ideally we should handle those cases with
some kind of animation instead of the current approach.
