There has been recently some work on modernizing and fixing the codebase of Basket. In the latest PIM update, I discovered that just the same has happened to KJots. Having used both projects, I think that they are very similar and serve the same purpose. Basket has the main advantage of having floating notes and tags, while KJots has the advantage of being Akonadi compatible. I created this task to discuss what should be the future of the two projects, in relation to each other: in my opinion, it would be nice not to duplicate development effort.
Description
Description
Comment Actions
That's reasonable :)
Basket has the main advantage of having floating notes and tags, while KJots has the advantage of being Akonadi compatible
I think that's more or less fair. Although tags is something I was also thinking of (Akonadi has tags - well, something that can be used to group bunch of notes by keywords).
So in general I'm currently looking into improving rich-text support (based on either KRichTextEdit or KPIMTextEdit::RichTextEditor), and working on compatibility with other formats (Markdown, ENML - used by Evernote) - eventually to be able to sync with some cloud services. That's where Akonadi could be quite useful.