Am 24.10.2012 18:15 schrieb "johannes raggam" <[email protected]>:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 10/23/2012 12:24 PM, kiorky wrote:
> >
> > On 23/10/2012 11:29, Patrick Gerken wrote:
> >> On Mon, Oct 22, 2012 at 10:09 PM, Robert Niederreiter
> >> <[email protected]> wrote:
> >>> Am 2012-10-22 21:07, schrieb kiorky: In pyramid, i'd use
> >>> Deform.
> >>>
> >>> Well, thats a matter of taste i guess. I mean, there's nothing
> >>> wrong with class based forms. I just don't like them yery much
> >>> due to the lack of flexibility.
> >> You can and I do create dynamic schemas for deform forms:
> >>
> >>
http://docs.pylonsproject.org/projects/colander/en/latest/basics.html#defining-a-schema-imperatively
> >>
> >>
> >>
> >>
> Also, deform works fine in Plone. The advantage I see with jawofil is
> >> that they already styled their widgets to match the plone ui. If
> >> you customize the design anyway, that's not an issue anyway.
> >
> > Well said, i didn't dare to tell it myself :-) Colander's deferred
> > is something magical.
>
> the idea behind YAFOWIL is to seperate the data model (schema) from
> the form. because forms do not necessarily represent the object's data
> model 1:1. in fact, by doing so, the UI often gets too complicated.
>
> for example, if you want to edit more than one object with only one
> form or if you have to set/unset interfaces on an object, depending on
> form input which has no representation in the schema.
Deform forms are also separated from the objects data. Creating a form to
fill out data for multiple, even different objects is also possible. Of
course, it is your job then to store the data back on the object. Something
that isn't trivial at all for normal content objects in Plone.
I guess writing a PloneFormGen clone with deform or YAFOWIL would be an eye
opener for many.
Best regards,
Patrick
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
