Open bmaehr opened 6 years ago
Joplin uses a special format for saving notes: "Joplin sync directory is basically just a database." (see https://github.com/laurent22/joplin/issues/264#issuecomment-369674691). This means, that the notes app would have to implement a second back-end for saving notes, since handling notes will differ from the current back-end. However, it is not our goal to provide multiple back-ends in this app since this would complicate the whole handling.
In order for Nextcloud Notes to integrate with Joplin, Laurent will need to release documentation on the Jex format. This would also be keeping in the spirit of open source development. :+1:
Or, Joplin could optionally start supporting plain text and Markdown as they are normally understood by any Markdown editor you would find in the internet.
The .jex file format appears to be a simple tarfile containing the markdown files + attachments. This is beautifully simple. Great work @laurent22!
You can examine it yourself as follows:
mkdir myjexfile tar -xvf myjexfile.tar -C myjexfile ls -alh myjexfile
This would be awesome. Joplin is already a pretty full-featured, Markdown-flavored notetaking application that not only has Android and iOS applications, but also desktop applications across the major platforms (Linux, Mac, Windows) and even a CLI application. 😛
The only thing it's missing is a web front-end, which Nextcloud could provide! Then, the circle would be complete. 🔥 🔥 👀 🔥 🔥
In fact I started implementing a Nextcloud compatible sync for Joplin. But the problem is, that is not only much work but I'm quite sure that even if i finish implementation - like it usually happens on OSS - the owner of Joplin don't like it and it will not be included.
Did you try asking @laurent22 for pointers? That is really cool of you to work on!
On Wed, Dec 30, 2020 at 5:35 PM bmaehr notifications@github.com wrote:
In fact I started implementing a Nextcloud compatible sync for Joplin. But the problem is, that is not only much work but I'm quite sure that even if i finish implementation - like it usually happens on OSS - the owner of Joplin don't like it and it will not be included.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nextcloud/notes/issues/248#issuecomment-752811764, or unsubscribe https://github.com/notifications/unsubscribe-auth/AANUKZRETK2CKLFEAIBK5SDSXPIPRANCNFSM4FRKJW4Q .
I don't need any "pointers". Yes, you will find the thread there (https://github.com/laurent22/joplin/issues/264) but I finished woking on it. I'm using for me my own partly implemented version. For me that's enough.
I forget to mention: The problem why implementing the sync to work smooth with nextcloud is so much work is because the existing sync implementation is a very long shitty implementation (https://github.com/laurent22/joplin/blob/dev/packages/lib/Synchronizer.ts) done in a quite annoynig language (JavaScript)- at least it was when I started to implement.
Since this bug report seems to be pretty stale, I wanted to ask again if it's nowadays possible to use Joplin in combination with the Nextcloud Notes app?
No, it isn't. You can use them separately
Anyone is welcome to correct this assertion. Cheers.
Joplin can synchronice very nice with nextcloud and stores the notes in a configurable folder. They are visible with notes, but not the real names and no notebooks. It would be if these information form Joplin are processed by notes.