> > > I'm not sure we have a way to manage random JS files in the tool chain. > JS files that use goog.provide can be included in a SWC and will be copied > to the output folder by the compiler. So you may want to consider adding > some sort of goog.provide to that file.
interesting. Some example already set to see how to do this? something already in place to take as example an make my own ? > Otherwise, folks will have to > manage it like any other asset. The tool chain does support links to > random JS files via the inject_html directive. > so, gol.provide will be for bundle in swc...while inject_html will put the line in my index.html right? > > Also, if this code can be called by other code in JS files being sent to > the Google Closure Compiler for minification/optimization, then an externs > file for this file will need to be generated. > I think this is not the case. MDL talks about it as a "companion", so they provide some class css and maybe js, but they suppose the dialog-polyfill is setup and in place. Right now externs are an obscure concept to me, where I could read about it and whats behind? -- Carlos Rovira Director General M: +34 607 22 60 05 http://www.codeoscopic.com http://www.avant2.es Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC S.A. La finalidad de dicho tratamiento es facilitar la prestación del servicio o información solicitados, teniendo usted derecho de acceso, rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
