Magnit.NodeGraph
obsidian-api
Magnit.NodeGraph | obsidian-api | |
---|---|---|
3 | 18 | |
7 | 1,611 | |
- | 2.2% | |
10.0 | 7.0 | |
over 1 year ago | about 2 months ago | |
JavaScript | ||
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Magnit.NodeGraph
-
JSON Canvas – An open file format for infinite canvas data
Oh sweet! I was in the middle of building my own version of a node-graph component (ref: https://github.com/catapart/Magnit.NodeGraph), but the `canvas.js` implementation from this JsonCanvas repo is exactly what I was trying to build. I really, really like how elegantly uncomplex it is. Could not have been more exactly what I was looking for. So thanks for this!
As far as the spec, I don't really like the idea of forcing well-known types for the nodes. A generic spec should allow for entirely generic nodes that can represent themselves to consuming functions with a 'type' property as a key, as well as arbitrary data types linked to arbitrary nodes. For instance: one of my use cases is an 'addition' node, which would take two number values and produce a number value. This node would also use an entrance execution pin as well as an exit execution pin.
If the spec were to include a 'pin' data type and capture the type keys and labels for pins, those pins could be stored as a list on the node. Then, the type property could just tell the executing context how to route the node data and the pin properties would bring type safety to the functional inputs passed to the mapped function.
Anyway, I assume all of that is out of scope for initial offerings, but that's my two cents on a generalized node spec. Regardless, thanks again for the sweet, simplistic node graph implementation!
-
Visual Node Graph with ImGui
> If people don't intrinsically understand you, maybe you need to go in to more detail so your explanation isn't so abstract.
People did; you didn't.
> Ergo, vis-a-vi have you ever actually tried making a graph that is rearranging itself while you're using it?
No one said anything about "while you're using it". Linters don't fuck up your text as you type it. It's a utility like anything else. And, YES, I have built a working version of one. It doesn't use machine learning/tensors at all, and it's a fucking nightmare to develop. I can see exactly where those things would help me. It's too abstract, to you, to understand? That's a shame! But other people seem to get it, so if you are having trouble, maybe try approaching your ignorance with openness and curiosity instead of cynicism and trivialization ('uncross some lines').
If you want to know how much time I've spent working on node edge graphs, you wouldn't believe me. But I can at least point you to the start of the web-component version I'm porting: https://github.com/catapart/Magnit.NodeGraph
-
Node-Based UIs
Shameless plug time! I've been working on something like this as a custom web component with no dependencies: https://github.com/catapart/Magnit.NodeGraph
Not the most feature rich - I'm developing it for a single project, so that's project's needs come first. But it's rudimentary enough to start from if you're looking to build your own, and it's simple enough to customize if it already does what you need.
obsidian-api
-
JSON Canvas – An open file format for infinite canvas data
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.
-
Love Letter to Obsidian
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.
-
Does Obsidian hold any patents, or feature-related intellectual property?
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)
-
Good starting point for learning more technical things?
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.
- Templater obtain name of previous active link, or parent note.
-
Is there way to run Obsidian command from the shell?
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.
-
Why not open sourcing ?
Canvas has been an open standard since its release.
-
Does Obsidian suitable for my usecase (I use Notion + OneNote)?
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.
- obsidian-api: Type definitions for the latest Obsidian API.
-
Obsidian Canvas is here!
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.
What are some alternatives?
nodes-io - A new way to create with code.
obsidian-livesync
fleeting-notes-quartz - Notes that extend your brain
obsidian-bartender - Allows for rearranging the elements in the status bar and sidebar ribbon
obsidian-note-linker - 🔗 Automatically link your Obsidian notes.
obsidian-sample-plugin
rextract - A simple toolchain for moving Remarkable highlights to Readwise
obsidian-ReadItLater
grit - Multitree-based personal task manager
Heptabase-Export
obsidian-excalidraw-plugin - A plugin to edit and view Excalidraw drawings in Obsidian
obsidian-local-rest-api - Unlock your automation needs by interacting with your notes in Obsidian over a secure REST API.