Hi Benjamin, I don't know for sure, but my guess is qooxdoo is mimicking HTML, where the 'readonly' attribute is only supported on text and password input elements. For checkboxes and radio buttons, there's the 'disabled' attribute, the qooxdoo equivalent of which would be the 'enabled' property. Unlike readonly, This causes the element to be visually "greyed out" both in qx and HTML, but IMO that's a good thing, as you don't want to mislead users into clicking an element only to find out it doesn't react.
Regards, Daniel On 01/17/2012 03:27 PM, Benjamin Dreux wrote: > Hi > > I just went throu the documentation of the checkbox class > (http://demo.qooxdoo.org/current/apiviewer/#qx.ui.form.CheckBox) > I discovered that there is no property readOnly. > > The documentation of qx.ui.form.Textfield says that this property > (readOnly) come from abtractField. > > I wondering why there is no suck property in the checkBox class? > Is there a real reason for this? If not i will open a bug report. > > > Regards > ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
