I looked at the changelog on Github, and while there is certainly a lot of good stuff in there, for such a big release I would expect more information on some points, such as 'determinePreferredLanguage' or 'teaches directive custom translate-value-* attr'. Or link the commit ids to the commits (and link to relevant issues).
Angular-translate 2.0 released
11–14 of 14 posts
Re: Angular-translate 2.0 released
#12I looked at the changelog on Github, and while there is certainly a lot of good stuff in there, for such a big release I would expect more information on some points, such as 'determinePreferredLanguage' or 'teaches directive custom translate-value-* attr'. Or link the commit ids to the commits (and link to relevant issues).
Yeap you're right, the changelog generation didn't work very well because our commit messages weren't always very specific. This will become better in the future.
For further information, checkout this G+ post: https://plus.google.com/+PascalPrecht/posts/V5GtNp1tU27
Re: Angular-translate 2.0 released
#13More information about the release can be found here: https://plus.google.com/+PascalPrecht/posts/V5GtNp1tU27
Re: Angular-translate 2.0 released
#14Almost a year ago when this project was announced on angular google group I was looking for a i18n solution for my app, I tried it but the negative performance impact made me discard it. Its approach of implement i18n through filters and directives relying on angular dirty checking make your app really slow If you have a regular amount of i18n strings. I ended up generating different templates for each language with…
You are right, dirty check is not the best thing when it comes to performance. However, we've updated the directive to only set up watches when needed. Which means, when you don't change the language at runtime, but kick off some $digest cycles, they don't get re-evaluated. So this should be an performance boost. Filters always set up watches, if you use filters, well... deal with it. You could use the directive. ang…
"Conditional watches" on the directive sounds good, I will try it. Also gettext support will be great, the use of existing i18n tools is a must have.