On 12/23/05, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > On 12/22/05, Mike Orr <[EMAIL PROTECTED]> wrote: > > I'm fine with optional Kid preprocessors that cover over some of the > > annoyances: > > > > <FOR expr="r in records" attr="value"> => > > <div py:for="r in records" attr="value"> > > > > <?python <![CDATA[
There are a lot of possibilities. The XML-compliant ones can maybe be done as Kid filters. The non-compliant ones can convert string to string before Kid sees it. Going from String to ElementTree is also intriguing, although I think Kid would accept that only for placeholder values and not the entire template. I'll make tickets for the more promising proposals. I don't think this has to hold up 0.9, however. The multitemplate plugin is more important, even if the API is marked experimental. The <FOR> proposal is XML compliant except that we've defined the default namespace as XHTML. If the parser can ignore that, we're fine. Or we can define an XHTML+extras DTD, which a later stage changes to XHTML. A preprocessor that puts a complete document around a <body> or <div class="page_content"> tag would also be desirable. I like my page templates to contain just their unique content, not several lines of boilerplate tags around them. Yes, the raw template shows up wrongly in the browser but it does show up. I think this is what py:layout was designed for. -- Mike Orr <[EMAIL PROTECTED]> ([EMAIL PROTECTED] address is semi-reliable)
