Re: much more than label field

Hi Sébastien,

 [...]
 > >  Maybe I have missed something, but typing in something like
 > >
 > > readonly="readonly"
 > 
 > Thanks for your response.
 > 
 > This is a good idea. But the problem is as follow :
 > - it doesn't works on all fields (example : MultiListField)
 > - it is not well implemented on all browsers
 > - on most browsers, the output is the same for readonly fields and 
 > editable fields, so the only way to know if we can modify the field is to 
 > try... it makes the user quite frustrated.

 Ok, I see. I have not thought about that.

 If I understand right, You want to render only the value of the field,
and not use an <input> element at all.
 Well, one could do this manually via the from rendering code, but of
course this is getting less nice ....

 My concern here is not about that specific feature; the problem I see
is that when editing Formulator fields one will have a lot
of fields and options there which are used in some, hm, special applications,
(someone out there who uses the alternate name feature?)
so one gets lost in finding the essential ones ... if one feature is
added one can always name the next feature. (how about an accesskey,
btw ;-)

 As such settings as "hidden", "disabled", "readonly", are both possibly
useful for all fields _and_ are not used very often, mayeb they should
be moved in a separate tab to keep edit tab manageable? Or maybe a
separate group in the "edit" tab? 

Just a thought,
Clemens