Albertas Agejevas wrote:
People relying on
automatic indexing would have to register a couple of event handlers
in their configurations (or include zope.app.catalog), but the rest of
us would be able to choose the policy of how and when the objects are
registered with IntIds and indexed in
Hi there,
Albertas Agejevas wrote:
[snip]
About a year ago zope.app.catalog as been moved to zope.catalog. I
think during this move there was a unique opportunity to leave these
event handlers behind in zope.app.catalog, so that the no .app
version is free of these forced choices.
Doing
On Sun, Sep 27, 2009 at 1:16 PM, Albertas Agejevas a...@pov.lt wrote:
About a year ago zope.app.catalog as been moved to zope.catalog. I
think during this move there was a unique opportunity to leave these
event handlers behind in zope.app.catalog, so that the no .app
version is free of these
On Tue, Sep 29, 2009 at 01:09:08PM +0200, Martijn Faassen wrote:
About a year ago zope.app.catalog as been moved to zope.catalog. I
think during this move there was a unique opportunity to leave these
event handlers behind in zope.app.catalog, so that the no .app
version is free of these
On Tue, Sep 29, 2009 at 01:33:21PM +0200, Hanno Schlichting wrote:
Is there any reason you don't just ignore the configure.zcml in that package?
Nobody forces you to load the zcml file. The whole point of having
these policies in zcml is to be able to ignore or override them
easily.
Good
Albertas Agejevas wrote:
On Tue, Sep 29, 2009 at 01:09:08PM +0200, Martijn Faassen wrote:
About a year ago zope.app.catalog as been moved to zope.catalog. I
think during this move there was a unique opportunity to leave these
event handlers behind in zope.app.catalog, so that the no .app
We teased out all this ZMI- and event-handling related behavior in
repoze.catalog. r.catalog consumes no events, and disuses the IIntIds utility.
It's otherwise a lot like zope.catalog. It might be a good starting point if
you want more control.
FWIW, we use this code heavily in several
