Mailman 3 March 2004 - Twisted-web

new nevow know-how needs...;-)
by Alex Martelli 07 Mar '04

07 Mar '04

Hi all -- I'm rather IRC-allergic, don't particularly love mailing lists, but apparently gmane should let me access this mlist via my newsreader (much, much better from my POV), so, let's see. With Rikard Anglerud, and help from Anders Hammarquist (aka Iko), we're developing a few web applications, and eventually a new framework for web applications, with/for AB Strakt's "CAPS" (see www.strakt.com), and we're basing our work entirely on nevow and other parts of twisted (CAPS already uses twisted for all communication among its layers, so the new approach already works much more smoothly than our "previous generation" web-apps based on Webware, IMHO). Over the last few days we moved our stuff from nevow's previous generation (the one that's part of quotient) to nevow's new, stand-alone incarnation. The amount of incompatible changes was staggering (serves us right for working with a new, hotly-developing framework, of course;-), but they do seem to be for the better, and we do have everything working again now (and having nevow as a stand-alone package does make the task of packaging it up with the rest of what CAPS needs _way_ easier, of course). I currently have _one_ serious problem understanding what's going on (or supposed to go on): nevow:data="whatever" directives. I don't understand the rules regarding WHEN this causes a lookup (e.g. of 'data_whatever' on a rend.Page subclass), WHAT it looks things up when it does do a lookup, WHEN it calls method 'data_whatever' thereafter, and with what arguments. Basically, I must be missing something important here -- it mostly feels that once I've used a nevow:data= directive, I lose control of what's going to happen and get nasty surprises. So, I'm gradually moving to using nevow.render= directives instead -- mixing the "model" aspect (getting the data on which rendering is to be based) with the "view" one (rendering it). Not nice, but with nevow.render I _do_ appear to have complete control, or maybe better expressed, _understanding_, of what's gonna happen... So, perhaps somebody can help me understand and use data directives in a more appropriate way? Thanks in advance! Alex

3 9

LiveEvil output buffer patch
by Justin Johnson 05 Mar '04

05 Mar '04

Will someone please apply the attached patch to liveevil? It adds an output buffer. The only additional thing that is needed is for the LiveEvil.output to be reset to None after every request. I'm accomplishing this in my own code currently by doing setting mind.output = None. I would like this code to be added now though, as it takes steps in the right direction until we find the best place to put the code to reset the output. Comments? -Justin

1 1

WebDAV for Twisted
by Thorsten Henninger 02 Mar '04

02 Mar '04

Hi all, since some people were interested in using WebDAV together with Twisted recently, I decided to send you my current work on this. I essentially used the "pydav" implementation: http://www.comlounge.net/webdav/ and wrote a twisted extension. Once you are familar with "pydav", the twisted extension is self-explaning. I hope, the short README.txt will help you. By the way, I tested this implementation together with the Windows Explorer and cadaver, a command line WebDAV client. In my opinion, it would be very useful to integrate WebDAV support in Twisted. Well, since I have never contributed code to twisted, I do not know, how to do this. regards, Thorsten -- brainbot technologies AG boppstrasse . 64 . 55118 mainz . germany fon +49 6131 211639-1 . fax +49 6131 211639-2 http://brainbot.com/ mailto:henni@brainbot.com

1 0

Re: [Nevow-commits] Replace ID generator values with IDs based on context.key. Group
by James Y Knight 02 Mar '04

02 Mar '04

On Feb 29, 2004, at 6:19 PM, mg CVS wrote: > +def keyToXMLID(key): > + """Convert a key into an XML-style ID """ > + if not key: > + print 'keyToXMLID: no key, but why?' > + return None > + return '-'.join(key.split('.')) Did you run into a specific problem forcing the translation of . to -? The HTML spec says: - ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons (":"), and periods ("."). The XHTML spec seems to be even more open, allowing many many characters to be used in names. It says you should only use names matching [A-Za-z][A-Za-z0-9:_.-]* if you want to be compatible with HTML4. James

2 1

Twisted-web March 2004