...
- Improve TreeView API
- In TreeViewNodePresenterBase::OnCollectionChanged it tries to do 'treeView.Nodes.Remove(node)'; that rarely works!! Should remove from node.Parent.Nodes?
- Improve TableView API
- add/remove columns is a mess (see ITableView / TableView)
- Improve provider logic (finding the best fitting view, properties, ContextMenu, NodePresenter etc. for a type)
- Fix working with units
- Extend views to support multiple items (via view context as an option)
- Improve handling of ViewContexs
- Improve 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 + SOBEK 3.1 plugins)
- Analyze and remove redundant events (using event tree)
- TreeView
- MapControl
- Replace all Timers by DelayedEventHandler and fine-tune them
- Review and fix all WorkInProgress tests
- Review / fix all HACKs in Delta Shell + SOBEK plugins
- Remove code dependencies between plugins, keep them loosely coupled.
- Fews plugin should not know anything about specific plugin of Flow1D, RTC
- Flow1D should not know about RR, RR should not know about Flow1D, ...
- Make them talk via API (Delta Shell, Hydro, etc.)
- What to do with forms used overall (MapView, CoverageView ...), pull-up?
- Tests
- Improve conventions for integration tests (they must be easy to find, should not be mixed with unit tests)
- Minimize dependencies in integration tests
- Improve existing code (eliminate HACKS)
- Water Flow Model 1D Boundary / Lateral Data
- Review RR schematiaztion and model classes
- Review WAQ classes
- Separate NetworkEditor and HydroNetworkEditor
- Introduce support for file-based models at framework level
- Use per-model directory in project data folder
- Rely on IFileBased for all file-based model items
- Keep model data directory in-sync with Project
- GetAllItemsRecursive
Wiki Markup Use object tree + \[Aggregation\] instead of custom implementation- Minimize number of GetAllItemsRecursive calls
- Go to most recent / stable version of 3rd party libraries:
- Gdal
- NetCdf
- IKVM
- etc..
- Take into account class-hierarchy when searching for nodepresenters or property classes
- Use providers for Importers/Exporters similar to views and nodepresenters (what about property classes?)
- Implement something like SynchronizedEventedList which can keep other list in synch with original list and take build/destroy methods, see e.g. HydroNetworkRoutesLayerController, DataItemSet, ...
- Integrate Netron 2.5 + Cobalt into trunk (Swf.Controls)
- Separate data hierarchy/organisation from data-application. Hierarchy/organisation should be responsibility of IProjectItem (Parent, Children, etc...)