ISISComputingGroup / ISISComputingGroup/IBEX
Script Generator: Different action types for each action
- Dominant language
- No language data
- Stars
- 6
- Forks
- 2
- Avg merge
- 16h 40m
- Merged PRs (30d)
- 2
Description
As a user of the script generator, I would like to be able to create a script where actions in my experiment may be of a different type to other actions in the script. This ticket is to make it so the user can decide the script definition each action in a script uses. It should still be simple to set a script definition for an entire script as well. The available action types for each action should be filterable in https://github.com/ISISComputingGroup/IBEX/issues/5495. This ticket relies on https://github.com/ISISComputingGroup/IBEX/issues/6661 to display different action types properly.
## Acceptance criteria:
- [ ] A user can select a script definition for each action in the table
- [ ] A user can select a script definition for the entire table
- [ ] Selecting a script definition for the entire table removes actions from the table that do not match that given script definition (the user is asked to confirm if they want this to happen)
- [ ] Selecting a script definition for an individual action clears the script definitions
- [ ] Either
- Global parameters are settable for each of the script definitions loaded in the table
- It is obvious from the UI which script definition each global parameter comes from
- [ ] Or
- Global parameters are replaced by configurable objects in https://github.com/ISISComputingGroup/IBEX/issues/5299
- Configurable objects are decoupled from script definitions so can be used in any script definition
- [ ] Actions can be manipulated via the copy/paste, reordering, inserting, deleting and duplicating actions as before
- [ ] Script definition help strings are shown when hovering over the selector for each action
- [ ] The selected instrument/technique help string are displayed at the top of the script generator
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.