Hi Justin, FYI, few years ago, I did a closer examination of existing limitations of current DateFormatter from Flex3 and suggested a few fixes for the following issues (old JIRA numeration):
Fixed SDK-23069 <https://bugs.adobe.com/jira/browse/SDK-23069>[Localization]: DateFormatter.parseDateString does not support non-latin characters in month and days names; Fixed SDK-23075 <https://bugs.adobe.com/jira/browse/SDK-23075> “[Localization]: DateField should support “MMM” and “MMMM” for formatString”; Fixed SDK-26715 <https://bugs.adobe.com/jira/browse/SDK-26715> “DateFormatter “parseDateString” method cannot parse dateString value formatted with non default en_US format”; Demo: http://jabbypanda.com/blog/2010/12/datefield4-component-for-flex-4-sdk/ If you are interested in code, it is available at the Github https://github.com/JabbyPanda/DateField4 On 20 April 2013 08:57, Alex Harui <aha...@adobe.com> wrote: > > > > On 4/19/13 5:28 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > > > > > Alex if you could review the tests as I'm not 100% familiar with > Mustella I'd > > appreciate it. > > > Looks like the right pattern for testing methods. Good job! > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
