inishell issueshttps://gitlabext.wsl.ch/snow-models/inishell/-/issues2020-03-14T15:24:54Zhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/824Simulations handling issues2020-03-14T15:24:54ZMathias BavaySimulations handling issuesI've started playing with Simulations. I've also noticed a few problems (the include absolute paths has already been committed):
* there are redundancies between the workflow and the simulation xml
* if we include an xml file that ...I've started playing with Simulations. I've also noticed a few problems (the include absolute paths has already been committed):
* there are redundancies between the workflow and the simulation xml
* if we include an xml file that links to a workflow, we end up with two workflows and possibly conflicting ids. This is not ideal (since it is not so user friendly to have to care about it). I have no clue what should be done...
* when we include an xml, we must provide a proper path to it. It would be nice to give the name (like ""snowpack.xml"") and let the system ""find"" ithttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/817Try building for Android & iOS2021-01-29T17:13:54ZMichael ReiseckerTry building for Android & iOSBecause why not... but needs a Mac with a lot of software.Because why not... but needs a Mac with a lot of software.https://gitlabext.wsl.ch/snow-models/inishell/-/issues/814Cosmetic INI discrepancies2019-12-30T00:50:29ZMichael ReiseckerCosmetic INI discrepanciesIn ./tests, there is a unit test for the INIParser, consequently showing what is currently being preserved when reading an INI file.
Some discrepancies remain between the read INI and the one we save back out, the biggest ones being:
1...In ./tests, there is a unit test for the INIParser, consequently showing what is currently being preserved when reading an INI file.
Some discrepancies remain between the read INI and the one we save back out, the biggest ones being:
1) In an effort to keep them as close as possible, if the default section [General] is not specified in the input file, it will not be written out. Currently this leads to the section header not being written out if there's both keys before any section, and later the default section found.
2) Empty sections should not be written out, unless they are already present in the INI file (like it is already implemented for default keys).
effort: 1/2 dayhttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/808Conditional mandatory keys2019-11-29T22:11:55ZMichael ReiseckerConditional mandatory keysIt is often necessary to set certain parameters as non-optional if another one is missing or present.
So, we should think of a syntax to describe this.
Before implementing it, the program should be well-tested against real world XMLs fo...It is often necessary to set certain parameters as non-optional if another one is missing or present.
So, we should think of a syntax to describe this.
Before implementing it, the program should be well-tested against real world XMLs for if all the scenarios style the panels correctly. (default, mandatory, missing but mandatory, default available but wrong format / out of reach, ...)
effort: 2 dayshttps://gitlabext.wsl.ch/snow-models/inishell/-/issues/803Reordering Replicator-items2020-03-06T23:39:05ZMichael ReiseckerReordering Replicator-itemsIt would be cool to be able to change the order of Replicator items, for example to change the filter or generator ordering.
This is tedious to do by hand, but it is also a little tedious in the code because we need to delete and rename ...It would be cool to be able to change the order of Replicator items, for example to change the filter or generator ordering.
This is tedious to do by hand, but it is also a little tedious in the code because we need to delete and rename keys in the INI on the file system.
The INIParser should be well tested before implementing this, but then I think it should be done.
We could try to implement custom dragging for the Groups (https://doc.qt.io/qt-5/dnd.html), but I don't know it's worth it since then we would have quite a way to drag always.
Simpler would be to expand a list that can be re-arranged with an underlying model of the items. Quick & dirty would be to query two indices and swap.
If we have it, we would enable it in the Selector also for ordering e. g. %COPY.
effort: 2-3 days