Hi Jorge,
Jorge Godoy wrote:
> You have to provide a callable to available options and pass selected options
> as the value. (This is with the latest version, that brings a lot of
> improvements, of course... The old one was too rudimentary but still
> available for backward compatibility...)
Thanks for the answer. I read the widget.py for selectshuttle and
worked out "value" as a template parameter.
It took a few iterations to get the template code to work, but then it
finally hit home.
Here is the controller and template code for others...
controller:
def cluster_editself, cluster):
.....
return dict(for_widget=for_widget, available=self.available,
value=dict(selected=self.selected))
template:
${for_widget.display(available=available, value=value)}
> If you modify the object dinamically you're in serious risk to show data that
> doesn't make sense or mix values from the operations of one user with the
> other.
That's why the error message is generated...
Thanks, Andrew.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
