On Saturday, September 20, 2003, at 02:00 PM, Matt Feifarek wrote:
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
I do mean to try and grok your new FormEncode library one of these days... and maybe steal some of your good validators, sure ;-)
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.
We've actually had compound fields all along; since our first release. They're slightly more complicated than a normal field, but they work pretty well. In fact, there are two examples in the Examples dir.
We've also done file uploads all along. It's a bit of a hack, but then so is fild-uploading over http anyway.
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
He's not really doing templating that I can tell. Do you mean the way he handles error markup?
Templating continues to be a thorn in our side, for all of our projects, not just form-related. It's a PITA. Our basic table dump isn't very pretty, but we had hoped that people would dig in and get the granular access to the labels and tags that we tried so hard to build. We don't seem to have communicated that very well...
We're adding a divDump() coupled with some default css in the next small release. That may help.
And of course there's the general issue of repeating and compound fields -- I think they are an
I tried to read the Readme.txt in FormEncode to determine what a "repeating" field is... but I couldn't find it. Can you briefly explain? It sounds important.
Thanks!
Soon, maybe after our next small release, I'd like to get a discussion going with you and some of the other people who seem interested in forms, and find a way to get some library actually /built-in/ to Webkit. It seems like a glaring omission that it's not there, and between your library and ours, I'm sure that we can find a good candidate. I'll send in a note with some ideas and questions for discussion in the next week or so.
-- Matt
------------------------------------------------------- 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
