One major difference seems to be that FFK expects you to use it to build your form layout as well as the tags and validation methods, whereas FormKit is less featureful, but (in my opinion) is more flexible with respect to using templating systems like tplCompiler.
What features would you say that FFK has that FK is missing, out of curiosity?
I don't know FormKit very well, but as I remember it had less form widgets and less validators (though you should feel free to take FFK's validators -- or even better use FormEncode's validators which are only slightly different). Compound fields mean you can have something like a credit card field, which is actually three fields (type, number, expiration) together with validation (e.g., that the type matches the number). There are also some more sophisticated stand-alone widgets dealing with file uploads and other stuff, though I don't know if there's anything keeping you from making the same in FormKit.
I think FFK's automatic form layout makes for nice forms for most situations, with fairly minimal description. Again, this is something that could be added on separately from the core package. For more general form tempating, I think something like this would be best:
http://simon.incutio.com/archive/2003/06/17/theHolyGrail
And of course there's the general issue of repeating and compound fields -- I think they are an important feature, but that's also been FFK's downfall, as adding it on to the design made FFK very hard to understand (even more myself). Which is to say, I don't think you can add that on to the design later, you have to build it in.
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
