On Wed, Jul 14, 2010 at 5:58 AM, Nick Phillips <nick.phill...@otago.ac.nz> wrote: > On Wed, 2010-07-14 at 00:11 +0800, Russell Keith-Magee wrote: > >> What exactly is your use case for something that designers want to >> customize in the raw widget that widget.render() doesn't expose? > > That reminds me of one thing I'd very much like to see in any > refactoring of form/widget handling. > > I'd like to be able to get at the "rendered" data (I say rendered, what > I suppose I really mean is "transformed" either due to rendering needs > or conversion from a graphical representation in the widget to something > that could be resubmitted), without any of the surrounding chrome. There > are various cases in which this can be useful, the most obvious of which > is to tell whether the data in the form has been edited before > submission. It's currently not possible to work this out from the > "before" and "after" data, as you don't know how any particular field's > data might have been munged by the widget (e.g. how is empty data > rendered, any forcing to unicode, Python boolean to textual > representation, date format transformation etc.).
Sounds like a reasonable request; and one that may almost be a necessity if we're planning to make widgets rendered by template, since we're going to need to expose most of the internals of a widget to make them available for any possible rendering scheme. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
