From: Edmund L. <el...@in...> - 2003-01-23 06:54:17
|
On 01/23/2003 01:21:56 AM Max wrote: >Where is FFK's CVS? http://sourceforge.net/projects/funformkit >Would next stable version of FFK be release soon? >Or may be it would be included in Webware 0.8 release? > >I it bothers me a bit to use CVS checkout on production site. ;) Can't be helped... I'm finding bugs in FFK now and then. Generally, I think it is fair to say that FFK v0.4, being quite a rewrite of earlier versions, needs more testing before a tarball should be cut, or it be bundled with Webware. In any case, source/version control isn't necessarily a mark of unstable software--it is a sign that the code is being worked on and managed. I actually deploy production stuff right out of a Subversion checkout. This way, I get an automatic code update/distribution mechanism for free. If you want to use FFK 0.4, I do suggest using what's in CVS since this is the only way you're going to be able to get all the fixes in a timely manner. E.g., the mutable forms code in the tarball does not work. I've fixed it as best I can, but I'm not willing to declare victory yet, although things seem to be working properly in this department. I have more bug fixes that I'm testing now, relating to full versus partial form validations. But, I don't expect to check these fixes until I've used them enough to test them. >> formDef = FormDefinition(...).mutable() > >> Then, use the methods defined for class MutableFormDefinition to >> add/replace/delete fields. I added an accessor method to get at the form definitions from the servlet. It is formDefinitions(), returning a dictionary containing form definitions, keyed by form name. To use mutable forms, you need to know what their names are, so you cannot rely on the auto-naming that FFK uses. So, make sure you do something like: formDef = FormDefinition(...., name="myForm").mutable() then when you want to fiddle with the fields: fd = self.formDefinitions()["myForm"] fd.addField(...) etc. ...Edmund. |