...
[10:53:52 CDT(-0500)] <cindyli> this path can be relative or absolute. but since you are accessing template thru a web server, absolute paths may not suitable or work, but you can certainly use the web absolute url such as "http://mysite/UIO-template-path" " as long as your template directory is exposed to the public
...
[14:02:25 CDT(-0500)] <yzen> i believe so, it's not frozen
[14:04:06 CDT(-0500)] <cindyli1> no, but the string is not updated with the new one, yzen
[14:05:26 CDT(-0500)] <yzen> cindyli1: right, makes sense, options for it are copied, we can avoid it if we "preserve" the messageBase option with mergePolicy
[14:06:06 CDT(-0500)] <yzen> so we can have a grade: fluid.uiOptions.messageResolver that is a "fluid.messageResolver" along with a custom merge policy
[14:06:17 CDT(-0500)] <yzen> this will let you modify the base from the outside
[14:11:57 CDT(-0500)] <cindyli1> yzen, Justin_o and I were thinking what's the best way for integrators to modify those strings. It doesn't make sense to modify i18n.js. If we provide an API, the auxiliary schema might be the best place for it. What do you feel about it?
[14:12:26 CDT(-0500)] <yzen> cindyli1: i think that would be best
[14:14:01 CDT(-0500)] <cindyli1> ok, thanks, yzen
[14:14:26 CDT(-0500)] <Justin_o> cindyli1: would you want to take in a message bundle into the schema to be merged with anything from the i18n.js
[14:14:27 CDT(-0500)] <Justin_o> ?
[14:15:01 CDT(-0500)] <cindyli1> yes, Justin_o
[14:33:42 CDT(-0500)] <cindyli1> anastasiac: Bosmon, yzen, the updated auxiliary schema - http://wiki.fluidproject.org/display/fluid/Auxiliary+Schema+for+UIO+Preferences, your feedback please
[14:38:42 CDT(-0500)] <anastasiac> thanks, cindyli1