At 05:03 PM 3/3/2007 -0800, Andi Vajda wrote:
Questions, comments are welcome.
Very cool! And here I was thinking I'd be the first to implement a context
manager in Chandler. ;-)
Should I implement "with view.observersDeferred():" next ?
It could be nested with "with view.reindexingDeferred():" and the order of
nesting would give some control over which side-effects are turned on and
off and when.
From an API perspective, I think I'd ultimately like to see something more
like a single block operator that defers all side effects, notifications,
etc., and rolls back the changes made if any errors occur within the block.
In practice of course, such a thing would require some careful examination
of what layering should exist between different levels of side effects and
notifications, to distinguish between those needed for the repository to
operate, those that are part of the domain model, and those that are part
of the application or UI layers. So, I understand that's not easily doable
in the near future.
Nonetheless, bravo! on the general direction.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
