Initial Work and Concept

I have invited you @bhdouglass and @Danfro to this, so you can peek / suggest / comment / push / pussicat or kill kill in the repo (:D)

The basic idea of the app should be to sync online/local notes.

We agreed (I think) in that we:

  • use markdown as format
  • sync using nextCloud / webdav
  • add reminders / tasks (if possible)
  • use QOwnNotesAPI if possible

General info

The QOwnNotesAPI connects to Notes app in nextcloud in a basic structure: Directories as categories, files as notes.

  • We have no books. We could use parent directories as books. Is that ok?
  • We have no tags (QOwnNotes uses a sqlite database to keep track of tags. Do we want to follow the same lead?
  • Notes can have only on category (as those are directories)

image

  • Parent folder is named Notes in the nextCloud installation but that can be customized by the user (changing the parent directory on the settings on nextCloud creates a new directory)
  • Notes are .txt files by default but that can changed to .md
  • I still haven't think about how to show the md code but I'm pretty sure I don't want to use a webview. I think I would rather to use a js that translates the md into rtf tags or similar.
  • I have added two modules: sync and filetracker. Sync for all the syncy syncs thingys and filetransfer for all the list of files and folders, render text in files, save files, etc.

What Memo does for now

  • loads a model with the «notes» files in a test folder (under qml/)
  • renders plain text in the first note
  • loads a model with directories and navigates down (not up)

What's missing?

  • All sync part. I have added a separate module (sync) for that. Is there anyone who could try to make that work?
  • Reminders. I should be able to look into notes-app code and try to guess what's going on :)
  • Tasks. As a recursive reminder? Pinned note?
  • Tags. What we do whith those?
  • MD rendering. I might get around it :)