-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
It might actually be the best to move these ZCML directives *down* into
zope.component. That won't affect the dependencies of zope.component at
all in fact; the [zcml] dependencies of zope.component already need all
the
Martijn Faassen wrote:
It might actually be the best to move these ZCML directives *down* into
zope.component. That won't affect the dependencies of zope.component at
all in fact; the [zcml] dependencies of zope.component already need all
the dependencies that zope.app.component's view and
Shane Hathaway wrote:
Martijn Faassen wrote:
It might actually be the best to move these ZCML directives *down* into
zope.component. That won't affect the dependencies of zope.component at
all in fact; the [zcml] dependencies of zope.component already need all
the dependencies that
Previously Shane Hathaway wrote:
Martijn Faassen wrote:
It might actually be the best to move these ZCML directives *down* into
zope.component. That won't affect the dependencies of zope.component at
all in fact; the [zcml] dependencies of zope.component already need all
the
Michael Howitz wrote:
Am 15.05.2009 um 13:30 schrieb Martijn Faassen:
[...]
Cool. It would seem to make sense that the named template mechanism is
bundled along with the page template library anyway (instead of the
form
library). zope.formlib currently depends on zope.app.pagetemplate
On Tuesday 19 May 2009, Martijn Faassen wrote:
* the registration of the zope:view and zope:resource directives. I'm
not sure what these are for, as we have browser:view and
browser:resource. Perhaps these can be safely lifted into
zope.app.publisher, which defines the browser:* varieties
Hi there,
I started working on zope.componentvocabulary. It exists now and
zope.app.interface and zope.app.component both depend on it, along with
zope.app.publisher. We're not entirely rid of zope.app.component yet though:
Martijn Faassen wrote:
[snip]
* the registration of the zope:view and
Hey,
I need to do some analysis to see where the zope:view and
zope:resource directives are in use. I don't want to accidentally
introduce *more* dependencies as packages that use these directives
would now have to depend on zope.app.publisher instead of
zope.app.component, and
Am 15.05.2009 um 13:30 schrieb Martijn Faassen:
[...]
Cool. It would seem to make sense that the named template mechanism is
bundled along with the page template library anyway (instead of the
form
library). zope.formlib currently depends on zope.app.pagetemplate
too so
we could easily
Am 14.05.2009 um 15:02 schrieb Martijn Faassen:
Michael Howitz wrote:
Am 14.05.2009 um 12:05 schrieb Martijn Faassen:
[snip]
Could you talk a bit about what your branch is trying to accomplish?
zope.app.exception depends on zope.formlib's namedtemplate mechanism.
zope.formlib has many many
Michael Howitz wrote:
Am 14.05.2009 um 15:02 schrieb Martijn Faassen:
psnip]
Is this replacement compatible with zope.formlib's namedtemplate
mechanism? Will anything break?
No it is not compatible. So I think it's a bad idea.
Ah, all right, glad we agree.
Breaking the
dependency
Hi Michael
Betreff: Re: [Zope-dev] zope.app.publication dependencies
(volunteersneeded!)
Am 13.05.2009 um 19:55 schrieb Martijn Faassen:
[...]
From this little graph, it looks clear we could do some of the
following things (research is needed to see how difficult they are):
* cut
Am 14.05.2009 um 11:00 schrieb Roger Ineichen:
The last option I already implemented on the
icemac_no_formlib branch in zope.app.exception.
z3c.template is used there instead of zope.formlib.
I can merge this branch in the next days and cut a release.
As long as z3c.template depends on
Michael Howitz wrote:
Am 14.05.2009 um 11:00 schrieb Roger Ineichen:
The last option I already implemented on the
icemac_no_formlib branch in zope.app.exception.
z3c.template is used there instead of zope.formlib.
I can merge this branch in the next days and cut a release.
As long as
Am 14.05.2009 um 12:05 schrieb Martijn Faassen:
Michael Howitz wrote:
Am 14.05.2009 um 11:00 schrieb Roger Ineichen:
The last option I already implemented on the
icemac_no_formlib branch in zope.app.exception.
z3c.template is used there instead of zope.formlib.
I can merge this branch in
Michael Howitz wrote:
Am 14.05.2009 um 12:05 schrieb Martijn Faassen:
[snip]
Could you talk a bit about what your branch is trying to accomplish?
zope.app.exception depends on zope.formlib's namedtemplate mechanism.
zope.formlib has many many dependencies but only this special function
of
16 matches
Mail list logo