![]() I'd like to share what I've observed the Joplin teams's priorities to be. That's why I registered to weigh in on this. ![]() It is for that reason that I stay with Boostnote for now, although for looks and functionality I find Joplin really attractive. Neither Joplin nor QOwnNotes have that as far as I can tell. It's no Joplin.įor the sake of completeness, there's a third feature/tradeoff that some find important, and that's the ability to handle multiple notebooks with different storage parameters in a single app. Of course QOwnNotes has the opposite problem. "I like the concept of having notes accessible in plain text files to gain a maximum of freedom. ![]() For editor agnostic storage options, stick with something like QOwnNotes. No - Joplin is not and will not be that.Yes - we strife for options that make all users happy or. ![]() Then the question becomes: Do we want to build an optional storage engine for editor agnostic notes backed by a database cache for a speedy startup? They just dislike that the notes cannot be editor agnostic, and wish that while others may disagree, they could accept that it makes sense for some, and continue from that premise. Because why bother? If they really are plain text files just use VSCode or some editor to manage them, then there's no need for a specialised app.īecause those people really really really love and prefer those dedicated editors like Joplin. In fact I feel it's a bit of a waste of time to build an app around plain text files. Where: You can store one notebook with encryption somewhere, and another notebook without encryption to be shared with others in Nextcloud for example. How: With a database (faster), or as self-contained markdown files, where a database is only used as a cache, but the note is always the source of truth. What I personally think would be absolutely ideal is an app where the user can choose per notebook: Where is it stored, and how is it stored. Like those that prefer inverted y-axis in gaming and those that don't. Not a good and a bad one, but different ones. A non-trivial minority is simply opposed to a database dependency that diminishes note editor versatility. When Boostnote went in the database direction with Boostnote Next, there was a rift in the community. If you mess this up, it will be replaced with defaults. You can only see it with an external editor. For example the note could be like this: -Ĭomment: This content is parsed and hidden by APP_NAME. ![]() Granted, the note format is off which defeats the purpose, but it proves you can have some extra information that the app strips away, while it can be edited with other editors for users that wish to.įrontmatter is a portable format for embedding metadata with markdown. You can find yourself in a place without the "right" editor, and just quickly add something important. You can sync the notes to some private cloud. This is infinitely more editable than a database, because you can literally use any text editor without any technical database knowledge or software. The note is immediately visible, editable and retains it's filename. For Boostnote (not Boostnote Next) they store notes as cson with a randomly generated name. Indeed in BoostNote they store the notes as JSON files with an ID as name, so not more editable than if it was in a database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |