As the page explains, the "Dev Mode On" and "Dev Mode Off" should be added as bookmarks to your browser. You'll then use the bookmark when visiting your GWT app to start a Super Dev Mode session.
I wrote a while back about how Super Dev Mode works; hopefully that should clarify things for you.
Update: note that with GWT 2.7, superdevmode is enabled by default within devmode, so you just launch DevMode "as usual" and it actually uses SuperDevMode under-the-hood, with a "compile on load" hook so you no longer use the bookmarklets. The "compile on load" hook can also be enabled with CodeServer using the -launcherDir
argument (point it to your war folder). Note that in both cases, the *.nocache.js
will then be overwritten with a script tailored for SuperDevMode, containing the "compile on load" hook; so make sure you clean and recompile before deploying. To get back to "classic" DevMode in GWT 2.7, pass -nosuperDevMode
to the DevMode.