Since ili2db 4.11 the id of the metaconfiguration file used to create the physical database is stored in the meta-tables. This means, on Project Creation we consider this id and provide the linked project topping.
Get Topping by selection
Still it's possible to disable it and choose another project topping file.
You can choose a project topping file (identified by model, db-type) from the UsabILITy Hub repositories or as well a YAML file from the local system.
Why, project topping file
... and not "metaconfiguration* file?
Because on this step only project topping files are relevant. Metaconfiguration files are only relevant, when the schema is created. We thought about to provide them, to choose the same like on schema import, but this part is already provided by getting the topping from the DB.
To do
[x] preferredDataSource
[x] Finetune GUI
[x] Synchronize with other open PRs
Resolves #479 and resolves #768
Busy Bar
Not directly related to this topic but it popped up again. Sometimes the wizard has to load - mostly checking the repos to suggest data / reload the comboboxes. And there users are confused, what's happening. For this reason it does now:
Topping on Generate
Get Topping of Metaconfig stored in the DB
Since ili2db 4.11 the id of the metaconfiguration file used to create the physical database is stored in the meta-tables. This means, on Project Creation we consider this id and provide the linked project topping.
Get Topping by selection
Still it's possible to disable it and choose another project topping file.
You can choose a project topping file (identified by model, db-type) from the UsabILITy Hub repositories or as well a YAML file from the local system.
Why, project topping file
... and not "metaconfiguration* file?
Because on this step only project topping files are relevant. Metaconfiguration files are only relevant, when the schema is created. We thought about to provide them, to choose the same like on schema import, but this part is already provided by getting the topping from the DB.
To do
Resolves #479 and resolves #768
Busy Bar
Not directly related to this topic but it popped up again. Sometimes the wizard has to load - mostly checking the repos to suggest data / reload the comboboxes. And there users are confused, what's happening. For this reason it does now:
Screencast from 04.12.2023 16:24:24.webm