I've been using FFK a lot, and I've found a few hard-to-use issues with
it. For example, it isn't possible to access the transaction object in a
validator, pass parameters into it from the servlet, etc.
This is something I specifically changed with FormEncode's validation. Basically every validation method takes a "state" parameter, which is a simple container that is application-specific (in a web application it would carry the transaction, in SQLObject it carries the SQLObject instance).
I understand that Ian is working on a replacement, one that ties FFK more
closely to SQLObject. This is a natural thing if you're using SQLObject,
as I've found out in something that I'm working on now.
I'm not planning to tie it to SQLObject, though SQLObject uses the same validation which makes it easier. More specifically, I plan to use interfaces (specifically PyProtocols, http://peak.telecommunity.com/PyProtocols.html , mostly because it's the best documented), and you'll adapt a object or class to a validator. Actually, it would have to be more than just a validator -- it would be a sort of model: validator, data source, and means of setting data all in one. So it should be relatively easy to add this to any object, including objects that you didn't write (since adapters can be written by third parties).
Of course, then this becomes some sort of object-publishing system, which wasn't what I was really expecting to make...
Ian
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
