You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One great feature would be to allow users to add a custom React component to each node kind to render custom body content. Until Safari fixes its foreignObject implementation, the component would have to only render SVG elements, but that still seems useful.
Right now all the nodes are fixed-size. The simplest version of this would keep the fixed node dimensions, and leave it up to the user to not overflow them. A slightly better version of this would leave it up to the user to compute each node's dimensions individually. And ideally we would automatically find a bounding box of the user's custom SVG content and dynamically resize the node to fit.
I'll let these options sit for a while and come back to this later. If anyone has ideas feel free to being them up.
The text was updated successfully, but these errors were encountered:
For another project, I just implemented a dataflow graph much quick/dirtier than yours, but also including the custom React components using https://reactflow.dev/examples/custom-node/ — I may look to refactor with aspects from both now that I've seen react-dataflow-editor's approach. The aim of the project is to allow domain expert to make specific updates to a bit of a large knowledge graph.
Nice job, and thanks for the detailed writeup which caught my eye to bring me here via Knowledge Futures and Twitter.
IsaacHook
added a commit
to IsaacHook/react-dataflow-editor
that referenced
this issue
Mar 4, 2022
One great feature would be to allow users to add a custom React component to each node kind to render custom body content. Until Safari fixes its foreignObject implementation, the component would have to only render SVG elements, but that still seems useful.
Right now all the nodes are fixed-size. The simplest version of this would keep the fixed node dimensions, and leave it up to the user to not overflow them. A slightly better version of this would leave it up to the user to compute each node's dimensions individually. And ideally we would automatically find a bounding box of the user's custom SVG content and dynamically resize the node to fit.
I'll let these options sit for a while and come back to this later. If anyone has ideas feel free to being them up.
The text was updated successfully, but these errors were encountered: