On 12/29/05, Martin Marinschek <[EMAIL PROTECTED]> wrote: > @default: I understand. > > @immediate: Why would that be? > > The general use-case for immediate UIInputs (as I have seen it > proposed in books, and used it myself) has been a selectbox which > triggers a form-submit. Depending on the value of the selectbox, some > other section is disabled/enabled.
OK. > Why can't that be model-based, and why shouldn't such an UIInput have > a required value? I should back off a bit on "model-based": it's more that it shouldn't have attached validation, basically because - as you've seen - it doesn't really work well, 'cause then there's no way to have, say, a Cancel button. My general development advice would be to avoid in any way possible having immediate fields that trigger validation. For example, in your selectbox example, you'd start it with a non-null value - and enable or disable the corresponding section accordingly - so "required" isn't needed. -- Adam
