John Anderson wrote:
Yes in some cases we don't want any notifications. Consider this case: I think this is a broken paradigm in CPIA - If CPIA is really a MVC paradigm, then the proper thing to do would be to update the model (by setting the selection attribute) and letting the view reflect this change (by actually telling the widget to select something) The problem is that we're trying to do BOTH: update the view and the model manually, and then wishing the controller wasn't getting involved. The reason for this is that we don't have complete control of our widgets: when a user clicks the mouse, the widget wants to update itself whether or not the model has actually changed. This is the one thing that always seems to be vaguely defined in the MVC implementations I've worked with, including CPIA: proper downstream (view -> model - maybe that's upstream? anyway..) communication. My suggestion would be for the view (i.e. the widgets) to maintain some sort of state about the fact that its changing an attribute (selection) and then ignore notifications on selection. I don't think that collection notifications should have to shoulder this burden because its really proprietary to CPIA's design. Alec |
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
