On Fri, 2001-12-14 at 14:05, Matt Feifarek wrote: > | Is it easy/possible to integrate with complex form layout? > | (i.e, is the presentation separate from the form logic?) > > Not really. We did this, and basically wrote wrapper classes using a > completely simple template/string-substitution method. All we rely on FFK > for is the <input nnnn> tags. We wrap them up in divs or whatever is > required via the template.
What did you do in your wrapper class? RenderableForm is basically a wrapper class itself, and is intended to be usable for templates and such -- though some template systems might not be able to access everything, if they can't access attributes and functions. > | easier then. :) I'd be willing to write a modification > | along these lines if someone will say "that sounds like it > | fits into the FunFormKit ideal". > > It seems difficult to "fit" something into FFK. FFK seems very > full-featured, but the whole paint/input/post/validate loop is quite > complicated and makes it hard to adapt. We have satisfactory results with > our wrapper, but I don't feel good about our code... it's pretty crufty. > > After we do a cleanup pass (or two) perhaps we'll let everyone see the code > and rip it up. I've been thinking that I should document some of the inner workings, as people will feel more comfortable with FFK they understand what its doing. The actual FormServlet class is fairly small (though dense), but the size might actually make it harder to understand -- the actual logic and flow of the code goes between the various classes quite a lot. Maybe a FunFormKitAnatomy document. Some of the confusion might be because of some ways in which I generalized the code which might not really be necessary, for instance all the method names you pass in, when predefined method names would probably be easier to understand. Ian _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
