Samuel GAIST authored Oct 10, 2019 and Samuel GAIST committed Nov 15, 2019

The selection can be done for both remote and local
development.

Samuel GAIST authored Oct 10, 2019 and Samuel GAIST committed Nov 15, 2019

Now the user has the choice to configure a remote
or docker environment. This allows for local testing
and then select a suitable environment for the platform.

This content is not valid in the sense that it's mostly empty.

The names are now less confusing with regard to their usage.

Empty as in "{}"

Empty as in "{}"

Empty as in "{}"

Empty as in "{}"

Empty as in "{}"

Empty as in "{}"

This allows to write tests more easily.

This will allow loading of unfinished experiments.

The editor tab will show an icon when dealing with
invalid asset content.

This also start the implementation for support "wrong"
experiments as in not yet fully configured.

It also now does updating of the IO mapping when selecting
a new algorithm.

This will allow to have a more accurate list of assets to
choose from.

The prototype while conceptually valid doesn't contain valid
plotter. This commit fixes that by selecting a valid Plotter
automatically.

Related to #244

The prototype while conceptually valid doesn't contain valid
data. This commit fixes that by selecting a valid Dataformat
automatically.

Fixes #244

This implementation auto-fiels the experiment content whith
whatever it can find matches input/outputs in number.

It currently doesn't check for compatibility.

Part of #185

This allows to support edition of "not yet created" asset
like for example the experiment which uses a two steps
setup.

This new implementation also opens the newly created asset
for edition.

Fixes #226

The method now returns an Asset and either None
or the data to be used to load the asset editor.

This version currently doesn't apply input/output checks.

This make viewing the content easier.

This will allow use of the meta object system.

This allows to visualise what a toolchain should look like

Samuel GAIST authored Sep 16, 2019 and Samuel GAIST committed Oct 04, 2019

This follows the Python3 recommendation in the documentation

https://docs.python.org/3/library/functions.html#super

Samuel GAIST authored Sep 16, 2019 and Samuel GAIST committed Oct 04, 2019

Issue found when testing with PySide2.

From the documentation, QPushButton::setMenu
does not take ownership of the menu. With PySide2,
the menu is garbage collected but the actions
created from it are not completely destroyed as
it seems. Giving the menu a proper parent ensure
that its lifetime is correctly handled.

Christine MARCEL authored Jul 10, 2019 and Samuel GAIST committed Oct 04, 2019

Fixes #242