I've just checked http://demo.qooxdoo.org/devel/demobrowser/index.html#ui~FormInvalids.html
and I still think the readability is poor on disabled state (by pressing the disabled button in the demo). This changes a little bit from theme to theme from indigo being less readable to modern being better readable compared to the non-disabled state. I'm using Aristo theme where the "gray haze" is even more distinctive. And I think we do not invent a new property or a new visual state. readonly is there and would perfectly fit the needs. But this may depend on customer needs and personal perception. Regards Dietrich Am 27.11.2012 08:07, schrieb Martin Wittemann: > Hey, >> Anyway I still see the use case for this: disabling checkboxes and >> radiobuttons puts a gray haze over the widgets, including their >> labels, which makes them poorly readable. The user should have good >> readability and the visual representation of the "value not changeable >> but readable" state. > But thats a different point. If its only about the look of the widgets, its a > topic we should not solve in the code base and "invent" a new property which > does literally the same as disabled except the theming. It's something we > should solve in the theme and make the components readable even in the > disable state. > I just checked all 4 themes we have and wonder where you think its poorly > readable. The labels of all input field turn gray on disabled as the icons. > Where do you see the problems? > Regards, > Martin > ------------------------------------------------------------------------------ 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
