Make Dojo work with Adobe AIR

[dylan]

Make changes to Dojo to allow Dojo to work within Adobe AIR.

Work done by SitePen? and Adobe, contributed under SitePen? CCLA and contract between SitePen? and Adobe.

[dylan]

Documentation/known issues

[dylan]

patch listing tests and features for Adobe AIR

[dylan]

patch of build profile for Adobe AIR

[dylan]

test cases for Dojo inside Adobe AIR

[dylan]

Somewhere in the source or documentation, we should add "Adobe and SitePen? collaborated on these modifications."

[dylan]

patch for core for Adobe AIR

[dylan]

patch for dijit for Adobe AIR

[dylan]

patch for dojox for Adobe AIR

[dylan]

patch for Adobe AIR's application.xml config file

[James Burke]

For dojo.patch, it has a branch point on dojo.isAIR (should that be dojo.isAir?) for things that call setTimeout. I would prefer not to have a branch and to preserve the use of dojo._scopeName within AIR. Instead of having the branch points can we do something like (for example):

setTimeout(function(){window[dojo._scopeName].loaded();}, 0);

This assumes:

• "window" exists in AIR
• We don't leak in browsers like IE with those closures.

I think we are OK with the closures, not sure about "window" support in AIR.

[James Burke]

Ugh, forgot to scrub that window may not be in all our hostenvs. So window might not be so good. "this" instead?

[James Burke]

On further reflection, the closure path used in the patch should be sufficient for all hostenvs, and it will preserve the scope functionality. That was the whole point of the scope changes: so that you do not need to modify the library code to know about it unless you are making string IDs or string callbacks. So this should be sufficient, no need for a dojo.isAIR (or dojo.isAir) check:

setTimeout(function(){dojo.loaded();}, 0);

[dylan]

post-commit refs hook seems b0rken... this landed in [12311]

[dylan]

Moving documentation issue to #5883