Hey, I agree with Daniel in closing the bug. A read only checkbox is a disabled check box. I think the user should see and know that he can not change the value but he can read it. Thats the basic idea of the enabled property. If you think different, you might either change the theme of the checkbox or extend the current checkbox and implement the readonly property yourself. Both ways can he handle with an acceptable effort. If you need any changes in the checkbox e.g. a private which should be protected, let me know. Thats something we can change easily. Regards, Martin
Am 26.11.2012 um 13:57 schrieb Dietrich Streifert <[email protected]>: > Hello everybody! > > Daniel closed the bug report for lack of use cases. > > Here is our use case: > > We have a huge qx.ui.form.Form and renderers based on > qx.ui.form.renderer.AbstractRenderer with a lot of radiobuttons and > checkboxes. > > The resulting rendered form widget is used (via model, controller et.al.) to > retreive the form content from the backend which works perfect. > > Based on the access rights of the current user the form is in a editable or a > readonly state so we would like to use the same form for viewing data without > allowing the user to change the contents or states of the form fields. > > It would be a tremendous work to create another form widget for viewing the > data readonly eg. by replacing radiobuttons and checkboxes by simple images > because we have then to implement another stack for getting the data from the > backend to the readonly form widget. > > Please consider the implementation of readonly buttons. > > Regards > Dietrich > > Am 17.01.2012 16:37, schrieb Benjamin Dreux: >> I added a bug report for this, as an enhancement >> Bug 6051 >> >> Regards >> >> Le 17 janvier 2012 10:31, Benjamin Dreux <[email protected]> a écrit : >>> But then why mimick the readOnly behavior ? >>> IMO since textField can be readOnly, the other form field have the >>> same behavior. >>> It will facilitate the understanding of the ui framework. >>> >>> >>> >>> Le 17 janvier 2012 10:21, Daniel Wagner <[email protected]> a écrit : >>>> 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 >>> >>> >>> -- >>> Benjamin Dreux >>> Analyste-Programmeur >>> Chaire de logiciel libre-Finance Social et solidaire >>> UQAM >>> Montréal >> >> > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
