16 Sep 2011 12:24 AM #1
I tried the Ext.LocaleManager, but it doesn't fit my environment. I'm using my own one now, and it really works for me, and I'd love to have a few feedbacks. You can find it on GitHub:
I'm improving it now to support dynamic translation on the server side, a requirement which I have here in my company. People develop new views everyday, they upload them in production, but we don't always have translations for them, so basically we need the server to be able to know "what" translations need to be done. Meanwhile, the non-translated views (or resources) will be shown in English, the default language.
16 Sep 2011 4:42 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Problem with using Ext.Loader in production is it's usually not present.Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services email@example.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
18 Sep 2011 7:05 PM #3
It depends what kind of production you have. We use ExtJS for our internal intranet websites, it's very fast, if there is a change to be made we quickly update a file or add a few... it's a very dynamic environment.