iain duncan <[EMAIL PROTECTED]> writes:
>> If it is expecting the form to be retrieve as xhtml -- I've never used such a
>> widget -- then you should render the form before returning and the widget
>> mechanism will deal with placing the errors in the correct places.
>
> Isn't that how the Remote Form widget works? That is what the tutorial
> shows at any rate, that the dom element passed in to the 'update'
> argument gets replaced with the xhtml coming from the method passed in
> with the 'action' par. Am I misunderstanding or do you mean you don't
> use that widget?
I don't use that widget. Never did. ;-)
>> result = conversations_grid.render(conversations).decode('utf-8')
>>
>> This renders a grid with "conversations" as values and places the resulting
>> HTML inside the result variable.
>>
>> You'd have to do something like that but passing the errors dict as well so
>> that those errors can be rendered with the form.
>
> If you don't mind ( I know you've spent a LOT of time today answering
> me! ) can you point me at how that is done? The examples I'm finding
> seem to assume it's done automatically.
I'm really tired now to write it to you (plus I'll have to get my mother at
the airport early in the morning), but remind me tomorrow and I'll try sending
you something that does that. (I might even try learning the Remote Form
widget to help you with that...)
But you'll have to write some docs on our Wiki to document all that in
exchange ;-)
Is it a deal? ;-)
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
