Alberto Valverde wrote:
>
> Yep, I think CompoundWidget has a place outside forms too, for
> example, the to-be-released AjaxGrid with pagination, filtering,
> etc... It will probably combine buttons, select fields, textfields,
> ajaxgrid, etc. into something like:
>
> smart_list {
> search_form {
> ....
> }
> ajaxgrid
> }
>
> I could place the grid inside the form but I don't think it belongs
> there really. IMO it's really a compound widget with a form (that
> GETs instead of POSTs) and an ajaxgrid that shows the results as
> children.
>
> I don't think its sole layout either because there could be many of
> these in just one page. I's much cleaner to insert n of these in a
> page than to put n forms + n grids in the same page template (and
> sync their ids and various params so the JS knows which grid to
> update and where to load the JSON from).
>
Hi Alberto,
thanks for the feedback.
As I said I haven't removed the CompoundWidget but just stripped away
forms specific behaviors I've sitting here some small changes that I
will commit after the supper time (:D) that should let you do very
basic layouts like the one you're trying do to, this means
CompoundWidget will just provide value_for and options_for that work on
a name basis and without the path concept (that's very form specific or
application specific), this should do the trick for you nicely I think,
since only the form will end-up in the path and you will be able to
validate it. ;-)
Ciao
Michele
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" 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-trunk
-~----------~----~----~----~------~----~------~--~---
