Geert,
Not always. For exemple it can be:
- through "plugins" like rife-crud: the crud bundles will be put at
the top of the list (see below the patch I use for
CrudElement.decorateTemplate)
- and/or through site configuration: then the final element, for
exemple the Add one, can specify a required bundle basename, that
will be put above the crud ones in the list.
I was just thinking about this. Actually that would not be a good
approach with your current implementation, unless there's something
that escapes me. Each element gets an instance of TranslatorSupport
injected. This can either be a global one or a local one. If it's a
global, and the element adds element-specific resource bundles to the
translator, do you think that it's a good idea that these will
automatically be present for all the other elements that use the
global translator? It seems to be that this is not what the user
would expect. What do you think?
With current BaseI18n and VersatileI18n implementations, each element
instance has its own translator instance. The point is not only about
resourcebundle basename list, but also about locales. Two elements can
work with the same basename list but with different locales.
It may be possible to work with a common default translator, and only
instenciate specific one if needed, i.e. as soon as non default basename
or locale is specified, but then some running checking will be needed.
Regards
Pierre
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
