flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Omar Gonzalez <omarg.develo...@gmail.com>
Subject Re: mx PostCode validator class
Date Tue, 06 Mar 2012 07:56:25 GMT
On Mon, Mar 5, 2012 at 11:31 PM, Justin Mclean <justin@classsoftware.com>wrote:

> Hi,
> > Yea, what about localizing the error messages.
> Already done unless I'm missing something? eg take a look at
>  wrongFromatError and resourcesChanged. The classes read values from the
> resource bundle and you can override the error strings if you want. No unit
> test exist for those methods as yet however.
> Justin

So I haven't found time to learn more about the new g11n methods you have
to implement to make the Spark validators work. But I'm curious as to what
the difference is in implementing those methods and just hooking into the
resourcesChanged like you have in your MX validators.
109 - 120).

Also, I haven't used ResourceManager at all. The times I've implemented
localization I've done so using my own implementations for updating my
views based off models. So I'm not sure what the usual ways are of working
with ResourceManager, but if I'm reading your code correct for the post
code validator, if the setter is used to override the value from
ResourceManager, and then the locale changes at runtime, then the error
won't update based on the current getter implementations. Is that correct
or am I misunderstanding something? I don't see any listeners for the
change events from the ResourceManager.

Omar Gonzalez
Apache Flex PPMC Member

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message