Hey Richard, I am not sure how can extending validation manager help. It has most of things private, especially __formItems. So by overwriting "validate" I cannot really influence anything there unless making my own internal storage of items there. I guess it would be possible with some hassle, but than it almost seems easier to just write own manager class.
For now it would be quite enough to be able overwrite method __validateRequired and check visibility there, but unfortunately it's private :/ Daniel -----Original Message----- From: Richard Sternagel [mailto:[email protected]] Sent: Thursday, February 21, 2013 4:00 PM To: qooxdoo Development Subject: Re: [qooxdoo-devel] Form validation feature: visibility check Hey Daniel, have you tried to extend the validation manager (by writing your own) and overwrite the "validate" method? http://manual.qooxdoo.org/devel/pages/desktop/ui_form_handling.html#validation http://demo.qooxdoo.org/current/apiviewer/#qx.ui.form.validation.Manager Regards Richard Am 21.02.13 14:13, schrieb Krejčí Daniel: > Hey, sorry for bumping this older mail, but I have similar issue. Some > widgets are set excluded upon some user condititon and there is > validation attached to it, which than fails and user cannot do thing > about it. > > What would be best practices to overcome this issue ? I have noticed, > that qx.ui.validation.Manager has method remove() but it removes whole > widget from validation, not only particular validation. > > Only thing that came to my mind is to loop through > getInvalidFormItems() after validation finishes and somehow filter out > those, that should not be validated due to visibility and other conditions. > > For field, that should not be required when hidden, it would be > probably best use binding between visibility and required properties, > although it will need converter function. It seems to me like a big > overhead just for this. > > Thanks for help > > Daniel > > *From:*Martin Wittemann [mailto:[email protected]] > *Sent:* Sunday, October 07, 2012 1:15 PM > *To:* qooxdoo Development > *Subject:* Re: [qooxdoo-devel] Form validation feature: visibility > check > > Hey, > > I've some problems with form validation. It's specific to my use-case: > > 1. an edit form is build with all possible fields with their > validators. E.g. field/productReference/which is required/when > shown/ > > 2. on setting the model for this edit form, the application takes > care of setting the visibility of the fields: if field in model then > field is 'visible' else field is 'excluded' > > Suppose a field that is marked required becomes excluded then a user > will not be able to ever get the form submitted. > > There surely are ways to bypass this scenario, but maybe it's nice > to support it by adding a visibility-check for fields in the > validate function of qx.ui.form.validation.Manager. > > I still can imagine that it might be useful to have a validation on > hidden items. I can think of a scenario where some visible input > fields fill a non visible input field and you still want to run the > validation on that hidden field. So I don't think that this i a > general pattern we should / could add to the frameworks code base. > > Regards, > > Martin > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
