Make it possible for a global localisation map to be available to all VStar code, including plugins, permitting LocaleProps.get() to be called from anywhere. A plugin could supply its own localisation string property file that is read and added to the global map. To avoid conflicts, the (fully-qualified) name of the plugin class (or similar) would have to be used when adding to and retrieving from the map, e.g. LocaleProps.get(MyClass, key).
Log in to post a comment.