GWT and debugging in the browser
Posted: Sat Dec 22, 2012 12:01 am
From what I've seen, Servoy is using Google Web Toolkit to produce the Servoy "operating environment" and our solutions in the browser.
This produces very dense and super minified code, which is great for a production environment, but isn't spectacular for when you're trying to debug in the browser.
When I was just getting started developing a test app, I was running into a problem on the client side (Cannot access property "dataProviders" of undefined) and had to spend quite a bit of time stepping though this code and deciphering what was gong on. Is there a way for when you "Export to WAR" to produce un-minified, somewhat more human readable code for deploying to test environments?
This produces very dense and super minified code, which is great for a production environment, but isn't spectacular for when you're trying to debug in the browser.
When I was just getting started developing a test app, I was running into a problem on the client side (Cannot access property "dataProviders" of undefined) and had to spend quite a bit of time stepping though this code and deciphering what was gong on. Is there a way for when you "Export to WAR" to produce un-minified, somewhat more human readable code for deploying to test environments?