Maybe someone can take a look at the app Transno which does this turning the headings of the outline and its children into separate cards in a flow chart of mind map.
Then you can edit in the mind map. Transno is on web and phone but they still are not letting people get to pay for the pro yet but the concept is still there.
H2s: the levels or degrees of separation from the start of the tree (trunk).
H3s: the notes or nodes of the tree structure
H4s: the notes’ properties, in this case only two, parent and children nodes. There can be other properties too, like connector descriptions (a la, that → generates → this, generates would be the connector, not sure yet though)
refs: this would be the major point in order to make the tree structure work, I’m not sure how these work behind the scenes though
Maybe there’s a better way to map out dependencies but this could even be an improvement versus the current mind map too, as the structure is the same of a tree.
I’m not sure if the refs are enough but I think that if they do work, they would offer the most compatibility with Obsidian and it’s block-level references.
I’m also thinking the strategy used by the Kanban plugin to have editabilty without interfacing with the .md text itself directly, would be preferable.
Longform is definitely for a similar type of user, however I do believe the tree style of gingko is a lot more advanced. @feva’s great take on it, shows how much more of an advanced system it is!
I don’t see it as the same type of thing at all. I’ve trialled Gingko in its various incarnations over a number of years (7 iirc), so I’m fairly familiar with it. It suits some people very well and appears to enhance their productivity. It’s visual. But it’s not the same thing as Longform.
afaics, Longform adds a sequential structure to scenes (it would be enhanced if chapters and sections were added) like the file pane in traditional outliners such as Scrivener, Atomic Scribbler etc.
(fwiw, I think the kanban plugin can stand in for some of the corkboard functions.)
Another very visual option would be to write scenes in Google Keep using extensions to compile into Docs; can be reasonably powerful.
Gingko combines this style of visual appearance with a hierarchical/sequential structure. So I see it in the same use space, but being an entirely different concept, and likely appealing to different users.
that seems like the correct one. As far as I know the project is still in progress!
I’m also super excited about this project coming to life. I just contacted @artem and either him or myself will definitely keep you guys updated on the progress!
Is the kanban plugin not a nice starting point for such a plugin?
Let’s define 6 levels (columns) to start with with each using a H1 … H6 heading as a column definition. So the first column shows all H1 levels, second all H2 levels, and so on.
Maybe deeper structures are needed but it might be a nice start.
The columns should be generated automatically and showing all relevant lower headings. Like Ginko the other levels might be subdued.
Not sure how the drag-and-drop would work and how difficult it would be to select the underlying headers.