I actually looked at this yesterday and it didn't seem to generate forms but does provide the marshaling + validation. so it seems to me it's similar to formencode/htmlfill, where I'm looking for something more like tw.forms.
On Sat, Oct 3, 2009 at 2:35 PM, Andreas Reuleaux <reule...@web.de> wrote: > You might also want to look at Malte's repoze.formapi, > see e. g. his blog entry > > > http://mockit.blogspot.com/2009/05/forms-that-dont-make-you-tense-and.html > > Personally I can't comment on repoze.formapi vs. formish, as I have > used neither of them yet, but I think both should work well with bfg, > whereas z3c.form would require some porting effort. > > -Andreas > > > On Sat, Oct 03, 2009 at 01:17:21PM -0400, Chris McDonough wrote: > > +1 to what Martin wrote, with something else that can only add to the > > confusion: recently I have been using Formish (http://ish.io) to do > > autogenerated forms. I think both zope.formlib and z3c.form try to paint > forms > > based on "model" objects; formish doesn't even try. It just lets you > create > > your own "form schema" and attempts to draw forms based on that. This is > > enough for my needs currently. > > > > - C > > > > > > Martin Aspeli wrote: > > > Thomas G. Willis wrote: > > >> OK, not sure if this is a blasphemous question or not. I've been > slowly > > >> working through "Web Component Development with Zope 3" , and instead > of > > >> trying out the things in zopeproject, I figured that trying out the > > >> things in bfg as well may yield a greater understanding of what the > heck > > >> is going on. I realize that this may be incredibly dumb, so I'm not > > >> surprised that I'm hitting roadblocks once in a while. > > > > > > Bear in mind that whilst repoze.bfg uses a number of Zope packages, it > > > is not built on top of Zope 3 (in the same way that, say, Grok is). BFG > > > contains forks/re-implementations of some Zope things, omits a large > > > number of package traditionally part of a Zope 3 bundle (this is a good > > > thing!), and solves certain things differently (e.g. the way views are > > > done in bfg is different from the way they are done in Zope). > > > > > > For this reason, Philipp's book will probably not apply in many cases > if > > > you're using BFG, and I don't think there's any documentation or good > > > guides to *which* parts will apply and which parts won't (i.e. a "bfg > > > delta zope" document). > > > > > > That said, I can't see it being impossible to use zope.schema + a forms > > > library in repoze.bfg. Not that I've tried. ;) > > > > > >> After reading up on zope.schema and zope.formlib, it seems that schema > > >> based forms, fit my brain, and I would like to use them in bfg if > > >> possible rather than tw.forms etc... > > > > > > This won't help with your specific question, but most people seem to be > > > ditching zope.formlib in favour of z3c.form, which is more feature > > > complete, better documented and better maintained. The basic principles > > > are still the same: you build a schema and then create a form from that > > > schema. > > > > > > http://docs.zope.org/z3c.form has the documentation. > > > > > > To use it, you need to depend on it in your own package's setup.py so > > > that it gets installed, and include its configuration via <include > > > package="z3c.form" /> in your configure.zcml. To use the default > widgets > > > (which you probably want) you also need to mark the request with the > > > IFormLayer marker interface. I'm not sure what facility repoze.bfg has > > > for that, though. > > > > > > Martin > > > > > > > _______________________________________________ > > Repoze-dev mailing list > > Repoze-dev@lists.repoze.org > > http://lists.repoze.org/listinfo/repoze-dev > _______________________________________________ > Repoze-dev mailing list > Repoze-dev@lists.repoze.org > http://lists.repoze.org/listinfo/repoze-dev > -- Thomas G. Willis
_______________________________________________ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
