Allow Kanbn to interoperate with Markdown Memo

[ngirard]

As a follow-up to #1, I wish Kanbn would be able to interoperate with Markdown Memo.

Implementing #2 would be necessary at least.

I'm having a hard time coming up with an extensive list of requirements, but out of my mind, the most important change is to be able to adopt Obsidian's and Markdown Memo's convention for bidirectional links, i.e.

- [[My task]]

instead of

- (My task)[tasks/My task/md]

Another design decision of yours, which would be too limited for my current project, is to consider 1 workspace = 1 kanban file, whereas my project would require several (at least one for each sprint, and one for each coworker). This is all the more so limited as plain Markdown files are supposed to let you structure your contents the way you need, which Markdown Memo acknowledges. Maybe I should file a new issue for that ?

[ngirard]

@svsool, hopefully I can ping you from this repository... Would you be kind enough to share your thoughts on this ?

Thanks in advance !

[svsool]

As far as I understand kanbn is react app rendered using vscode webview API, while memo works directly with vscode editor view / markdown native view, so it seems to me that kanbn would need to re-implement a good part of memo to support this feature.

[basementuniverse]

I haven't had a detailed look at Markdown Memo yet unfortunately, but hopefully I'll have some time to try it out over the next couple of days - it certainly looks like something I'd get a lot of value out of :smile:

I'm not sure how I'd get bidirectional links working in Kanbn, but might be able to figure something out.

In relation to https://github.com/basementuniverse/vscode-kanbn/issues/2, I have added an option for configuring the name of the index file (currently in progress here). Using this feature, it might be possible to have multiple index files in the same workspace, however I still need to test this.

@svsool that's correct; vscode-kanbn is a react app rendered inside a WebView, however almost all of the core functionality (i.e. reading and writing markdown files) exists in the kanbn project, which is basically just a node CLI app. The VSCode Kanbn extension is just a react wrapper around this library.

[victorkane]

Hi there! By coincidence, I too am searching for a replacement of other worthy tools I've been using over the years, in order to be able to have Markdown based task tracking plus zettelkasten note taking knowledge base features working together (i.e. like vscode-memo with its bidirectional linking + vscode-kanbn). In my search I came across Foam a "personal knowledge management and sharing system inspired by Roam Research", which also has a vscode version (although a wee bit top heavy and is still quite in alpha). The one feature Foam has that is "killer" in scope is the Graph Visualization showing links between notes, or memos. What I wish to bring to the table in this discussion is:

• The main "compatibility" that should be sought is standard markdown things (like the great change you guys did to make front matter standard in #3) including, perhaps, CommonMark and Github markdown standards, both of which are used in Obsidian and Foam (and seem to be the "fashion" right now. It is not so important, then, maybe, that vscode memo and vscode-kanbn have a similar architectural stack.
• I think vscode-kanbn is a wonderful, great project, I'm using it every day, and it's just what I need to escape heavy and vendor-lock-in solutions I'm itching to get away from. I think it is premature to decide with which knowledge base or note taking app it should be compatible with (even though vscode-memo looks extremely promising, and I'm going to try it out immediately), and simply concentrate on its own wonderful feature set and its amazing simplicity and stability. That's my two-cents in this discussion. Thanks for a wonderful project @basementuniverse !

[victorkane]

update: I am using both vscode-memo and vscode-kanbn on a permanent basis, together with markdown links (visual graph), vsnotes and other extensions making up my "low level support and basement working environment" for zettlr, which I will be publishing as soon as I can get my blog up again. While more integration would be great, I am basing myself on functional integration, that is, just using both as they are. Will report back on how that works, and what difficulties it brings me. The most important thing is that integration should not be with obsidian, zettlr, notion, etc., etc., or any other note-based apps in mind, since different users of vscode-kanbn are going to be using all kinds of different apps.