Hi Pierre,
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?
Best regards,
Geert
--
Geert Bevin Uwyn bvba GTalk: [EMAIL PROTECTED]
"Use what you need" Avenue de Scailmont 34 Skype: gbevin
http://www.uwyn.com 7170 Manage, Belgium AIM: geertbevin
gbevin at uwyn dot com Tel: +32 64 84 80 03 Mobile: +32 477 302 599
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
