Repository navigation
Closure library support? #2
Description
Great project! Is there support for using this with Closure Library? I noticed the generated JS doesn't have the Closure Library namespaces at the tops of the files, which are necessary for use with the dependency framework of Closure Library.
Also, I don't believe the Closure Compiler can resolve dependencies / minify Javascript if it is served from a URL instead of being on disk.
I noticed in the code there is a TODO for allowing JS complication options to be passed in. I think this would take care of the first part of this issue. There should also be an option / management URL to write the JS files to the host server's disk for complication with the Google Compiler.
I can start hacking on these issues to fit my needs but I wanted to get your thoughts first. Let me know what you think...
Dylan
Activity
codedance commentedon Jan 5, 2012
Sorry for the slow reply. Was off sailing over the Christmas/New Year period! Back into the computers now.
Regarding the TODO for adding JS compile options. My thoughts were to have a servlet/config option (a config string) that would modify the JS compile behaviour. There are potentially a lot of options so one thought was to map the config string to method names via reflection.
Regarding writing compiled files to disk. I'd like to hear more about this (the use case).
I'm keen to support any work that fits within the project's goal ... a nicer tasting tofu :-)