Comments on: Flex Validation – Future Directions

By: Shanon

Shanon — Fri, 04 Sep 2009 02:46:40 +0000

The hamcrest matchers look great. I haven’t written any validation routines yet so I’ll see if I can leverage your work do some of the heavy lifting.

On an unrelated note, your old colleagues at Mazda say hi

By: Drew Bourne

Drew Bourne — Fri, 04 Sep 2009 02:10:08 +0000

I’ve build a validation system with the same intent using MXML and the hamcrest matchers. By combining and nesting matchers you can very quickly create any sort of custom validation.

http://github.com/drewbourne/hamcrest-as3/tree/master

By: Roland Zwaga

Roland Zwaga — Thu, 03 Sep 2009 18:16:20 +0000

Good to hear you’re going OS Shanon! I already have some ideas on how to hook these validators up to the new stage processing functions of Spring Actionscript, I’ll keep watching your progress

By: Shanon

Shanon — Thu, 03 Sep 2009 08:40:00 +0000

Thanks for the feedback Roland

Oh yes I’m definately looking to open source the project. I hope to release it in the next month time permitting. It won’t be very feature rich at that stage but it will be usable and ready to evolve based on user feedback.

By: Roland Zwaga

Roland Zwaga — Thu, 03 Sep 2009 08:05:37 +0000

Very nice effort! Flex form validation is indeed sorely lacking, your solution so far looks very promising.
The only nit-picky criticism I’d come up with right now is that your interfaces aren’t prefixed with an ‘I’, which is common in actionscript. So IValidator and IValidationBuilder would be more straightforward for a lot of people.

Are oyu planning on opensourcing your lib?

cheers!