obsidian-api VS grit

I really like that you commit to keep this stable and open.

Do you plan to make the TypeScript definition part of this new site?

https://github.com/obsidianmd/obsidian-api/blob/master/canva...

For me it's easier to read TS format.

The Canvas feature is a custom file format, but they published the format here: https://github.com/obsidianmd/obsidian-api/blob/master/canva...

If Obsidian goes under or you want to migrate at least your data isn't lost.

Obsidian is closed source so you won't be infringing their copyright by incorrectly getting/copying their code within your code. I don't believe they have any software patents (too small a company), and the canvas data format is available under MIT license (https://github.com/obsidianmd/obsidian-api/blob/master/canvas.d.ts). Even if you decided to reproduce their plugin APIs (so that existing Obsidian plugins could be reused with your software), you'd be fine per https://en.wikipedia.org/wiki/Google_LLC_v._Oracle_America,_Inc. (but their API definition is under MIT license anyway: https://github.com/obsidianmd/obsidian-api/tree/master)

I would start with with the obsidian api docs and the obsidian plugin docs then feed it into a gpt document loader and ask gpt the same thing you asked here. Obsidian offers a couple different “talk to your notes” plugins using gpt (all you need is an open ai api key) if you’re looking for a streamlined “ai document loader” you could just copy and paste the info into a new note once you have the plugin installed.

In any event, there are no CLI flags to do that at the moment. The canvas format is very new, and not part of the standard markdown format. There is a public specification for it, but it's up to developers to make applications supporting it.

Canvas has been an open standard since its release.

As far as I know, any API that can be used by end users and plugin developers (as described in the previous post) is considered public. You can find the API repo here and definitions in this file.

The .canvas format is a simple JSON-based format that is designed to be easy to parse. We've already seen several plugins leverage this and hope to see even more tools outside of Obsidian. You can see the spec here.

This is cool, but the killer feature I'm looking for is a UI to accomplish the functionality of grit https://github.com/climech/grit. Grit itself isn't particularly functional, but its write-up in the readme hasn't been fully realized by any task tracking software (as far as I'm aware).

*

By specifying order through indentation, we've now created a DAG for what needs to be done, in what order, with the most actionable tasks having the largest indentation. This is how I organize my plaintext to-do files, but afaict no todo list software is able to handle this gracefully- with the exception of grit, which is more of an experiment (but the readme is incredibly well written and describes DAG problem to a tee).

https://github.com/climech/grit

Does anyone know if org-mode handles complex trees? All the examples I've found online were trivial (i.e. one task deep)

Seems like it uses sqlite. Presumably it's trivial to sync using whatever file sync tool you want (Dropbox, or whatever) as long as you're fine without concurrent editing. For that you'd need application support or a more amenable data structure.

https://github.com/climech/grit/blob/master/db/db.go