I'm trying to use ext-js, which was just renamed to Sencha, in a module. For reasons I'm not familiar with, in order for ext to work at all, the script elements and css link element that reference the ext js and css files need to be in the head element. If these files are reference from the body element, ext doesn't work at all. Currently I'm using the Opensocial Development Environment version 0.9.2. When I put these script elements and the link element in the Content element of my Module, they get put into the body element of the html document that gets generated and put in an iframe when the module gets deployed to Shindig. This means I can't use any of the ext functionality as things are currently. As far as I know, there isn't a way to make these elements go into the head element instead of the body element. It would be helpful if there was some way to specify if a script or link element should be put in the head or body of the generated html page that goes inside the iframe.
Regardless of my issue with ext, being able to specify if a link or script element goes in the head or body of the generated html document inside the iframe seems like a useful feature that would encourage portability of modules.