Has anyone had the requirement to use more then one properties file for
defining field labels? We basically want the setup that
FieldLabels.properties is our 'default' settings that rarely ever get
change, and if our customers want to change field labels they can in their
own 'customer.properties' file. Right now I don't see anyway to have this
capability in Stripes. We did it in 1.4 by changing the
LocalizationBundleFactory interface and some of the other supporting classes
to take lists, but I would like to avoid having to do this again with 1.5.
Any thoughts or suggestions on how to handle this? Thinking of using a
custom locale picker, but I'm not entirely sure what that would affect, or
what it would really involve.
Thanks for the input!
-Nick
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
