Help with Super Dev Mode not showing content

[rjcarr]

I have an old project (been around since the early days of gwt) that's pretty large (the compiled javascript file is about 600KB).  I'm using GWT 2.7 and at some point a while ago the old dev mode stopped working (basically the browser wouldn't load the plug-in) and so I've lived without it.  I didn't use it that much so I plodded and trudged through with development and eating the 90-180 second compile times for every change.

But now I finally have a breather and have time to look into super dev mode.  The write-up on it seems a bit old but I got it working without much trouble.  And it all seems to work fine using the bookmarklets and the code server.  However, my application is split up into (visual) sections and when trying to load one of the sections it simply doesn't work.  As in, you click the section tab for it to open and just nothing appears.  Turn dev mode off and everything is fine.

There's no indication of any kind of problem in the browser (chrome) nor from the code server (if that even makes sense).  It just doesn't work.  No indication of anything in either the "sources" nor "console" sections (or anywhere else) of the development tools.  

Is there anything else I can do?  It's only one section (of 6) that's having problems.  It is the most complicated section, but as I said turning off the dev mode everything is fine.

I'm just looking for some way to tell something to be more strict and alert me to problems.  Ideas?

Thanks!

[Jens]

Sounds strange. 

You can open Chrome Dev Tools and on the sources tab there is a small "pause" icon on the right which says "Pause on exceptions". You can even tell Chrome to pause on any exception regardless if caught or not. 

So you could start your app and before clicking the tab that does not work you could activate that Chrome feature to see if any exception is thrown that might not reach the browser console for any reason.

Alternatively you could set a break point in Chrome debugger and then step through your code until it might fails. You could also place a GWT.debugger() call into your Java code and Chrome will stop at that location just like with break points.

Also as a general hint: If you use GWT 2.7. then the bookmarklets are generally not needed. When you launch the SuperDevMode CodeServer it will generate a special <modulename>.nocache.js file that triggers recompilation whenever you reload the browser. However I think GWT 2.7 has a timestamp bug and if that <modulename>.nocache.js file already exists because you have done some normal compilation then it might happen that the CodeServer does not replace that file. So to be sure you can delete the GWT output folder, restart SDM and then deploy the app with the newly generated <modulename>.nocache.js.

-- J.

[Robert J. Carr]

Hi Jens-

Thanks, I also thought of using the debugger and I think I might already have a lead.  Great advice!  I didn't know about the other debugging features you mentioned so I'll make a note of those.

I am finding that I need to use the bookmarklets most of the time.  It isn't a major nuisance so it isn't a problem, but thanks for the info.

I think the debugger will lead me to the problem so thanks again.  If you're interested in what I find out please let me know.

Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/UNXCyvjnnTs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Robert J. Carr]

Hi Jens-

Just letting you know I found the problem using the "pause on exceptions" feature.  Handy that!  Thanks for leading me in the right direction!

Robert