> > It supports either a single postcode format or an array of postcode > formats. Formats are defined as strings consisting of N,A,CC,- or space > where is N is a number, A is a letter, CC is country code (optional) and > "-" or space for formatting. eg "NNNN" is a 4 digit postcode. "NNNN AA" is > 4 digits, followed by a space followed by 2 letters.
> It doesn't validate for ranges of numbers or exact letters. I've > considered a way of setting a call back that calls a user defined function > to do this. > This part sounds like a good idea for tricky postal codes. > > Would anyone like to see this added to the SDK at some point in the future? > I think the more validators we can add, that bring value, the better. > For contribution like this what should the namespace be? mx.validators or > org.apache.flex.mx.validators or something else? > I've been using org.apache.flex.spark... for the validators I put in my whiteboard area. I think its still up for discussion whether we want to eventually change the namespace, we talked about it briefly but I don't think its something we want to do in the 4.x.x branch just so we don't add an additional barrier to switching from Adobe Flex to Apache Flex. > > Any interest in a similar spark version? > Yes, I was wondering why you went MX as opposed to Spark. I guess a lot of people are still using MX components, I haven't written in MX since Spark was released. :D -- Omar Gonzalez s9tpep...@apache.org Apache Flex PPMC Member
