[Twisted-Python] Bug involving Interface.pixel, Interface.box, and Method

Glyph Lefkowitz glyph at twistedmatrix.com
Tue Feb 6 19:39:54 EST 2001

On Tue, 6 Feb 2001, Chris Armstrong wrote:

[ stuff about bugs, pixels, and boxes ]

This isn't a bug -- since those methods (box, etc) are designed to be used
by Interface, it expects that the current page will have a child called
'pixel' that will provide the image support that it needs.

Also, this starts to beg the question of creating an actual *good* HTML
generation library; the stuff in twisted.web is extremely hacky.  However,
it does outline a general philosophy that I'd like to preserve, so here
you go --

Twisted.Web was not, and is not, designed as a "content" (i.e.
design-heavy text) generation tool.  It is intended to be used to generate
an efficient, distributed interface to stateful Python programs.

To that end, it's desirable that whatever HTML generation API comes with
it should treat them as program interface elements; wherever possible
displaying a traceback if generating one of them fails (this is the
philosophy behind .runBox() -- segregating the page into elements both
visually and in code).

I am open to suggestions as to how to achieve that goal.

                      ______      __   __  _____  _     _
                     |  ____ |      \_/   |_____] |_____|
                     |_____| |_____  |    |       |     |
                     @ t w i s t e d m a t r i x  . c o m

More information about the Twisted-Python mailing list