On Tuesday, October 29, 2013 12:33:33 AM UTC-4, mr.freeze wrote: > I am trying to break up a large form into steps that have complex > interdependent values for a benefit application. I can achieve everything > with controller/client side logic but I was hoping to do it at the widget > level so that the form is portable (i.e. works in appadmin too). It would > be a breaking change so I'll drop the issue. Thanks for the feedback > though. >
It might not have to be a breaking change. The "represent" attribute did not originally take the record either, and the code was re-written to accept either a single argument (the field value) or two arguments (the value and the record). I still think the widget is fundamentally different from the "represent" attribute, in that the content of the widget can change dynamically via user interaction in the client, whereas a "represented" value is simply displayed statically. Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
