notes VS org-roam

Plume is actually based on my open source note-taking app Notes[1]. You can already get it on Flathub, Snap Store etc. Notes uses just a simple plain text editor while Plume has a completely revamped block editor that I built from scratch. That parts of Notes used in Plume will remain open source (per the MPL license) but the rest of the code will be closed source. At least for the time being.

[1] https://github.com/nuttyartist/notes

Plume is built on top of my open source note-taking app Notes[1]. Since Plume is based on Notes, I'll of course comply with the MPL license and release all existing files that were changed (and must stay MPL licensed).

But I recently discussed my reasoning to go close-source with Plume[2]. I've been working night and day (every day) converting 4 cups of coffee into code for the last 4.5 months to create Plume. I don't want to risk not being rewarded sufficiently for it. But, I'm 99% sure that I'll either open source the core block editor or the entire app in the future.

[1] https://github.com/nuttyartist/notes

[2] https://news.ycombinator.com/item?id=38584960

2. Each note is just a simple plaintext in the underlying data (although currently stored in a database, but in a future update we'll convert the database to an arbitrary folder).

So you can create beautiful and advanced notes, easy. In a non-proprietary format (when that future update arrives). All while using a resource efficient and fast software that is cross-platform.

[1] https://www.get-plume.com/

[2] https://www.get-notes.com/

My Noets app[1] editor is built on top of the Markdown syntax of QOwnNotes.

My new app Plume[2] is built on top of Notes but features an advanced block editor and a new design.

[1] https://www.get-notes.com/

[2] https://www.get-plume.com/

Indeed, I want this feature badly myself to create wikis and such. There's an open issue[1]. We'll definitely implement that some day.

[1] https://github.com/nuttyartist/notes/issues/431

I mostly disagree. Like you said, Qt is the best native GUI toolkit available today. And that is a hard achievement. There are many tradeoffs (some you pointed out) but the open source community seems to find a way around those limitations. There are thousands of open source libraries you can plug-in into your Qt app to overcome many of its limitations (although some remain, like how can't we still not easily change caret/cursor color of QTextEdit??).

Unlike you, I like the direction where Qt is taking. I think QML and Qt Quick are great. I just implemented a feature in my note-taking app that turns Markdown text into Kanban board using QML and the experience has been great (https://github.com/nuttyartist/notes/pull/574). I'm planning to continue transition from QWidgets to QML/Qt Quick.

I do worry of the continuous friction with open source development and hate the online installers as well. I can recommend this useful tool https://github.com/miurahr/aqtinstall that allows you to easily download prebuilt Qt binaries. I hope they can revert their approach on that.

I beg to differ, QML is great. I'm implementing a feature that converts all tasks in Markdown editor to a Kanban view (written in QML) and it's been so easy to do. Work in progress GIF here: https://imgur.com/a/sZNHnp6

And it's even crazier that most of it compiles to C++. It's so fast to develop with it, and runs so fast.

BTW, source code here: https://github.com/nuttyartist/notes/pull/574

Thanks! Even more awesome features and improvements are coming soon (:

We're on Github here btw: https://github.com/nuttyartist/notes

I keep absolutely everything in a single folder. Saved documents, images, movies, financial records, game saves, it doesn't matter. My hierarchical naming scheme takes care of organization. On the odd occasion I actually need a folder, I just append ".d" to the filename.

I use . as a hierarchy delimiter, so file extensions are just part of the hierarchy, and I can have multiple files with the same name except for the extension. For example, "film.spongebob.png" is a photo of spongebob, "film.spongebob.org" is a note about spongebob, and "film.spongebob.s1.e7" is my favorite episode.

I use org-roam [1] for note-taking and task/time-management. I absolutely require a plain-text system so it either had to be markdown or org-mode. Emacs was the deciding factor, else I would have still been using Dendron [2]

If OneNote is your thing, I'd probably recommend Obsidian [3] over org-roam. Despite it being the greatest program ever created, Emacs is a lot to learn "just" for taking notes.

If you like VS Code, check out Dendron. It's the one that got me into more serious PKMS instead of just chucking notes in a folder all willy nilly.

- [1]: https://www.orgroam.com/

- [2]: https://www.dendron.so/

- [3]: https://obsidian.md/

I'm using org-roam to keep my notes, which generally works well for me. There's one thing I am missing and I'm wondering if I just overlooked it, or whether it simply doesn't exist.

Org-Roam is a Roam-inspired Emacs mode that builds on top of org mode. Every node (aka note) has a unique ID that's different from its name. Every link from node A to node B actually links to the ID, so you can change node B's name without affecting the link. When you're on node B, you can open the Roam buffer and it will show you all of the links that point to that node.

Org Mode. I can export my notes to LaTeX or HTML and keep things tidy in a zettelkasten with org-roam.

Of course, the real power-user move would be to use Emacs with Org-Roam, but you have to be prepared to dive deep into the rabbit-hole. If you don't, it won't be worth it. If you do, you'll be handsomely rewarded. I know because I have, and I can highly recommend it if you like tinkering with and customising your tools. IMO, Doom Emacs is the way to go nowadays.

I'd highly recommend Org-roam. It's what has enabled me to actually start consistently keeping notes (and being able to retrieve/access them later). It's very easy with Org-roam to quickly add new notes, or add information to old notes, and the links/backlinks make (re)discoverability very easy.