...
Decision 
: We keep the exchange items as an hierarchy, and will use alternative 2 for the linkable components, together with combined empty interfaces mentioned at the previous meeting.:
| Code Block |
|---|
ITimeSpaceLinkableComponent : IComponent, ITimeSpaceLinkableComponent {};
|
...
(Jesper) It was discussed in the last meeting to add extra events to the TimeSpaceExchange item to keep track of when the timeset and elementset changed. I would suggest to put these directly on the ITimeSet and ISpatialAxis/IElementSet instead. Especially, for the ISpatialAxis/IElementSet it could also be nice with a property bool IsDynamic, to indicate wether the ISpatialAxis/IElementSet can change at all.
Decision 
: Could lead to a managemanagement problem (keeping track of all listeners).
3.3. Revisit discussions left out from meeting 28
There is a number of discussions there, that has not yet been decided on.
3.
...
4. Should an ITimeSpaceLinkableComponent override some of the IBaseLinkableComponent methods:
(Jesper) Currently an ITimeSpaceLinkableComponent provides its inputs and outputs as IBaseInput and IBaseOutput. Are these always transferable to ITimeSpaceInput and ITimeSpaceOutput, or could there be cases where other types of inputs and outputs are suitable? Would we even allow that? It could be considered to add methods to the ITimeSpaceLinkableComponent like:
...
That would require all inputs and outputs to be of type ITimeSpaceInput and ITimeSpaceOutput. I guess that would make it difficult to make an ITimeSpaceDictionaryComponent, combining the TimeSpace and the Dictionary extension, since they would each require a different type of their inputs and outputs lists.
Decision : Avoid too specialized components.