Actually that name, params versus formData, doesn't matter at all that
was just my convention. In the end you are expanding the dictionary
into keyword arguments to the display function so you could actually
do this and cut out the struc-like formData all together:
In the controller:
value=...
repetitions=...
options=...
return dict(form=form, value=value, repetitions=repititions, options = options)
And in the template:
${form(value=value, repetitions=repititions, options = options)}
Actually the widget api isn't bad its just kind of complicated and you
can't get field id's which is REALLY annoying.
As far as I know this works for alls params not just options, value
and repetitions. Any param that is set on a nested widget can be
passed down using a series of dictionaries and lists as demonstrated
previously.
-Ian
On 2/17/07, Marco Mariani <[EMAIL PROTECTED]> wrote:
>
> Ian Wilson wrote:
> > Wierd to the max....
> >
> We're lucky that a cleaner widget API is coming with tosca :-)
> Not that I despise the current one, it just takes a while to figure out
> because the examples in tutorials are very basic.
> > If I am correct your original mistake was to not make options for each
> > repetition.
> >
> Indeed. That, and the name 'params' instead of 'formData'
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---
