Open waxlamp opened 9 years ago
Like it - maybe even the "bring yellow nodes back" is unnecessary. I feel it would be better to let the user mark or "favorite" nodes explicitly as needed. And by "favoriting" simply updating the color is a good start, but also showing a node label for that node would probably help a lot.
I see that instead of marking what has been expanded or searched on, it may be more useful to provide some subtle visual cues that there are more links available from a node. This would let the user see when expanding would provide more information. This would not be trivial to implement though and would require more "lookahead" type queries being available to the view which means more computation.
On Wed, Aug 5, 2015 at 9:26 AM Jeffrey Baumes notifications@github.com wrote:
Like it - maybe even the "bring yellow nodes back" is unnecessary. I feel it would be better to let the user mark or "favorite" nodes explicitly as needed. And by "favoriting" simply updating the color is a good start, but also showing a node label for that node would probably help a lot.
The "bring yellow nodes back" would be a fair amount of coding effort in any case, so it's good that we drop it for now. I'll open issues for "favoriting" a node (I'll even use the standard lit-up star UI widget for that).
What do you mean by "node label" in this context?
I see that instead of marking what has been expanded or searched on, it may be more useful to provide some subtle visual cues that there are more links available from a node. This would let the user see when expanding would provide more information. This would not be trivial to implement though and would require more "lookahead" type queries being available to the view which means more computation.
I recently implemented a "findLinks()" operation (in analogy to findNodes()) so this may actually not be too difficult to do. It would be something along the lines of marking new nodes with an "unexpanded" flag, and decorating those nodes with a little "hairball" of preview links. I'll open an issue for this feature as well.
I don't know what I mean by "node label". I would start with the unique ID but in the future you could potentially put anything there, customizable by the user.
Make the rootness get out of the user's face, unless they want/need to see it (via a Google-style "undo" toaster or similar).