the slides are here: http://redhat.slides.com/vszocs/debugging-ovirt-gwt-applications?token=brh5Tzaz

I've made some new discoveries while working on this, the biggest one is that SDBG (link below) actually works for oVirt WebAdmin!

This means there's a viable alternative to existing GWT debug method, which doesn't restrict you to using an ancient (NPAPI-compliant) browser, while still being able to use Java IDE (Eclipse) as well as reaping the benefits of SDM code server (fast incremental recompiles).

If you're an oVirt UI maintainer, I highly suggest you to join this session, spend ~1 hour of your time and in return, get the knowledge to be more productive when dealing with our GWT code.


On Tue, Mar 28, 2017 at 3:56 PM, Vojtech Szocs <vszocs@redhat.com> wrote:
Update: moving the session to Tue, Apr 4 @ the same time as originally planned.


PS: Greg sent me a link to SDBG project [1] which allows you to debug GWT application via Super Dev Mode from within Java Eclipse IDE. I'm going to cover this in the presentation as well.

[1] http://sdbg.github.io/

On Mon, Mar 27, 2017 at 8:09 PM, Vojtech Szocs <vszocs@redhat.com> wrote:
Hello UI devs,

with oVirt master UI using the latest GWT SDK [1], I'd like to host a live demo session with two goals in mind:

a, explain how the (Java IDE based) Classic Dev Mode works and mention its limitations
b, explain how the (browser based) Super Dev Mode works and encourage people to start using it to boost their productivity
The Classic vs. Super Dev Mode are two possible ways to debug GWT applications. This session will give you the knowledge to decide which one to use in a specific situation.

Proposed time: Mon, Apr 3 @ 5pm CET / 6pm TLV / 11am US EST. (This can be changed as needed.)

Let me know if this kind of session interests you or if the above time doesn't fit you but you'd still like to join.