On Apr 6, 2012, at 6:14 PM, Anthony wrote: > I wonder if it wouldn't be straightforward to have a version of BEAUTIFY > (arguments? alternative version called DUMP?) that would suppress this > behavior and give us a dump of the object down to lower-level structures: > dicts, lists, etc? Or is there already some better way to explore the > structure of a FORM or SQLTABLE or whatever? > > I usually just look at the serialized HTML to figure out the structure. What > kind of output do you suggest? >
What BEAUTIFY would give you if it were fed a structure of dict/list/primitives without any special xml methods. Example: what you get when you beautify request & response. It might be enough to have an option to BEAUTIFY that suppressed calling .xml(), though it might be worth making exceptions in some cases. My case: I'm using SQLFORM.grid to display a table that's cached by memcache for the client (not for the grid). I'd like to add a button to delete the item from the cache. Easy enough to make it separate, but it'd look better integrated with the other buttons that are already there.
