On Aug 30, 2:42 pm, Benjamin Sims <[email protected]> wrote: > > The demo site provides nice examples of its capabilities: > > http://deformdemo.repoze.org/
Having explored this a little more, I must admit I find it daunting. Sure, for simple stuff it's "easier than building HTML by hand", but for anything non-trivial, it's hard to work out what to do, because everything's hidden from me. I have an object which is a few string fields and then a list of references to Tag objects. The input for the rest of the object is fine but I can't see any way to handle the tags, because the way the schema seems to work is that it assumes the object is composed of everything within it, as opposed to associating with things outside of it. So I can add new tags to the object, but that is not the behaviour I want, because the user needs to be limited to existing tags. And I have no idea if this is something I need to fix with deform, or colander, or both. Any suggestions? Do people really find this easier than just emitting the HTML? If I was doing this by hand I'd grab all the Tag objects, emit "<input type='checkbox' name='tags' value='%d'>%s</input>" % (tag.id, tag.name) for each one, then map those IDs back to Tags in the response handler. That's why I asked about webhelpers, because a function to generate that HTML for an input tag is quite handy without obscuring the detail of what is actually going on. -- Ben Sizer -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
