I noticed the same thing when using closure library in our dev environment.
First, I highly recommend setting up closure compiler. In addition to making your JS output smaller for production, it has multiple modes of operation including a mode that figures out your JS dependencies and concatenates all the necessary files into one file. This operation runs very fast (compared to doing an actual compilation) and your code will not be obfuscated for easier debugging. However, since the code is concatenated, the single JS file will be huge and hard to navigate during debugging. I had been operating in this mode until recently, when I finally sat down and configured plovr. In addition to being able to recompile your code on every refresh, plovr can also serve out all closure library and your app's JS files separately and does it in a multithreaded manner, very quickly. For me, plovr has been absolutely amazing. Lastly, in your development environment you could run a simple Apache server with a docroot pointing to your source files and have your app code load from an alterate url (http://localhost:<other port>/...). I have not actually played with this configuration, but it should work much better than serving these static files through dev_appserver.py -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
