On 14/03/2006, at 14:17, Michele Cella wrote:
>> fqf bye bye.... (No one displaying two forms in the same page,
>> right??)
>>
>
> The problem is not displaying two forms on the same page, but one
> validated form, this moreover doesn't make sense from an usability
> POV.
Yep I know, remeber I've been fighting this beast too... :) As I see
it, the only use case for a FQF is when you want to display the
values/errors in the right fields when multiple forms are involved.
Example:
<template>
form1.display(value, action="form1controller")
form2.display(value, action="form2controller")
</template>
<controllers>
@expose()
def displayforms()
return dict(form1=form1, form2=form2)
@expose()
@validate(form=form1)
@error_handler(displayforms)
def form1controller(self, form1):
# do something with form1
@expose()
@validate(form=form2)
@error_handler(displayforms)
def form2controller(self, form2):
# do something with form2
</controllers>
See, two forms in the same page with the two needed controllers, each
of the redirecting to the same page in case of errors. I personally
have tried doing something similar but couldn't. Of course, two forms
in the same page is considered bad-practice from an usability POV, so
I don't think we should break our heads to support it considering all
the ugliness, complication and pests it carries along.
Sorry if I just repeated what you wanted to say but just to make sure
we're in the same frequency :)
Alberto
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
