On Thu, Mar 6, 2008 at 5:29 PM, Mike Samuel <[EMAIL PROTECTED]> wrote:
> On 06/03/2008, Bruno Bowden <[EMAIL PROTECTED]> wrote: > > > > Shindig should be able to use Caja in debug mode with non-minified > > versions of those added files. I'm not sure of the correct way to do > that. > > > For debugging or for other reasons as well? > > Does shindig have a production vs. development mode switch? Yes, but it's not quite perfect yet -- passing debug=1 in the iframe urls (or debug: 1 in the JSON interface) will cause the loaded JS to use the original source files. > > > > > > On Thu, Mar 6, 2008 at 5:09 PM, Mike Samuel <[EMAIL PROTECTED]> wrote: > > > > > Attached is a patch. > > > > > > Kevin suggested that it'd be a good idea to get the added files from > the > > > Caja JAR instead of copying them into the shindig source tree. > > > He also suggested consolidating and minifying those files in the JAR > > > since shindig doesn't do runtime minification. > > > > > > That's a great idea but I'd like to do that in a separate change. I > > > will talk to Mike Stay on Caja to make sure the jar contains those > files or > > > a minified JS bundle in future versions. > > > > > > > > > > > > features/caja contains runtime support for Cajoling of gadgets. See > > > code.google.com/p/google-caja > > > > > > DOMita provides a partial fake DOM Level 2 implementation that gates > > > gadget access to the DOM > > > > > > This change adds DOMita and updates the html sanitizer used when the > > > Caja feature is enabled. > > > > > > Some of the functionality in container.js is redundant with domita, > and > > > is removed, but none of that functionality should be triggered when > the Caja > > > feature is disabled. > > > > > > > > > > > > > > > cheers, > > > mike > > > > > > > > -- ~Kevin
