Taipy 3.0 has changed the configuration files, adding a version number and getting rid of Pipelines.
Studio (2.0) must be able to read those files and handle them properly.
If a user selects a configuration file for edition that has no version, Studio should assume it's a 2.x.
Studio would then prompt the user for the target Taipy version (3.0 being the default at this point). That version number will be set in the generated configuration file. That allows, in the future, users to use a legacy version of Taipy.
Studio will not generate configuration files for a version older than 3.0 any longer.
If the user wants to stick to a past version of Taipy, then the relevant extension version must be used.
Sequence management
Taipy 3.0 has replaced the notion of Pipelines with Sequences. A sequence belongs to a scenario and is made of a series of Tasks (that must form a connected graph).
To deal with this change, we propose the following changes to the Studio UI:
The Pipelines panel should be removed from the Configuration pane, and there should be no icons or actions related to Pipelines any longer.
The Scenario perspective and panel are the only places where Sequences are handled:
Scenario panel:
Sequences of any scenario appear as children of the scenario node.
New action on a scenario node:
"Add Sequence": pops a dialog where one can create the sequence name (check for duplicates), and then another dialog ("Select Sequence Tasks") lists the scenario tasks to add to the new sequence. On confirmation, a new sequence is created with the selected tasks. Sequences can have no task at creation time (but that would issue a warning in the configuration file).
Actions on a Sequence node:
"Edit tasks": the "Select Sequence Tasks" dialog is shown and lets the user select the tasks for that Sequence.
"Remove" ("Delete"?): removes that sequence from the scenario.
Scenario perspective:
The title of the perspective should appear in a line above the toolbar as text: "Scenario: " (if the selection in the scenario panel is a scenario) or "Sequence: in Scenario: " (if the selection in the scenario panel is a sequence)
When a sequence is selected, the tasks that it holds should be highlighted (with a thicker border?)
A good-to-have feature would be to also highlight all the data node nodes and links (not mandatory)
If the selection in the scenario panel is a scenario: right-click on a tasks proposes the "Add to Sequence" action, The action is similar the the "Add Sequence" action on a scenario node of the Scenarios panel except the indicated task is pre-selectd.
If the selection in the scenario panel is a sequence:
Action on a task that is part of the sequence: "Remove from Sequence"
Action on a task that is not part of the sequence: "Add to Sequence"
The configuration file checker should make sure Sequences are connected graphs and issue a warning if not. Sequences that are not compliant with this restriction should appear as a warning in the Scenarios panel.
Acceptance Criteria
[ ] Ensure new code is unit tested, and check code coverage is at least 90%
[ ] Propagate any change on the demos and run all of them to ensure there is no breaking change
Description
Taipy 3.0 has changed the configuration files, adding a version number and getting rid of Pipelines.
Studio (2.0) must be able to read those files and handle them properly.
If a user selects a configuration file for edition that has no version, Studio should assume it's a 2.x. Studio would then prompt the user for the target Taipy version (3.0 being the default at this point). That version number will be set in the generated configuration file. That allows, in the future, users to use a legacy version of Taipy.
Studio will not generate configuration files for a version older than 3.0 any longer. If the user wants to stick to a past version of Taipy, then the relevant extension version must be used.
Sequence management
Taipy 3.0 has replaced the notion of Pipelines with Sequences. A sequence belongs to a scenario and is made of a series of Tasks (that must form a connected graph).
To deal with this change, we propose the following changes to the Studio UI:
Acceptance Criteria