2 ms·
Sure.. The idea is that the issue with tags is they can be difficult to trace to all their referenced locations. I find myself not using them because they are
by cam_l 8y ago
Sure..
The idea is that the issue with tags is they can be difficult to trace to all their referenced locations. I find myself not using them because they are difficult to keep track of.. you can't 'see' them at a glance.
But we don't need to see all the referenced locations, just the tree which leads away from the item you are looking at. So you get strict split between, and easy to understand, [left / right], [hierarchy / reference] organisation. Would make it easy to position and re-reference information. And would let you see referencing visually. Below for a really rough idea of what I am talking about.
- list 1 - sub-list 1 - item A | - sub-list 1 - list 1
- item B |
- item C | - sub-list 1
| \ sub-list 3 - list 2
- sub-list 2 - item D | - sub-list 2 - list 1
| \ sub-list 3 - list 2
- item E |
- item F | - sub-list 4 - list 2
- list 2 - sub-list 3 - item G | - sub-list 3 - list 2
- item C | - sub-list 1 - list 1
| \ sub-list 3 - list 2
- item D | - sub-list 2 - list 1
| \ sub-list 3 - list 2
- veli_joza 8y agoOh, I see what you mean now. Left side shows which branches you used to get to leaf, and right sides show other paths to root. It might be very useful occasionally, but would probably have to stay hidden most of time because it would clutter UI with redundant information.
- simantel 8y agoWhat you're describing sounds a lot like Gingko: https://gingkoapp.com/ https://gingkoapp.com/