#1493 closed defect (fixed)
Fix xdomain loading to work with i18n resource bundles
Reported by: | James Burke | Owned by: | James Burke |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Loader | Version: | 0.3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
xdomain i18n resource loading is broken. Here are some quick notes on things I need to fix to get it to work:
Issue with nls.dojo_ flattened resources. When can we load them? Have to wait until dojo onload is about to fire, then don't fire, but instead trigger the preload to happen. Hmm. Ick.
For regular, non-flattened resource bundles:
- Look for dojo.requireLocalization
- Async load those packages, but only the first path, not all parent locales.
- Have a task that will flatten resources but don't combine bundles.
- Need to know if a language has a flattened bundle, or if we should grab root? Or is this is a build property where you tell it which ones you want to support? Makes it harder to share libraries with others. How can we register "supported languages" for a 3rd party package?
- loader_xd.js: need to change dojo.hostenv.loadUri to return true/false. What about the callback? The i18n stuff seems to rely on it. So need to overwrite dojo.requireLocalization() and not do the callback. Then, when we make the xd.js file for nls files, do the module assignment code that happens in the loader.js callback. Don't have to worry parent locale stuff, because it should be flattened.
Change History (8)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
severity: | normal → blocker |
---|
comment:4 Changed 14 years ago by
Milestone: | 0.4 → 0.4.1 |
---|
This is partially working:
If you do a custom build that includes resources that use flattened bundles, that case will work.
What doesn't work right is trying to xd load a resource that uses bundles that was not part of the custom build. Pushing that work to 0.4.1.
comment:5 Changed 14 years ago by
comment:6 Changed 14 years ago by
comment:7 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
(In [6183]) References #1493. These changes allow flattened resources in a custom build to be used in xdomain builds. There may be an encoding issues with the xd bundles, but this is a definite improvement. Still need to do the work of being able to xd load bundles that are not part of the custom build