Re: SDM with modular-webapp - no client-side debugging possible

2014-11-23 Thread Thomas Broyer
…where SDM will write a .nocache.js file that compiles on load. This is how DevMode calls SDM under the hood. -- 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

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-22 Thread Kay Pac
I'm not sure I understand how launcherDir would allow you to recompile on load? Doesn't this just set an output directory? On Saturday, November 22, 2014 1:34:15 AM UTC-8, Thomas Broyer wrote: > BTW, how about using to have "recompile on load" instead of > using the bookmarklets? > > On Saturd

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-22 Thread Thomas Broyer
BTW, how about using to have "recompile on load" instead of using the bookmarklets? On Saturday, November 22, 2014 10:33:02 AM UTC+1, Thomas Broyer wrote: > > Inspect the DOM, you might have a transparent element layered on top of > the SDM dialog (and have a look at the zIndex for each; the SD

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-22 Thread Thomas Broyer
Inspect the DOM, you might have a transparent element layered on top of the SDM dialog (and have a look at the zIndex for each; the SDM dialog uses a very high zIndex but maybe you're using one even higher?) On Saturday, November 22, 2014 7:42:22 AM UTC+1, Magnus wrote: > > I see, I am on my own

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-21 Thread Magnus
I see, I am on my own with this issue... Nevertheless, I post my proceedings here. Maybe it helps someone someday... Well: There must be some side effect between the SDM dialog box (div) which shows "Choose a module to recompile" and my library test code. My library test code also is a DialogBox,

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-19 Thread Magnus
Could please someone give a little feedback? How could you further localize the problem? For example, normally, when selecting "DevMode On", there is something going on in chrome's "network" tab: dev_mode_on.js is loaded and when you click on "compile" a lot of messages are written. In my case,

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-17 Thread Magnus
I have reproduced the following a dozen times: - Begin with a new app based on modular-webapp archetype: works! - Add my own gwt library: - add dependency to the modular-webapp's client pom - add inherits-statement to modular-webapp's client gwt module xml file - add

Re: SDM with modular-webapp - no client-side debugging possible

2014-11-17 Thread Magnus
In the meantime I found out this: The app was using a gwt library, which is what I am currently testing. When I comment out the code that uses the library (while leaving the pom as is), it works! The code is just this: TestBox t = new TestBox (); t.show (); When removing it, debugging works.

SDM with modular-webapp - no client-side debugging possible

2014-11-16 Thread Magnus
Hi, when running an app built with maven and the modular-webapp archetype in SDM, client-side debugging does not work. I start SDM in two terminals like this: mvn clean install -Dgwt.draftCompile cd *-client && mvn gwt:run-codeserver -Ddev mvn tomcat7:run -Ddev Then I can open the app at h