On Wednesday 16 July 2008, Philipp von Weitershausen wrote:
this came out of the ST project, where we constantly repeated this sort
of code.
Not that it matters much, but I think it was Martijn Faassen who wrote it.
... who worked on ST at the time and saw this pattern there.
Regards,
On Wednesday 16 July 2008, Fred Drake wrote:
I suspect this is what you mean, though we've been mostly referring to
the added event.
Right.
Regards,
Stephan
--
Stephan Richter
Web Software Design, Development and Training
Google me. Zope Stephan Richter
On Wed, Jul 16, 2008 at 10:45 AM, Stephan Richter
[EMAIL PROTECTED] wrote:
But I agree. The system supports simple type and that is one of the use cases.
While I originally wanted to add at least 2 of the events to the IAnnotations
adapter itself, I agree with you that the overhead penalty
Previously Stephan Richter wrote:
On Wednesday 16 July 2008, Fred Drake wrote:
On Wed, Jul 16, 2008 at 10:26 AM, Stephan Richter
[EMAIL PROTECTED] wrote:
I agree. I realized only later that those events are defined in the
zope.app.container package. In this case I would just create
On Wed, Jul 16, 2008 at 11:33 AM, Roger Ineichen [EMAIL PROTECTED] wrote:
Even worse, I store objects in the annotation wich are added to
a real IContainer as items somewhere else. This objects are created,
added etc. already in the other container and provide locations
from there.
Only the
On Wed, Jul 16, 2008 at 11:46 AM, Fred Drake [EMAIL PROTECTED] wrote:
I don't see any need for a way to suppress them, since they shouldn't
trigger any subscribers for the normal containment events.
Based on some discussion here, I realize that my position may not be
terribly clear. Just to
On Tuesday 15 July 2008, Tres Seaver wrote:
Comments? Silence is consent as always.
I must be missing something: why would you catalog annoations as though
they were separate content objects? The entire point of annotations was
to be meta about some other content object.
Right, but
On Tue, Jul 15, 2008 at 2:28 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
Right, but annotations are still content in their own right. And we fire
events that are specific to annotations all the time, for example in workflow
instances.
I agree that it's reasonable to fire some event when an
On Tuesday 15 July 2008, Fred Drake wrote:
It *is* reasonable for the IAnnotations adapters to generate a
specific annotation-added event when an annotation is added. There
are probably a whole bunch of other hooks needed to get all that
working with catalogs, and I'd hate to see more magical
