> I have time today to integrate nunb's code into the > render-view-field-value today.
> What other attributes would be usefull to implement? I have found that having a style attribute is invaluable, as users get discombobulated by the slightest 1px difference in spacing, and rather than fix it in a CSS file, it is quicker, and *much* more reliable to fix it at the input text site. > Here is a complete list of attributes but I dont think all of them make > sense in render-view-field-value. Saikat posted some work with :onchange a while back, even though forms/ views would need to be reworked to specify in-form dynamism (onblur/ onchange affecting other fields, for example) I feel it is at least worthwhile to put some of these options in render-input (html- utils.lisp) if not in render-v-f-v for the form-input-presentation. Also, this is a good test of your original "Call for widgets" proposal: since we cannot obviously fit in *all* options, which options do we select and make available? After all it is trivial to rewrite render-input .. IMHO the stuff in html-utils (render-checkbox, render-input, render- dropdown etc) should support almost all W3C tag attributes, and render- v-f-v/presentations should support the common use-cases, with specialized presentations for special needs. -- 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.
