Hey,
Chris McDonough wrote:
[snip]
I tried to go after this today (reversing the dependency setup between
zope.formlib and zope.app.form). There are hundreds of changes that need to
be
made to move interfaces to zope.formlib. I made them (more or less
mechanically) but then couldn't
Chris McDonough wrote:
I tried to go after this today (reversing the dependency setup between
zope.formlib and zope.app.form). There are hundreds of changes that need to
be
made to move interfaces to zope.formlib. I made them (more or less
mechanically) but then couldn't get the tests
On 5/15/09 7:00 AM, Martijn Faassen wrote:
Hey,
Chris McDonough wrote:
I did a bit of research on the direct zope.app.* dependencies of
zope.formlib.
Cool!
- I looked into its dependency on zope.app.form. It
essentially uses a bunch of interfaces from the
Hey,
Hanno Schlichting wrote:
This is part of the whole named template adapter story. The rationale
for the whole story is to be able to replace the template of a view
without touching the view. So the template is looked up as an adapter
and not just accessed as self.index / self.template.
Hey,
Chris McDonough wrote:
[snip a lot of places where these interfaces are used]
I'm sure these interfaces are used all over the place as they're used to
help implement widgets; we can't just remove them from their original
location, but...
It's also apparently documented in Phillip's
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 the dependency of zope.app.publisher on zope.app.component
* OR cut the dependency of
Hi there,
Michael Howitz wrote:
z3c.template is used there instead of zope.formlib.
I can merge this branch in the next days and cut a release.
I'm worried by the amount of *new* code that is pulled in just to reduce
a dependency. Making this change would pull in *more* dependencies, not
On 5/13/09 1:55 PM, Martijn Faassen wrote:
Hi there,
zope.app.publisher is depended on by quite a bit of code that uses the
Zope Toolkit, as it defines brower:view and browser:resource and the like.
Unfortunately zope.app.publisher currently depends on more than 60
packages. This is rather
Chris McDonough wrote:
I did a bit of research on the direct zope.app.* dependencies of
zope.formlib.
- I looked into its dependency on zope.app.pagetemplate.
It defines two named templates in its form.py module using
The ViewPageTemplateFile class from zope.app.pagetemplate.
On 5/14/09 6:09 PM, Chris McDonough wrote:
On 5/13/09 1:55 PM, Martijn Faassen wrote:
Hi there,
zope.app.publisher is depended on by quite a bit of code that uses the
Zope Toolkit, as it defines brower:view and browser:resource and the like.
Unfortunately zope.app.publisher currently
On 5/14/09 6:36 PM, Hanno Schlichting wrote:
Chris McDonough wrote:
I did a bit of research on the direct zope.app.* dependencies of
zope.formlib.
- I looked into its dependency on zope.app.pagetemplate.
It defines two named templates in its form.py module using
The
Hi there,
zope.app.publisher is depended on by quite a bit of code that uses the
Zope Toolkit, as it defines brower:view and browser:resource and the like.
Unfortunately zope.app.publisher currently depends on more than 60
packages. This is rather excessive, and we'd like to cut down on this.
12 matches
Mail list logo
