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. In principle, I'd be better off with Pages or Word (argh) if I didn't love Markdown so much.
Just by the way: Tags, Dates and other Meta are solved in iA also (Multi)Markdown compatible ( #tag1 #tag2) and very performant.įor me, unfortunately, also a reason not to use Joplin, Ulysses, Bear, Spaces, etc., even if everything else is really great. With the gift advantage that folders and files are even syncronized and backed up via iCloud without having to do anything. The examples of Lightroom (also Darkroom), XnView and iA Writer show how a hybrid solution with a database, folder and file name structure can work very well. While not a completely closed one, it is an added complication for daily work when working with multiple devices, programs (not just text) and operating systems. The end result is that Joplin creates a silo. And the result does not have the same structure as before. Without an export you can't get out again. In the case of iTunes, it destroyed one's painstakingly created folder and file name structure if one wasn't careful. They are still pictures, but without the detour via "Photos" they are not accessible. "Photos" or iTunes / Music does on macOS: all pictures (or music) get cryptic names and are stored in cryptic folders. Joplin does use Markdown, but it squanders the advantage of that openness by giving Joplin's files cryptic names and packing away images completely. And when I search for content, Spotlight doesn't show me cryptic file names that I have to open all in a row until I find the right one. I can rename files even several at once and I can find them via Spotlight. For example, I can use XnView to edit the same images and folders to remove duplicates, for example, and I can drop images from any source with meaningful file names into a meaningful directory structure.
In the case of images and Lightroom, it's the same. Or you can put Markdown files from other programs into this directory structure. This way, for example, in the case of iA Writer, you can edit the Markdown files with any text editor by simply clicking on them in the file system (without going through Joplin exports). Both do not touch the LOCATION or the NAME of the files. Good examples are iA Writer or even Lightroom from Adobe. The advantage would be that you have a simple folder based structure of files that you can edit with different programs. What MrObvious and mean is pretty easy to understand if you take off your programmer glasses for a moment. That's a pretty rough way to answer, isn't it? Whatever, and in any case, for those in the want, there is a feature request for exactly this: Export to ENEX peculiar, all the more considering how unusable Evernote has become and how deep it has sunk (after being considered by me and many others the most important app to have on your computer!) I.e., leaving Joplin for Evernote because you cannot go back to Evernote is, well, let me say. Maybe it would be better to ensure Joplin and JEX become the de facto standard? Go tell Evernote if they want their users back (I am by far not the only one making the Evernote 10 exodus.), they will need to write a JEX importer? However, I assume, it is more of a strategic question if you want to support ENEX export or not. Second, given the vast number of note-taking apps that can read ENEX, it is a de facto standard. Only a few weeks later again did I decide that Evernote (10.) is indeed no longer usable and too laggy for about any real usage, coming back to Joplin for good. In fact, I first switched to Joplin, then went back to Evernote once more (manually migrating the notes I had taken in Joplin during those weeks.). As a past Evernote "junkie" I can understand where this request from OP is coming from.
0 kommentar(er)
