At 04:59 PM 6/3/2005 -0500, Timothy Soehnlin wrote:
>What if instead of intersplicing node commands, such as iterating through
>lists, into
> the actual document, you were to operate on a different idea.
>
>What if you were to parse an xml file, and then manipulate the entire
> page as through a
Yeah, this is more along the idea that Paul Abrams had, as I mentioned
in my blog, leading me to bring up this subject. In his idea, he had
a piece of Python splicing together pieces of XML, and treating the
DOM somewhat like a dictionary where the ids where the keys.
Best Regards,
-jj
On 6/3/05
What if instead of intersplicing node commands, such as iterating through
lists, into
the actual document, you were to operate on a different idea.
What if you were to parse an xml file, and then manipulate the entire
page as through a system of blocks. i.e.
--
If you made Stan separate, I'd be very inclined to add any explicity
support for it necessary to Aquarium. I think templatings engines are
a matter of opinion, and it'd be nice to share more code here. Thanks
to Ksenia's hard work, Aquarium now supports WSGI.
I see a brighter future ahead of us
James Y Knight wrote:
> On Jun 3, 2005, at 2:18 AM, Ian Bicking wrote:
>
>> * Can parse HTML, not just XHTML. Not the crazy HTML browsers parse,
>> but unambiguous well-formed HTML. I don't like the idea of putting the
>> HTML through tidy; that's fine for a screen-scraper, but is way too
>> de
At 12:20 PM 6/3/2005 -0400, James Y Knight wrote:
>Just inserting all the whitespace from the original document into the
>DOM is a pretty safe thing to do, but it'd be nice to not have to do
>that, as you end up with excessive numbers of text nodes that have no
>meaning.
PWT (peak.web.templates) d
On Jun 3, 2005, at 2:18 AM, Ian Bicking wrote:
> * Can parse HTML, not just XHTML. Not the crazy HTML browsers parse,
> but unambiguous well-formed HTML. I don't like the idea of putting
> the
> HTML through tidy; that's fine for a screen-scraper, but is way too
> defensive for this kind of thi
Donovan Preston wrote:
> We've talked about this slightly before, but I think now more than ever
> stan can be that DOM. I don't think it would be too much work; it would
> mostly require removing assumptions that other nevow modules are
> available. I think stan could be broken out of nevow and
> On 6/2/05, Ksenia Marasanova <[EMAIL PROTECTED]> wrote:
>
>
>> I used it quite a lot, and while it is fast, bugs free and simple to
>> use, total separation of markup and code is IMHO contraproductive -
>> every simple change mostly requires changing two files.
>>
>> --Ksenia
>>
>
> Is changing
On Jun 2, 2005, at 11:18 PM, Ian Bicking wrote:While we're on the topic of DOM-based templating...FormEncode has a module htmlfill (http://formencode.org/docs/htmlfill.html), which is basically like DOM-based templating that just knows about HTML forms. But currently it doesn't use a DOM, it uses
>
> So. That's what Nevow templates are about.
>
At this point, I would like point to the online nevow docs (which is
not yet listed in nevow.com, for some unknown reason)
Tutorial: http://divmod.org/users/mg/nevow-doc/ [available in rst
format in the tarball]
API doc: http://divmod.org/users/
11 matches
Mail list logo
