A more visual graph view

[gillchristian]

It would be really neat to haven an alternative view of the Zettelkasten graph that could be navigated.

Example 👇 from github.com/learn-anything/learn-anything

NOTE: I'm up to work on this. Probably better to do after #98

[srid]

Probably better to do after #98

Agreed. I'd feel a little uncomfortable if the amount of JavaScript on this repo begins to grow 😛

[srid]

On that note, if you wish to take a stab at #98 -- so as to port over ./src-script/search.js to PureScript -- feel free to go ahead (but do let me know what your approach would be)!

UPDATE (Oct 9): Let's use GHCJS (reflex), instead of PureScript.

[gillchristian]

I'm not familiar with PS ecosystem nor with nix so it'll take some time, but when/if I find something I'll post on #98

[srid]

Some improvements in #195

[jaygray0919]

Might it make sense to export to a graph generator? For example, the classic RDF graph generator is Rhizomik which uses Graphviz. An example of the dot notation and rendering is here and here.
Mermaid is used on GitHub. Here is an online example.
A new entry is diagram.code

The basic idea:

export Neuron data as input notation to the preferred graph engine (and template).

Alternatively, like Markdown support for Mermaid on GitHub, implement the graph in a specific zettel, with links to navigate to target zettels.

[GenrihGrigoryan]

The perfect ability for making visual graph is to copy it from the obsidian realisation:

[srid]

I don't find these graph views very useful for navigation -- they provide more of eye-candy than utility -- however my plan is to use that only as a starting point (our current z-index UX stops being useful for larger zettelkastens), and then refine it further (use folgezettel, 'graph search' narrowing, etc.). See Graphic views do not work with a Zettelkasten. I'm experimenting with these ideas here, which will eventually replace both the current search and z-index pages.

@aca made this prototype: https://aca.github.io/neuron_zettels_in_3d.html

[jaygray0919]

We agree

I don't find these graph views very useful for navigation
Graph navigation should be similarTo menu navigation where the submenu are exposed/visible (i.e. not revealsed on mouseover).

It's certainly important to support complex documents (mermaid; d3.js; three.js, graphviz) on a zettel page.

But those services are implicitly/explicitly designed for a canvas - not a necessarily compact format such as navigation (menu selector).

However, we are concerned about maintainability of neuron instances.
If we understand correctly, the formatting services (mermaid, graphviz, ...) are page specific and manually injected.
In contrast, Sphinx requires services to be defined in a configuration.py document such that the service can be used on any page that is part of the configuration.

MathJax support in Neuron may be an example.
Since MathJax is "configured" the notation can be used on any zettel.

Might it be better (i.e. easier to maintain) if neuron required services to be configured globally, and then used by declaring a service identifier before including processor-specific code (e.g. d3.js or three.js).?

[srid]

@jaygray0919 They don't have to be page-specific. You can put the JavaScript code globally in a file named head.html (MathJax is included in this way) and they get automatically included in all pages. See https://neuron.zettel.page/custom-head.html

The menu navigation is a good idea.