-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FR: Support dendron hierarchy stubs #297
Comments
Thank you for the detailed FR @Kamholtz, always appreciated :) |
I (and likely many other Dendron users) eagerly await this! Thank you! |
Can you give it a try on 2.46.0 and let me know if it works :) |
I can confirm that this is working extremely well on my Dendron vault. I think you just made this a very viable option for creating/exploring Dendron notes on mobile devices. Thank you so much for the speedy work! |
@Kamholtz Hello Carl. I loved Obsidian but I miss Dendron hierarchies so bad. I'm trying to use same vault for Obsidian and Dendron to overcome this. Would you elaborate on how you are using them together? |
In Dendron there is the concept of a stub (https://wiki.dendron.so/notes/c6fd6bc4-7f75-4cbb-8f34-f7b99bfe2d50/#stubs). A stub is a note that is referenced in a hierarchy, but does not actually exist yet. It appears as a parent when viewing its descendants.
Example
Notes in vault:
note1
note1.note2.note3
note1.note2.note4
In this vault,
note2
is a stub. It does not exist yet, but it is referenced in the hierarchy ofnote1.note2.note3
. Whennote1.note2.note3
is opened,note1.note2
should appear as a parent, and upon selectingnote1.note2
it should be created (in the same way that following a link to a note that is not yet created will automatically create it).Purpose
By not supporting stubs, it becomes difficult to ascend the hiearchy when you are at
note1.note2.note3
because its parentnote1.note2
does not appear in breadcrumbs. It also cannot be inferred thatnote1.note2.note3
andnote1.note2.note4
are siblings.It therefore becomes necessary to remember to create
note1.note2
for easy traversal of the graph. This is a point of friction and error prone as the hierarchy grows.Without stubs, existing dendron vaults will not be traversable using breadcrumbs without first creating all of the stubs.
Use case
Suppose I want to create a todo list for my projects in my brand new vault with Dendron hierarchies. It is grouped by project, then tasks, then parts. I want to jump straight in and write two notes for
part1
andpart2
oftask1
inproject1
todo.project1.task1.part1
todo.project1.task1.part2
In order to get breadcrumbs to recognise these two notes as siblings, I must create the entire hierarchy first by making each note in the graph. This is particularly tedious on mobile.
todo
todo.project1
todo.project1.task1
todo.project1.task1.part1
todo.project1.task1.part2
By recognising stubs, I can start at the lowest point of the tree by writing
part1
andpart2
and navigate up the tree via breadcrumbs (which will automatically create the notes) to fill out the details oftaska
andprojecta
at a later time.The text was updated successfully, but these errors were encountered: