On Fri, Jan 18, 2008 at 12:57:33PM -0500, Stephan Richter wrote:
> On Friday 18 January 2008, Fred Drake wrote:
> > That almost supports the use case. ?Do the adaptation first, then use ?
> > self.template if there's no adapter, and you're golden.
>
> That's what we are doing too. z3c.template is
On Friday 18 January 2008, Fred Drake wrote:
> That almost supports the use case. Do the adaptation first, then use
> self.template if there's no adapter, and you're golden.
That's what we are doing too. z3c.template is pretty much that.
Regards,
Stephan
--
Stephan Richter
Web Software Design
On Jan 18, 2008, at 11:58 AM, Brian Sutherland wrote:
What about zope.pagetemplate.interfaces.IPageTemplate?
Good, because there are no new interfaces that way.
Personally I like the way z3c.form.form.BaseForm approaches this:
def render(self):
'''See interfaces.IForm'''
# r
On Fri, Jan 18, 2008 at 04:35:58PM +0100, Malthe Borch wrote:
> Getting back to the monkey, perhaps it would make sense to formalize the
> way a template object gets its source file. The template class could
> adapt to an ``IFileSource`` implementation that would provide a filename.
What about zop
On Jan 18, 2008, at 10:35 AM, Malthe Borch wrote:
In the current implementation, z3c.jbot monkeys its way into
zope.pagetemplate to easily allow overriding the template source file.
Whacky.
certainly desirable). At any rate, this could be fixed at the level of
the page template implementation
