Roadmap

For 0.2

Javadoc (IN PROGRESS)

Obviously.

Locale-aware bundles (IN PROGRESS)

With the same characteristics as the existing MessageBundle: return the key if no match found.

Make two versions: one with fixed sources, another with cacheable sources. Without resorting to Guava!

NEARLY DONE. The code is working, but the API is a mess.

New API

Related to the point above. First idea:

• MessageBundle stays as is (except it has locale support), and is modifiable;
• there is a LoadingMessageBundle which is not modifiable once created.

Or maybe a FixedMessageBundle, and MessageBundle is an abstract class? But then, what API for modification? MessageBundle.modify()?

In the future...

MessageFormat support?

To copy what ResourceBundle does. Also printf()-like support?

Cache expiry?

The first implementation of an i18n bundle will record lookup results (failures and successes) permanently.

Try and devise at least a failure expiration policy? What about success expiration policy?

Global factory?

Right now, a class is created in each package using this library for each message bundle it wants. Try and find a way to have bundles centralized. Find a good design pattern for this.