Heisessie: 1000156.011-000-DSC-0002-m-Uitwerking-Heisessie-Delta-Shell.docx
NGHS 2013
... stable, performance, memory use, transparent file formats, documented (API)
- Improve API:
- Drag & Drop
- TreeView
- TableView (add/remove columns is a mess (see ITableView/TableView))
- Remove IGuiView (remove dependencies on IGui from all view)
- Improve/add provider logic for finding best fitting (i.a.w. most specific) type
- View provider
- Property provider
- Context menu provider (still needs to be implemented)
- Node presenter provider (actually "TreeView"/)
- Importers/exporters (still needs to be implemented)
- Improve property grid:
- Support for dynamic property hiding (just like dynamic read only)
- Support for property ordering (fix PropertySorter)
- Make ExpandableArrayConvertor part of framework
- Improve IView/IViewContext/ViewManager API:
- View creation / resolving logic (double-click on item opens view for parent>parent>parent object but can also open view for this object), currently it is too implicit (CreateView changes view.Data to a different object and Delta Shell should check it)
- Clean-up database and remove duplicate classes (Delta Shell)
...
- Separate Delta Shell and Plugins (delete ALL direct dependencies between plugins) and use NuGet to manage / develop / deploy Delta Shell and plugins
- Improve ProjectItemMapView viewcontext (using custom ProjectItemMapLayer that doesn't save datasource)
Delta Shell Next
... future release, open-source, flexibility, simplicity, research version
...
- Extend DataItems to exchange values only when it is asked. This is a minimal requirement for parallel (asynchroneous) model runs.
- Keep time info in mind
- Note: Improves performance of all models (including coupled ones => profile RTC + FLOW: implicitly will be solved by slit of "data “data item set / exchange value"value”)
- Bubbling of CollectionChange and PropertyChange must happen automatically in ModelBase, derived models and functions:
- ModelBase OnInputCollectionChange and OnInputPropertyChange etc should work on ALL aggregated and composed items of the model
- Model vs. Model Runmodel run:
- Functional requirement: scenario / version / run of model (light-weight) input + output (HARD TO IMPLEMENT FOR NOW – LONG TERM)
- Generalize import/export (wizard) logic:
- "File column" to "Data property" matching and vice versa
- Ability to specify a custom separator (in case of csv)
Suggestions by Pieter van Geer
- Move UserControlValidationManager to framework
- Move ShowModalWithTimeNavigator in MorphAnTestHelper to general TestHelper