> My solution to this was to remove intermediate-form-values from the
> dataform widget. Instead, I would add a field to form-view-field that
> stores intermediate values, and change the obtain-view-field-value to
> return this value instead of the field's value when it is set. It
> seemed like the way intermediate-form-values is currently being done
> is a bit hackish as it is (I feel like the view is responsible for
> maintaining the actual fields that are being displayed and their
> rendering). Plus, having this value at a the form field level doesn't
> keep the dataform widget from still accessing it. Does anyone have
> any objections to this change/is there anything I am overlooking?
I may be misunderstanding what you want to do, but aren't form views
singleton objects? So if you were to store temporary values in form-
view-fields (ie, in the view) they will clash when multiple dataforms
use the same view.
It is some combination of {view, object, widget} where you should
store intermediate values, imho. field-info in utils.lisp may be what
you want to munge, then.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"weblocks" 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/weblocks?hl=en
-~----------~----~----~----~------~----~------~--~---
