Alberto Valverde <[EMAIL PROTECTED]> writes:
> Jorge is making some good points here... Maybe we should support
> multiple forms per page (arggg). The hack at the schema generation is
If there's another way to handle those things without having to resort to FQF,
then it might help... I believe that this discussion might help all of us :-)
> already done and works so don't need to worry about it... Dunno
> exactly the problems you're facing at display_field_for exactly but
> maybe could be solved somehow... could try to help if you tell me
> exactly what you want to do. I know I'm contradicting my prev. post,
> but it's true that people might want multiple forms... :(
I think that if it is a bad design (hey! who decides that? every use case
should get to a conclusion that solves the problem it is documenting, so...),
then we should let the designer pay with more work. But we shouldn't restrict
that.
Other common things:
- search forms within the same page as a data input form
- login forms within the same page as a search form *and* a feedback
form (just to make two cases where you might have a "name" and/or
"password" fields)
I believe these are also considered "multiple forms on one page".
> I think we need more feedback on this...
>
> Attention people, RFC:
>
> Would you want the Form widgets to support multiple forms per page?
Definitely yes if the above two are also in this list.
> Your controllers will need to receive the whole form as input like
> def controllermethod(self, form):
> If you want to receive data from a FQF. It will be a (possibly)
> nested dicts representing your form's struucture. Normal paramters
> for non-FQFs. This cannot be easily solved so don't come complaining
> later... :)
So I'd have to get data from my form as
name = kw['form']['name']
instead of
name = kw['name'] ?
If this is so, it looks OK to me, specially from our prior discussion about
the Tab stuff on the other thread (the #613, I believe) where we agreed that
it will be needed to find the path to a certain form and field to fill in
values for forms having fields with the same name...
>> I agree that too many hacks are wrong... :-) Maybe we can change
>> those to
>> "technical implementations" :-) (Just kidding)
>
> Patches are always welcomed :)
I still have to get one ready for you WRT the AJAX DataGrid, to make paging
work. :-)
--
Jorge Godoy <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
