Open jensschmeink opened 5 days ago
Notes about the seperationof the models: -> Early checks if all data can be restored is part of the gtDataModel. This has to be done separately if the models are separated
Notes about the seperationof the models: -> Early checks if all data can be restored is part of the gtDataModel. This has to be done separately if the models are separated
An additional check if all task-group tasks/calculators can be restored has to be added
Idea of one "gtProcessDataModel" besides the gtDataModel to collect all task-Groups. This might be beneficial for relations of tasks of different task groups and a simple interface
Code doubling of gtDataModel and gtProcessDataModel should be avoided by moving several parts of the implementation to a generic namespace for both implementations
Summary
Currently the model of the process dock is a styled and filtered gtDatamodel. This leads to several problems and should be changed
Impact on the codebase
Should only be part of the application and not lead to problems in the exported API
Current workarounds
It is one model