While I was concerned that doing this would remove the capability to
suppress tooltips on the active node, clearing the hoveredItem when it
used for documentation functions without even producing a temporary
tooltip.
A future commit will likely be made so that disabling tooltips for nodes
doesn't also prevent the hovered item from being tracked in the store.
Basic connecting for using the existing documentation hover code to
select an item from the active help pane.
Scrolling on selection will now properly perform the minium required
scroll to place the element on screen
Basic styling has been added to the display of documentation for nodes
using the existing tooltip system. This will need another pass to ensure
that style updates immediately when the light/dark toggle is hit instead
of requiring a change of node.
VHS specific namings have been replaced and the code for determining
what the mouse is hovering over has been removed. The existing tooltip
implementation is cleaner and will need to be integrated anyways so
tooltips are temporarily suppressed for the node actively being
displayed in the documentation sidebar.
Optional callbacks have been added for the initial sidebar display and a
user selecting a node element by hovering over it. While selection is
not yet implemented, this should cover any developer needs from more
involved collapsables to automated seeking to video timestamps.
Previously, description was a simple string, but supporting more complex
descriptions requires that new data be passed.
The type of a nodes description has been updated to be either a simple
string as before, or an array consisting of short description string, an
html string for the full description, and a placeholder dict for future
usage.
Definitions and usage points for description have been updated to
accommodate this change
The formatting of ndoes using the existing standardized tooltips has
been improved.
Experiemental work for assisting nodes with display of more detailed
descriptions
f74973 introduced a regression where a node which has had an input
added, will clobber a converted input of in a workflow created before
the input was added.
The prior behaviour was also incorrect (the new input would not exist on
the node), but would often be runnable.
Keeping the position of the converted widget and adding the new input to
the end is an unfortunate compromise. Doing it the other way around
breaks primitive nodes
