On Sep 13, 2009, at 1:59 PM, Chris Rossi wrote:
This looks reasonable. I think it would also be reasonable to just
make this the standard 'view' functionality, since afaict the
current functionality is a subset of this.
+1 for adding the attributes/functionality below as options to the
Here's some sci fi I wrote up about a page ZCML directive. As Tim Hoffman
suggested, maybe the fact that the page is passed into the template would
give us enough pull capability to avoid any of the other hacks I proposed to
push global names into every rendered template.
Note that the view
I may be missing something that makes this impossible, but my point was that
you could probably add it to the existing implementation without changing
how any existing applications work. The existing functionality is all there
as a subset of the new stuff. But I haven't stared at it for too long
Hi Chris
You are correct, I just didn't want to see the view directive just
disappear and be left with a page implementation ;-).
T
On Mon, Sep 14, 2009 at 10:34 AM, Chris Rossi ch...@archimedeanco.com wrote:
I may be missing something that makes this impossible, but my point was that
you
Tim Hoffman wrote:
Hi Chris
You are correct, I just didn't want to see the view directive just
disappear and be left with a page implementation ;-).
I just baked all this behavior into the view directive on the trunk. There
are no backwards incompatibilities.
- C
