biseau-gui issueshttps://gitlab.inria.fr/lbourneu/biseau-gui/-/issues2019-10-28T19:29:50+01:00https://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/18Representation of json scripts2019-10-28T19:29:50+01:00BOURNEUF LucasRepresentation of json scriptsA script loaded from a JSON file should have its keys and values shown in the `options` tab.
This enables the user to change its name, inputs, outputs, file/code, etc.
This may require an important change in the script system (see http...A script loaded from a JSON file should have its keys and values shown in the `options` tab.
This enables the user to change its name, inputs, outputs, file/code, etc.
This may require an important change in the script system (see https://gitlab.inria.fr/lbourneu/biseau/issues/6 )Efficient Script managementBOURNEUF LucasBOURNEUF Lucashttps://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/17Action for scripts: "Write back"2019-10-28T19:29:30+01:00BOURNEUF LucasAction for scripts: "Write back"User should be able to write back the script on disk.
When a script is loaded from a json, lp or py file, user can then modify it.
The user may want to pass on this modification to the script, so that the script is modified.User should be able to write back the script on disk.
When a script is loaded from a json, lp or py file, user can then modify it.
The user may want to pass on this modification to the script, so that the script is modified.Efficient Script managementhttps://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/16Show the window associated to each script2019-10-28T18:41:21+01:00BOURNEUF LucasShow the window associated to each scriptWhen having few scripts, it is quite hard to determine where are the windows associated to each script.
Scripts are listed on the left, and their window are on the right. Which window correspond to each script ?
This question is especia...When having few scripts, it is quite hard to determine where are the windows associated to each script.
Scripts are listed on the left, and their window are on the right. Which window correspond to each script ?
This question is especially hard when many scripts have the same name (see #15)
Idea: when hovering over a script in the left list, an indication of which window is associated to this script should be drawn, such as a line linking the script item to the window, or the window being highlighted.Efficient Script managementsacha schutzsacha schutzhttps://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/14Drop-down button to merge Export actions2019-07-09T18:01:40+02:00BOURNEUF LucasDrop-down button to merge Export actionsThere is multiple `_export_*` actions in mainwindow, but in order to keep the interface simple, only one export button should be available.
This could be achieved with a [drop down button](https://www.pythonprogramming.net/drop-down-but...There is multiple `_export_*` actions in mainwindow, but in order to keep the interface simple, only one export button should be available.
This could be achieved with a [drop down button](https://www.pythonprogramming.net/drop-down-button-window-styles-pyqt-tutorial/).https://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/13Non working sliders in script options2019-07-02T12:51:54+02:00BOURNEUF LucasNon working sliders in script optionsQSlider is used to represent script option annotated with type `biseau.run_on_types.ratio` and `biseau.run_on_types.percent`. See script `build_iceberg_lattice.py` for a usage example.
When rendering the options of that script, it seem...QSlider is used to represent script option annotated with type `biseau.run_on_types.ratio` and `biseau.run_on_types.percent`. See script `build_iceberg_lattice.py` for a usage example.
When rendering the options of that script, it seems that the QSlider widget is correctly rendered.
However, i can't modify it by drag and dropping the handle.https://gitlab.inria.fr/lbourneu/biseau-gui/-/issues/8Error raised while loading scripts2019-05-03T18:32:10+02:00BOURNEUF LucasError raised while loading scriptsWhen a script is loaded, errors may appear. For instance, `ImportError` if the script is using a non-installed script.
While these scripts shouldn't be added to the GUI, user should be able to know which scripts are unavailable, and why...When a script is loaded, errors may appear. For instance, `ImportError` if the script is using a non-installed script.
While these scripts shouldn't be added to the GUI, user should be able to know which scripts are unavailable, and why.
Currently, biseau package does not provide any way to get an InvalidScript object, but it will be done soon.
The GUI should show them, or at least the errors raised by biseau.Efficient Script managementsacha schutzsacha schutz