[8pt, 8pt] UI: Inspect and modify flow-graph and block/parameter definitions in the FEC (GNU Radio and flowgraph) and in the UI (flowgraph)

[ivan-cukic]

• [x] 1st step: Parser for GRC into a DOM-like structure (in C++)
• [x] 2nd step: Basic UI node-editor which loads and saves the nodes into GRC
• [x] 3rd step: Communicating GRC to REST (depends on OpenCMW #182 and #184)

[giucam]

This is the current state of the flowgraph branch. There are two sources with dummy data and blocks can be added in the flowgraph and then connected to the sinks which get plotted in the dashboard page.

[wirew0rm]

This one is currently on hold until #20 is finished and some experience was gained with the REST client on the acquisition property to apply it to the flowgraph properties.

From the discussion in the meeting about going forward with writing to the flowgraph settings:

• ui has one active dashboard, which can be
  • cleared, saved to /dashboards/<name> property, saved to disk/browser storage/download, loaded from file or /dashboards/<name> property
• each service should have a default dashboard
• each dashboard has a client-side flowgraph associated with it
  • Q: included in dashboard yaml or as separate neighboring file/property?
• each service has a service-side flowgraph saved at its /flowgraph property which runs on the service and provides the sinks. The UI needs to be able to change that flowgraph.
  • suggested UI: flowgraphs for all services of the sinks in the current client-side flowgraph are shown as additional tabs
  • ui provides a way to go from sinks to source and vice versa. (Also from plot sink to plot/legend item to plot sink?)
  • alternate approach: show all flowgraphs on a single pane and draw boundaries between services and client parts.
  • or something different?

[giucam]

Q: included in dashboard yaml or as separate neighboring file/property?

Right now it is a separate yaml tree, not included in the dashboard one, however they are combined into one file. I did it mainly considering the case of locally saved dashboards, where having multiple files probably is not very convenient and user error prone, in cases like when moving them to a different folder. I suppose they could be included however, i don't really see drawbacks.

[giucam]

This was implemented mostly in #49. #77 also adds the support for showing and modifying the flowgraphs of remote services.