Ah, I see. Thanks.
On 24 November 2011 23:06, Meikel Brandmeyer (kotarak) wrote:
> Hi,
>
> the ResourceBundles themselves are memoized by the Java runtime. You can
> reset this cache with ResourceBundle/clearCache. Then the underlying
> ResourceBundle will be retrieved again on the next access.
Hi,
the ResourceBundles themselves are memoized by the Java runtime. You can
reset this cache with ResourceBundle/clearCache. Then the underlying
ResourceBundle will be retrieved again on the next access. Then the
memoization does not trigger. But the memoization itself is probably
premature o
Hi Meikel,
Thanks for this library.
I noticed that each bundle's keyset is cached via memoization. I believe
this prevents adding more bundle properties at runtime (e.g. during
interactive development).
Is there a way to "reset" a resource bundle? Is this something that you
might consider in a f
2011/9/5 Meikel Brandmeyer (kotarak)
> Salut Laurent,
>
Hallo Meikel,
>
> Am Sonntag, 4. September 2011 21:51:20 UTC+2 schrieb lpetit:
>
>> Interesting!
>>
>> I don't see the link between the README page and the currrent state of the
>> API, though. Is the README ahead of time, or is the desig
Salut Laurent,
Am Sonntag, 4. September 2011 21:51:20 UTC+2 schrieb lpetit:
>
> Interesting!
>
> I don't see the link between the README page and the currrent state of the
> API, though. Is the README ahead of time, or is the design it is describing
> an intermediate state which should be remove
The README represents an early draft before simplicity ensued :)
FWIW, here's how it's used in Seesaw:
https://github.com/daveray/seesaw/wiki/Resource-bundles-and-i18n
Dave
On Sun, Sep 4, 2011 at 3:51 PM, Laurent PETIT wrote:
> Interesting!
> I don't see the link between the README page and the
Interesting!
I don't see the link between the README page and the currrent state of the
API, though. Is the README ahead of time, or is the design it is describing
an intermediate state which should be removed ?
Cheers,
--
Laurent
2011/9/4 Meikel Brandmeyer
> Dear international Clojurians,
>
Dear international Clojurians,
I'd like to announce j18n. A small wrapper around ResourceBundles to provide
easy internationalization of Clojure applications. j18n will power the i18n
features of the upcoming seesaw release.
The interface consits (at the moment) of a single function: resource.