...
- when to extrapolate/interpolate
- the component needs to know which decorator is a TimeDecorator.
2.5 GUI
The Gui is quite on its way. To be done:
- details on working with decorators
- actually run the application
2.6 SimpleRiver Model - running in GUI
While developing the GUI, the Simple River Model has been updated also (there might be small issues when really running it).
2.7 OpenMIException : Exception - sugestions
Introducing the OpenMI exception is being rediscussed.
The opinion is that it might be done, but that it does not have a very high priority. During the present meeting we will focus on other, more urgent, issues. The OpenMI exception then will be considered at the september meeting.
2.7 OpenMI 2.0 wrapper around OpenMI 1.4 Components
Discussion/Conclusion part: 
We will add an Update() call to the OutputDecorator. The linkable component calls this Update() on all its decorators at the end of its own Update(). This actually is completely the same as what happens in the current 1.4 Wrapper: after IEngine.PerformTimeStep the wrapper updates the buffers.
2.5 GUI
The Gui is quite on its way. To be done:
- details on working with decorators
- actually run the application
Details on working with decorators have been presented by Adrian, we all agreed to the approach of introducing a button that shows a window containing the available decorator and/or factories. The selected one will be added to the component, and thus to the list of output items. By repeated doing this step, the end user can build a chain of decorators.
2.6 SimpleRiver Model - running in GUI
While developing the GUI, the Simple River Model has been updated also (there might be small issues when really running it).
2.7 OpenMIException : Exception - sugestions
Introducing the OpenMI exception is being rediscussed.
The opinion is that it might be done, but that it does not have a very high priority. During the present meeting we will focus on other, more urgent, issues. The OpenMI exception then will be considered at the september meeting.
2.7 OpenMI 2.0 wrapper around OpenMI 1.4 Components
Jesper worked on it quite a bit, together with Stef when needed. Quite some progression was made.
The content of the task shifted from wrapping a 1.4 LinkableComponent to wrapping the 1.4 Sdk.Wrapper.IEngine.
Jesper worked on it quite a bit, together with Stef when needed. Quite some progression was made.
The content of the task shifted from wrapping a 1.4 LinkableComponent to wrapping the 1.4 Sdk.Wrapper.IEngine.
So people who have implemented their wrapper based on the IEngine will be able to migrate their model to 2.0 quite easily.
...
Will be discussed later during the meeting, Stef will show an example of using isAvailable(whosAsking);Discussion/Conclusion part 1: We will add an Update() call to the OutputDecorator. The linkable component calls this Update() on all its decorators at the end of its own Update(). This actually is completely the same as what happens in the current 1.4 Wrapper: after IEngine.PerformTimeStep the wrapper updates the buffers.
Discussion/Conclusion part 2: We decided to let the LinkableComponent have a propery: CascadingCallsDisabled.
The default is false, indicating that the component is running in Pull Driven mode (there will be a cascade of update() calls. This Pull Driven mode has to be supported by every component.
If set to true, the component is expected to run Update()-step by Update-Step(), controlled by some outer world (which may be another component). If the component does not support this Update() by Update() way of running, it will throw an Exception when CascadingCallsDisabled = true is called;
...