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
{{ message }}
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.
In a previous slide in the SURF GUI wireframes, they mentioned a feature to display the workflow graph somewhere in the system.
@mcastril had a great idea to share a common component to visualize the graph workflow view. This is a good opportunity to separate this component from the main project and publish it in npm. Then, this component can be utilized by anyone who wants to add a workflow visualizer to their own GUI using the data retrieved from the API.
Of course, this will be mainly designed to be a React Component. If this stays like this, we can also migrate to a more powerful network visualizer like React Flow. On the other hand, if in the future we want to also port this component to Angular or Vue, it will be better to stay using vis-network or, even better, migrate to D3.js which are native Javascript libraries.
In GitLab by @ltenorio on Nov 22, 2023, 16:15
In a previous slide in the SURF GUI wireframes, they mentioned a feature to display the workflow graph somewhere in the system.
@mcastril had a great idea to share a common component to visualize the graph workflow view. This is a good opportunity to separate this component from the main project and publish it in npm. Then, this component can be utilized by anyone who wants to add a workflow visualizer to their own GUI using the data retrieved from the API.
Of course, this will be mainly designed to be a React Component. If this stays like this, we can also migrate to a more powerful network visualizer like React Flow. On the other hand, if in the future we want to also port this component to Angular or Vue, it will be better to stay using vis-network or, even better, migrate to D3.js which are native Javascript libraries.
@bdepaula
The text was updated successfully, but these errors were encountered: