Open domoran opened 7 years ago
I know this behaviour, but didn't find a way to solve it simply using jsTree.
So, for a future/alternative version I'm thinking of a Blaze (or React?) component, which treats all the states in the Meteor way, but with less features (no drag & drop, etc.) This would be sufficient for my use case – I use the tree only as navigation element.
I am opening this issue as a discussion on how to implement this feature easily. Currently when the underlying collection changes, the whole tree will be redrawn.
I used the treeview for a skills management page, where people could add / move / delete skills concurrently. Currently all people working with the skill matrix will get a whole redraw when one skill gets added to the tree.
What I would like to implement is, to have the tree dynamically add / remove nodes, that have been changed inside the collection. For this I would need to separate the code for building the nodes from the code that builds the and attaches the event handler. But I am not a meteor expert, so I am not sure on how to efficiently handle the node updates.