Right, right.
I confused myself. You were speaking specifically about the validation layer in FormEncode, and I confused that with FE in its entirety.
FormEncode's identity is a little mixed up. In many ways I'm really throwing away most of FormEncode except for the validation
We're certainly open to improving the validation constructs in FK. I need to look at your library at some point soon.
I know from your blog (which I enjoy, thanks) that you're not into form tag generation. We're not ready for that yet, but I sympathize. Should people need tag generation, I doubt that there is anything much better than FormKit. Perhaps that's all Subway needs?
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.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- 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
