On 28 February 2002, David Ascher said:
> I've found that at times I need to do a fair bit of reorganizing of my
> code in order to, e.g., get the right things in the , while I'm
> actually deep in the body of the .  Given the very "sequential"
> nature of "HTML accretion" in Quixote, that can be a little tricky.
>
> Has anyone else longed for a DOM-like approach at times, where one
> could, as an _alternative_ to just returning strings, do something like:
>
>    response.head.append('bit of html')

I have occasionally wondered if this might be useful.  It's never really
been a great hardship, though.  We have a standard header() function,
err template, that's pretty complex:

  template header(request,
                  title=None,
                  author=None,
                  keywords=None,
                  description=None,
                  meta_info=None,
                  tree_info=None):

...and that's just the signature.  ;-)  In the first couple months of
development, it felt like we were tweaking this template every other
week.  It's been stable for a long time, though -- I guess we finally
got it right.  Or at least good enough.

Bottom line is that I have happily reconciled myself to Quixote's
"accretion" paradigm, and I don't really worry about the alternatives
any more.

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org