enyojs/enyo — pull request #138 by vtomilin (2012-08-31 21:16:52+00:00)
Title: Made enyo compatible with Google Chrome Packaged Apps

Made Enyo core code compatible with Content Security Policy(http://developer.chrome.com/extensions/contentSecurityPolicy.html), namely inline scripting(reliance on enyo.bubbler) and using of "unload" window event handler.

I also got a version of Enyo sampler, running mostly fine(Jsonp's samples not working) as new style Chrome packaged app(i.e. sampler window loaded via chrome.app.window.create API).

What's not working is JasonpRequest as it violates violates Content Security Policy directive: "default-src 'self' chrome-extension-resource:". I am not sure if there's a way around that.

Note: debug version of enyo app can not be deployed as a new style Chrome packaged app still due to loader using forbidden document.write() API. However, debug version can still be deployed as old-style app, .i.e. in apps' manifest it should use "app": { "launch": { "local_path": "debug.html" } }.

Thanks for Enyo, it's marvelous!
--Vit