wwwald
commented
3 years ago A minimal version of this would be a "breadcrumbs" widget with a history-based trail of notes. But the stacked notes look really nice, would be great to see this in Trilium!
Open mursilsayed opened 3 years ago
wwwald
commented
3 years ago A minimal version of this would be a "breadcrumbs" widget with a history-based trail of notes. But the stacked notes look really nice, would be great to see this in Trilium!
leeyaunlong
commented
3 years ago What we have today in trilium notes
When we are browsing notes in trilium notes, we usually use the tree structure that is available to us in the left pannel. However, notes can contain links to other notes and upon clicking, they take you to the new notes. This works fine and if you want to go to the previous or linking note, you can navigate backwards using some shortcut.
Proposed stacked navigation.
When you are browsing notes by following links in your notes, you may significantly improve the user experience by introducing stacked note navigation See Andy Matuschak's notes. When you follow a link, it opens the new note in a new stack thus preserving the context of navigation and providing a rich user experience to browse your knowledge base.
Like this breddcrumbs ?
wwwald
commented
3 years ago Well - those are path-based breadcrumbs, showing the full tree path to the current note.
The actual idea seems to be closer to history-based breadcrumbs, where you can see the pages you visited previously.
That being said - the full visual "note stacking" functionality described by @mursilsayd would be very nice, adding a lot more on top of breadcrumbs.
mursilsayed
commented
3 years ago @leeyaunlong the idea is to keep both the referencing document and the referenced document in a Stacked UI view.
If document A reference document B as an internal link and you click the link, it will keep document A in the UI and will open document B in an additional stacked UI panel(not a separate tab) on the right side thus clearly showing the navigational context. You can use the horizontal scroll bar to collapse or expand the navigational stack. This will reduce the need for back references and will keep the navigational context in front of the user. See example of stack ui navigation
leeyaunlong
commented
3 years ago Well - those are path-based breadcrumbs, showing the full tree path to the current note.
The actual idea seems to be closer to history-based breadcrumbs, where you can see the pages you visited previously.
That being said - the full visual "note stacking" functionality described by @mursilsayd would be very nice, adding a lot more on top of breadcrumbs.
but it cannot work at v0.47.2
I also create a plugin to save the navigate history, but it has some limit with multi-tab/window.
So for your require , i suggest you run the trilium with docker, then access it with chrome. As we know , chrome has many plugins for pages. the logical as below:
Creling
commented
3 years ago @leeyaunlong the idea is to keep both the referencing document and the referenced document in a Stacked UI view.
Well, I think it is expensive to do such a big change. And, Trillium has already be divided into 3 column so I am afraid there is not enough room left for a Stack UI Navigation.
However, It might be partly implemented by improving current preview floating window.
This is an ideal preview floating window for me.
And, of course, I hope trilium could support such a floating window for previewing.
What we have today in trilium notes
When we are browsing notes in trilium notes, we usually use the tree structure that is available to us in the left pannel. However, notes can contain links to other notes and upon clicking, they take you to the new notes. This works fine and if you want to go to the previous or linking note, you can navigate backwards using some shortcut.
Proposed stacked navigation.
When you are browsing notes by following links in your notes, you may significantly improve the user experience by introducing stacked note navigation See Andy Matuschak's notes. When you follow a link, it opens the new note in a new stack thus preserving the context of navigation and providing a rich user experience to browse your knowledge base.