Right now a container developer has to move a bunch of static files around to inject container behavior into a page. I'd like to see the core and samplecontainer pieces managed using the same JS infrastructure as the iframe hosted JS. This means that we get minification, dependency management, jsdoc generation and all that.
2010/2/9 ๏̯͡๏ Jasvir Nagra <[email protected]> > I don't understand the consequences of moving directories but +1 on > renaming > gadgets.container to something other than gadgets.container. > > On Tue, Feb 9, 2010 at 10:00 PM, Paul Lindner <[email protected]> > wrote: > > > Hi, > > > > One thing that always bothered me for containers was the problems getting > > the page all set up. You had gadgets.js some other utils etc. > > > > Unless no one objects I'm going to move javascript/container/gadgets.js > and > > friends to features/shindig-container. > > > > I will also change the namespace gadgets.container to shindig.container > > (with a deprecated backwards compatibility reference) > > > > This will allow a container page to just reference a single client side > js > > file like so: > > > > <script type="text/javascript" > > src="../../js/core:rpc:shindig-container:pubsub.js?c=1&debug=1"></script> > > >
