Kevin Dangoor wrote: > If that's not enough (and I'm sure it's not in some cases), widgets > have a "source" method whose purpose is to generate the Kid necessary > to have a fully-editable but still functional template. The part that > isn't baked about that (and isn't likely to be created immediately, > unless someone contributes it), is tools that manage the generation of > those templates. > > There are certainly other options (and I think Michele has presented > some), but I don't know that any of those will land in the next > version. It's important to get something out the door and iterate from > there, rather than trying to match all requirements right away.
I hope you'll give some consideration to formencode.htmlfill as well; for any given form, that's going to be the easiest thing for a designer to work with. It also opens up the potential that someone can escape from programmatic HTML generation by copying the rendered HTML directly into the template. If you make htmlfill easy to use, I think that would be a good answer to many more obscure feature requests for widgets. -- Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
