Words to the wise, David ‘Bombe’ Roden <bombe@pterodactylus.net>
wrote:

You could implement a controller which just listens to whether the
language is being changed and which then iterates over all controls
and sets the corresponding string from a resource bundle depending on
the new language string. Whether that is simpler than your solution, I
cannot say.
--
Claus Dragon <clauskick@mpsahotmail.com>
=(UDIC)=
d++ e++ T--
K1!2!3!456!7!S a29
"Coffee is a mocker. So, I am going to mock."

- Me, lately.

On Sat, 08 Mar 2008 14:45:44 +0100, David ‘Bombe’ Roden
<bombe@pterodactylus.net> wrote, quoted or indirectly quoted someone
who said :

see http://mindprod.com/jgloss/localisation.html

You don't necessarily need Runnables. You can change
localized texts in the Event-Dispatch-Thread.

A workable approach is to have custom components,
for example an on-the-fly-label that stores a key
for the text lookup, listens to a custom property
that notifies the component when the Locale has changed.
On Locale change, the component can update its text
by re-reading the resource for its key.

Note that Locale has no bound property that can be
observed for that case. So a common approach is to
set a new Locale and then fire a change in a custom
(bean) property somewhere.

-Karsten