Comments on: Best practices for client-side validation in Flex 2

By: Nash

Nash — Sun, 07 Jun 2009 20:10:59 +0000

Good thoughts on line of validation thinking.

Example using date validation
http://yasob.blogspot.com/2009/06/flex-custom-date-validation.html

By: emsebi

emsebi — Fri, 08 May 2009 09:43:50 +0000

help me
Balkan_Client
of what kinds is it ?
what to register site ?????

By: Geoff

Geoff — Mon, 16 Jun 2008 17:42:05 +0000

I like your best practice principles for validation, but I think there’s another that could be added, which is “When Possible, Don’t Permit the User to Make Mistakes in the First Place”. You can do a Change event check to boot out any non-valid characters before they even show up in the Input. For instance, I don’t think most people deliberately insert a letter into a telephone number, so most likely the letter is an accidental keystroke.

It’s not always appropriate, but passive rejection of invalid characters is the ultimate way to keep the user flow as seamless as possible.

Late post, I know, but any thoughts?

By: Colin

Colin — Wed, 12 Mar 2008 19:48:01 +0000

Aral, this was very helpful. Being very new to Flex, I wonder how this could be adapted to still disable the button when one of the fields is required and the user doesn’t type anything in it. Because the TextInput only seems to have methods based on user input, the button is still lit.
Thanks,
Colin

By: Mike

Mike — Mon, 26 Nov 2007 04:12:49 +0000

I’m new with Flex development and I stumbled upon your quick start on Validators. After implementing the quick start solution I felt that although it was nice, I’ve abandoned any color blind folks that might use my form. There needs to be visual indicators in addition to turning a border red. Also given that I’ve never seen an application on the web that disables the submit button by default, I’m wondering if that would just cause more confusion for the users (not to mention those pesky color blind folks, can they even see the difference between an enabled and disabled button).

I would love to have some ability to display the error tip in addition to turning the border red and have the error tip show up on every field that has an issue when the user tries to click the submit button. I think expecting the user to roll the mouse over the error field to see what is the problem is not user friendly.

At this point I’m about to abandon the Validators and just go back to displaying errors in red at the top of the form.

Have you had any additional thoughts on the validation topic?

Thanks in advance

Michael

By: vaibhav

vaibhav — Thu, 23 Aug 2007 10:51:44 +0000

i want an example of email validator.
mail me at pareekvaibhav@gmail.com

thanx in advance

-vaibhav

By: Plaigarizing blog posts is stupid at Aral Balkan

Plaigarizing blog posts is stupid at Aral Balkan — Thu, 15 Feb 2007 12:03:56 +0000

[...] RexyStudios, who ripped off my blog posts on User Interface Design Principles for Web Applications (ripped off copy here) and Best Practices for client-side validation in Flex 2 (ripped off copy here) are, according to their Founder and CEO, Anthony G. Persaud on their About Us page, a “new type of design/development type of group”. This must be a new type of design/development that apparently doesn’t respect the intellectual effort of others enough to give them credit for their work when copying it. What a horrible way to market a company that works with IP. Can you trust such a company with your own projects? If they don’t spare a thought to ripping off blog posts, what about source code and company secrets? In a line of work where trust and reputation are paramount, I cannot think of a worse way to shoot yourself in the foot. [...]

By: Matt Brailsford

Matt Brailsford — Tue, 24 Oct 2006 09:50:29 +0000

Hi Aral,

I have a question about this approach.

This works great for empty forms thats require input, but how would you work with edit forms? ie forms that are populated with existing data that requires editing.

Under this senario, the submit button would be disabled initialy even if the form is technicaly valid.

Matt

By: aral

aral — Thu, 31 Aug 2006 19:47:55 +0000

Hi Douglas, I didn’t separate out the model in this example since I didn’t want to complicate it further. I did create a version that had this, however, and I might publish that later myself because it’s a very valid question. It’s not that much more complicated however.

Personally, I don’t like the way formatters are implemented in Flex 2. I don’t find them very flexible. Would have preferred if they used a more event-driven process. Regardless, however, you have flexibility in assigning them in the controller part of your application.

Take a look at the Data Binding section for the MVC approach to binding. I would then add validators and formatters in the same manner.

By: Douglas Knudsen

Douglas Knudsen — Thu, 31 Aug 2006 19:37:35 +0000

I’d really like to see how you approach this topic when all sorts of bindings are invovled. For example, you have a textinput whose value is bound to a model variable and the model variable is bound to the textinput, AKA double binding. Where to put validators in this mix? Further, where to put formatters, eh?