...
- Move IsAvailable to IExchangeItem. Is it only for a thread-safety? If yes than see also ICollection.IsSynchronized
Stef: The question is confusing, the actual issue is that we should distinguish between IsAvailable and IsValid.
We are now realized that there is a difference between IsAvailable (only for output item, means it is for consumers) IsValid (probably for IExchangeItem, meaning if item is valid in the context of current component, maybe updated during Validate() call)? - Move Values { get; set; } to IExchangeItem?
- get; set;
to be reviewed at this meeting When discussing get/set, the subject of the discussion graduallly moved to the pull versus loop driven approach. This led to an important decision
: We will introduce a boolean argument that indicates whether the component should run in a pull mode (like in OpenMI 1.4) or in loop mode
- get; set;
Wiki Markup Add *params* keyword to IArguments\[\] args parameter in Initialize(IArgument\[\] args).
- Adrian review, if happy then ...
- Adrian review, if happy then ...
- Change "string Validate()" to / "bool IsValid(IExchangeItem item)" Gena: probably the second one is not needed if we will have IsValid in IExchangeItem.
string return type in the Validate() has to be changed to void/ "IsAvailable()", etc.- to be reviewed at this meeting
Wiki Markup (y) Add "params IOutputItem\[\] items" argument to Update() in order to specify explicitly what should be updated.
- Maybe generalise to IExchangeItem i.e. allow IInputItem?
- Remove AddConsumer/RemoveConsumer and use BindingList in the implementation instead to listen to IOutputItem.Consumer.Add() / Remove()
We will leave AddConsumer/RemoveConsumer for now. The BindingList mechanism has been implemented, though
Add Durations, TimeZone properties to ITimeSet (see also changes from Rob in Java version), so anyone can use it
- When we get loops in the compositions - we have to tell which component will be first! (WHAT SHOULD WE DO IN THIS SITUATION?) Relevant when implementing the Runner process in GUIIn the new GUI, we will let the user indicate the 'Start up component'.
- Add Durations, TimeZone properties to ITimeSet? (see also changes from Rob in Java version)
- Replace all ITime, ITimeStamp, ITimeSpan by: System.DateTime, System.TimeSpan. Should be straightforward. For components working in Julian only time in FORTRAN CalendarConverter can be used. But for .NET all nice features of the .NET date time, time span will be available, e.g. DateTime.AddDays(int), DateTime.AddHours(int), time1 > time2, time1.AddDays(1) > DateTime.Now, and so on.
- all time issues will be discussed at this meeting
- Change XYPoint+XYZPoint, ZYPolyline+XYZPolyline => Point, Polyline (make it look more like OGC entities)
- Review OGC methods to see how we know when a Z coordinate exists?
- Split IIdentity into class IIdentifiable { long Id { get; set; } } and class IDescribable { string Caption { get; set; } string Description { get; set; } }
- Splitting interfaces
- Make various interfaces derive from IIdentifiable, to review
- Do we need a TimeHorizon in the ILinkableComponent ? Seems to be useless since we have ITemporal
- IArgument needs a mechanism for identifying the type of argument e.g. File, Path, int double etc Very usful for providing customised GUI functionality
- Adrian to come up with proposal for next meeting
- Using empty Temporal and ElementSet in the Input items
- Changing of the ElementSet during the time and different Times (steps) for different Elements
- For the Time can be probably solved by missing values
...