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. The code makes assumptions that are not quite right--e.g., static implies hidden (or was that the other way around; can't remember), etc.
I've hacked in some bug fixes and modified the code here and there to remove some of the assumptions in the code. But, at the end of the day, Ian is right, it is time to move on from FFK and start afresh--the code is just too hard to maintain in its present form. 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. However, I feel that there's definitely a need for a form handing system in Webware, one that ties in a bit more closely to the standard Webware servlet action handling method, but is not tied closely to any particular backend. I've not yet had a chance to use FormKit, so I don't know if it would be a good candidate for being the standard forms system. Thoughts or comments? ...Edmund. ------------------------------------------------------- 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
