@Srid I want to have obsidian like interactive graph but reuse the nodes from uplink tree in emanote. How much of an effort, according to you, would that be?
I like having the graph stuck to the screen on the sidebar, for quick navigation, while I scroll through the page -- a UX I prefer.
I'd like to improve the layout such as the right side includes sticky ToC. And the left side includes a navigation sidebar built off folgezettel relationships. So, it shows the siblings of current note in context of the inverted tree.
Yes, I want to do this in Emanote. But it is not clear how to visually represent a sidebar tree where nodes may have more than one parent. (In uplink tree this is not an issue because we don't show siblings)
The graph itself is orthogonal feature, we can have that too. But I don't think it would be as useful as a (more flatish) navigation sidebar.
But it is not clear how to visually represent a sidebar tree where nodes may have more than one parent.
Can you give me an example for nodes having more than one parent?
The graph itself is orthogonal feature, we can have that too. But I don't think it would be as useful as a (more flatish) navigation sidebar.
If the sidebar works out, I don't mind using that. In the end, accessibility must be easy and navigation should be intuitive.
Shivaraj B H said:
But it is not clear how to visually represent a sidebar tree where nodes may have more than one parent.
Can you give me an example for nodes having more than one parent?
Your own post: https://nixos.asia/en/blog/nixify-haskell-project-intro
What would the left sidebar content be, exactly, for this page?
Another example: https://nixos.asia/en/gotchas/macos-upgrade
Say, both 'Gotchas' and 'macOS' have multiple children. How would these children be rendered on the sidebar, and where and how would the current page's title be positioned?
How would these children be rendered on the sidebar, and where and how would the current page's title be positioned?
Why can't we have the title of the current page positioned in the centre and show the siblings of the current page recursively? It would look something of this sorts for nodes with multiple parents:
Screenshot-2023-12-07-at-12.47.00-AM.png
In this manner the children of 'Gotchas' and 'macOS' will be visible on the left side-bar when they visit the respective page. This will sure hide certain details, but is it a compromise worth making?
Can you draw up (maybe on paper) what the https://nixos.asia/en/gotchas/macos-upgrade page would look like?
Don't think I fully understand the visualization being proposed here.
If my understanding of siblings is right, https://nixos.asia/en/gotchas/macos-upgrade doesn't have any siblings, does it?
It does have siblings.
In context of gotchas, it has two siblings:
And in the context of macOS it has none, but could have in the future.
(siblings by definition share the same parent)
This is how normally sidebars are rendered. For eg, when you look at the sidebar of https://emanote.srid.ca/tips/adding-images you see its two siblings: "JavaScript behaviours" and "Synchronizing notes using Syncthing".
Now this sidebar can only represent one parent, unlike our heterarchy which can have multiple parents (and thus multiple sets of siblings).
Related discussion: https://github.com/srid/emanote/discussions/64
Possibly related as well: https://github.com/srid/emanote/discussions/50
Ahh, my bad! I don't know why I kept thinking of children instead of siblings. I will get some sleep and think about this with a fresh mind
This topic was moved here from #general > obsidian graph in emanote by Srid.
Tangentially related: https://github.com/srid/emanote/discussions/358
^ Seems relevant to generate a 'learning map'
Implementation exploration here, https://github.com/srid/emanote/pull/483
Will try to make nixos.asia use this branch once it is stable.
Uptree can now be optionally enabled on the same book layout (I'll remove the note layout as it will no longer be necessary):
https://nixos.asia/en/tutorial/nixos-install
Last updated: Nov 13 2024 at 11:45 UTC