From: Sean P. <sp...@ad...> - 2006-10-18 03:24:15
|
> Ah, I think we've found a problem in our thinking. Yes - your are correct - there can't be a singleton value. > The second API call should be invoked by the model, however, and is > indeed the only place where the call can take place. I disagree with this - if a view wishes to behave in such a way it can receive any value and filter internally. If a view can only receive data of a given type then an exception would be thrown if it were attempted to be notified with a different type. Eventually we'll have type constraints on the model to avoid such behavior (or rather to check it statically) - but either way it should not impact the view interface. Having the model responsible for checking to see if data is displayable is backwards - the model is not aware of the display. Sean |