I see your point. While in FK these functions are packaged in the same library, there's not much "together" in the actual logic. Basically, we have some tag-building (string building) stuff and then some data validation stuff. And some glue to hook it to webkit.
Either one could be removed and used, in theory. I need to think about how hard that would really be. What kinds of thing would people like to see? For example, does Subway (or webkit or whatever) want tag-building purely? Our challenge to ourselves was to make HTML forms (which SUCK SUCK SUCK) as OOPy as possible via python. We find such an approach useful. On Thu, 03 Mar 2005 15:40:09 -0600, Ian Bicking <[EMAIL PROTECTED]> wrote: > I don't mind form tag generation -- I just think it's unreasonable to > *require* form tag generation. Generators are a great way to create > quality forms without a lot of effort. But a system that creates the > tags for the form, and simultaneously fills in attributes like "value" > and puts in error messages, is putting too much stuff together (IMHO); > there's a good chance you'll want to replace the generator someday > (maybe not, but a chance), and you shouldn't have to reimplement the > other parts of the system at that point. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
