For now process is always call. When call from workflow_concept it insure the input has benn provided previously. Otherwise you should provide the xas_object. It might evolve with time.

Add some simple unit test to insure an orangecontrib est workflow can be converted to a graph and a graph to an est workflow.
Add test to insure we can execute it as well

Make `Process` inherit from Task
Create a OWESRFWidget which inherit from OWWidget and implement stuff for the task graph.

OWESRFWidget fir the expected design for the esrf task graph. Creating a OWWidgetTaskExecutor for example

[orangecontrib][test] add test for converting esrf task graph to ows and .ows to graph with the current est implementation

settings are not handled yet.

processing source code used:

input_ows_file = "..."
from esrf2orange3.owsconvert import ows_to_esrf, esrf_to_ows
from esrftaskgraph.graph import TaskGraph
graph = ows_to_esrf(input_ows_file)

Include wout hdf5 reading

See merge request workflow/est!43

Test with zocallo

See merge request workflow/est!42