Just to rephrase things a little better - I noticed in the source code
of a number of deform widgets that it uses 'field.oid', which seems to
be related to the order that a widget appears on the form. So if I
ensure the template for my new widget assigns an 'id' of field.oid, is
this what deform would look for in order to know what to serialise and
subsequently return for the field value?
On Sun, 2010-12-26 at 23:22 -0500, Chris McDonough wrote:
> On Mon, 2010-12-27 at 16:32 +1300, Tim Knapp wrote:
> > Hi,
> > I've been hammering away at a deform widget that consists of 2-3
> > dropdown menus that are much like the 'cascading' jquery plugin, i.e.
> > you choose a value in the first menu and an ajax call is made to a url
> > that returns the values for the subsequent menu and the same for the 3rd
> > one.
> > So far I've got the jquery/python going independently of deform and now
> > I'm trying to create a deform widget for it.
> > Here's the deform widget code:
> > http://duffyd.pastebin.com/GpxyjmCq
> > Here's my current template code:
> > http://duffyd.pastebin.com/JtYWeLRz
> > And here's the traceback I get when clicking on submit:
> > http://duffyd.pastebin.com/FQsC1W2X
> > This is the jquery:
> > http://duffyd.pastebin.com/EV26iPht
> > Any tips on how I can get this to work in deform?
> Not really. You'll need to look at the other widgets and the docs.
> - C
Repoze-dev mailing list