On 9/7/06, Karl Guertin <[EMAIL PROTECTED]> wrote:
> > Also, the attributes input_values and validation_errors aren't
> > assigned to the request object. Shouldn't they be?
>
> It's not request, it's cherrypy.request.input_values and
> cherrypy.request.validation_errors
In the code I pasted, I imported request from cherrypy. Doing it your
way, "import cherrypy" and then referring to it like
"cherrypy.request" produces the same error:
print cherrypy.request.input_values
...
AttributeError: 'Request' object has no attribute 'input_values'
> > Are these problems bugs or have I fundamentally misunderstood
> > something?
>
> I still don't understand what is wrong enough with widgets that the
> wheel needs to be reinvented. I know they have limitations but you've
> never given a reason to avoid them. I keep asking this because I plan
> on trying to document issues people have with the framework.
You misunderstand. I'm not trying to reinvent "widgets" because I
think objects bunding html templates are pretty useless. For each
non-trivial widget, there are so many customizations you want to make
that aiming for reuse isn't worth it. Plus, widgets use Kid which I
dislike, are undocumented and have weird apis forcing you to do things
in strange ways. IMHO...
--
mvh Björn
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
