Support for runtime-loaded CLDR

[gigafied]

My current project is using AMD w/ Ember. Thus during dev, we have no build step. Without the ability to load the CLDR data on-demand, I am unable to implement ember-intl.

Apart from my specific issue though, it would be good to have an option to create Locales and register them as needed during runtime. Say our backend were to have language management, with the ability to add new languages or remove languages. Currently this isn't possible as the full list of languages needs to be included when building the JS.

[jasonmit]

@gigafied when you say locales are you referring to the CLDR, translations, or both?

/cc @ericf in reference to the need to extract the broccoli logic out into its own project so people can have more finite control over the extraction.

[gigafied]

Both.

[jasonmit]

@gigafied I have changes to resolve portions of your requirements in #68.

However, The CLDR extraction logic hasn't been solved yet. But I think the path will be to expose the new broccoli plugin (https://github.com/yahoo/ember-intl/pull/68/files#diff-616282132dc0285e5107b705ebf796eaR1) as a third party module where you can use to push CLDR to your asset tree instead of app tree.

I can provide documentation around all of this once it's complete.

[jasonmit]

#41 I'm going to use this issue as the reference for this feature since this is a duplicate.