I guess I overlooked the second "print render...". It's very late...
That does seem to answer my question quite nicely, I just didn't manage to see it for some reason.
but _also_:
I was actually going to reply to this thread with news that I had (re)discovered _this_ thread from a while back:
http://groups.google.com/group/turbogears/msg/6d3bc5e83180b1ef
In which you wrote an excellent explanation of exactly what I was looking for!
So thanks for that too!
Kevin H
On 5/25/06, Michele Cella
<[EMAIL PROTECTED]> wrote:
Kevin Horn wrote:
> Thanks, Michele, that helps, but I'm still not quite there in my
> understanding.
>
> I think what I'm looking for is a way to pass a Form or CompoundWidget
> values between the time the widget is created and the time the widget is
> rendered.
>
> If I were to try to use the default keyword argument with data from a
> database (for example), wouldn't that be breaking the "statelessness" of
> widgets?
>
> I think I just need to see a good example...there are several good example
> of widgetized forms for adding data, but I have yet to see one for _editing_
> that data. If you know of one, please point me to it!
>
That's what FastData is doing.
I just used the default example there but you can leave default=None
and pass a value dictionary at display/render time, this will fills
your fields with the values you want to be edited. ;-)
Look at the second print render(value={...}) I've provided in the
previous example.
Ciao
Michele
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
