Use gwt logging in playn-html

[samskivert]

Is GWT's built-in logging now better than gwt-log? If not, I'd rather provide this as an alternative to HtmlLogEnhanced instead of replacing it. One already has to opt-into HtmlLogEnhanced, so they could opt-into HtmlLogGWT or something like that.

[korzha]

I consider gwt logging has several advantages:

• It emulates java util API so if someone uses it already in the project (e.g. I'm using) it will reduce code size (because there is no need in gwt-log library for me)
• Gwt logging is supported by gwt so I think this is better to use in the library

I thought about providing alternative HtmlLogGWT but I would want PlayN use gwt logging too to reduce code size.

[korzha]

I think gwt logging and gwt-log derived from one library because they both have similar loggers but gwt logging support is stronger. For example, take a look at these CLs:

https://gwt-review.googlesource.com/#/c/8270/ https://gwt-review.googlesource.com/#/c/8224/ https://gwt-review.googlesource.com/#/c/8140/

[samskivert]

By default PlayN uses neither GWT logging, nor gwt-log. It uses a very simple native method that just writes to window.console.

Since GWT logging is built-in, I don't mind using GWT logging by default instead of the window.console code. Assuming the same user experience is preserved: that logging goes to the JavaScript console in the browser by default.

So if you want to redo the patch to change HtmlLogSimple to use GWT logging, and leave HtmlLogEnhanced as is, that is fine with me.

[korzha]

Ok

[korzha]

I've moved implementation into HtmlLogGwt.

[samskivert]

Great, I made a couple of small tweaks (and a bug fix), but otherwise it's ready to go!

[korzha]

Thanks!