...
- IDimension.equals() should be been renamed to IDimension.describesSameAs(), to be constistent with IValueDefinition.describesSameAs(), and to put emphasis on the fact the we are comparing dimensions from a "content point of view", and not implementing the language's Object.equals() function
- Question: do we still want to have the hardcoded integer enumeration values in ElementType, DimensionBase, etc.? I think they originated from the time that we also wanted to describe these possible values in c and/or Fortran.
- Question: what does isAvailable() mean in case of multiple consumers. Do all consumers need to have the same time(s)?
Leave in for now, review after more implementation, one suggestion of modification bool isAvailable(whosAsking);
- Question: Collection or Set instead of List for (In|Out)putExchangeItems in LC?
Leave as is, as definatly cannot use set as unimplemented in .NET currently.- Gena: I will check if changing it to ICollection<> works fine.
- Question: Introduce IState instead of Object? This will emphasize the relation between IManageState and IPersistentState. Additional suggestion: IPersistentState extends IState.
(b.t.w: makePersistent / readPersistentState are wrong names, should be something like getAsByteStream)Gena will discuss with Rob
- Unresolved at this time, if Rob can convinve Gena then we can
- To be discussed: Introduce generics in IOutputItem.Values()? i.e. weakly typed via <T>
- Gina Gena will implement examples in the SDK, but not, for now, in the standard
- Remark: Working with providers/consumers, we should take care that such a circularity might give garbage collection problems
Implementing IDisposable and removing item from Provider/Consumers there might solve the problem
- Point noted, no aggreement as to solution
- Question: for java, shall we use Observer/Observable for events? We then have to offer a base implementation comparable with the current IListener/IProvider.
- To be discussed: what exactly is returned by IOutputDecorater.Arguments()?
Adrian suggested to have Provider there in the interface, then we can step to the previous decorators (if there are any) and get their arguments, and show them nicely grouped in the GUI.
...