Re: Old fashioned debugging

GWT.log() prints to the browser console (using console.log()) in SDM, and is compiled-out in prod mode.

And java.util.logging can be used otherwise (the default in prod mode is to compile out everything below SEVERE –the default value of gwt.logging.enabled– and to respect gwt.logging.logLevel in SDM). I have never tried it but if you you could possibly set gwt.logging.logLevel to DEBUG or similar and setup remote logging, and then adjust the configuration of java.util.logging on the server-side through JMX, without restarting neither the SDM CodeServer nor your servlet container.

On Thursday, December 11, 2014 5:40:31 AM UTC+1, Blake wrote:

Greetings,

Before real debuggers were available, we used to just use print statements.  After that we had libraries that would allow us to control what debugging prints got activated based on a config file or command line arguments.  At that point we didn't have to get rid of our debug statements on the production system.  All we had to do was not enable them with the config file or command line arguments.  Log4j works a lot like this.  Although it took more time to debug because you sometimes had to add more print statement to see something new and then re-build, it did work.

With all the trouble setting up SDM and the subsequent limitations, I wonder if an API exists or can be easily built so that arbitrary debug print statements can be added to front-end code (in Java) that would magically appear on the backend console or somewhere where the IDE can display them without affecting the display or execution of anything on the front-end?  Of course this would work with some sort of backend config file to enable/disable particular groups of debug print statements ala-Log4j.  All debug prints would be disabled by default.

I am in no way suggesting we abandon SDM in any way.  I am just wondering if something simple-minded like this is available or can be easily added.  Of course the trick is to do the print on the front-end code but have it appear in the backend IDE output.

Another cool enhancement, if possible, would be to allow the addition of debugging print code on the front end without restarting the system.

Just some ideas.

Thanks.

Blake McBride

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.