Thank you for your answer Florian, But as I wrote before it's all solved form me, but I'm trying to convince others that this is a use case and may be implemented in the core ui.
I've additionally created decorators which visualize the readonly state for textarea, textfield, combobox etc. to allow users to distinguish between disabled, readonly and normal state. Regards Dietrich Am 27.11.2012 09:24, schrieb Florin Jurcovici: > I don't know if this works, but IMO you could try it. Why don't you > simply not bother with editable/readonly at the level of each > individual form element, and just put a blocker with opacity == 0 on > top of the form when it has to be read-only? IMO this also provides a > nicer separation of concerns/single point of control for the read-only > vs editable decision. > > ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
