854727e281ceb189c615558ed9cd682746191882
wiki/super-dev-mode.md
| ... | ... | @@ -16,13 +16,13 @@ When opening an entry point page you will see a popup while the Java code is com |
| 16 | 16 | When changing some frontend code the compile will be much faster on refresh, as Super Dev Mode incrementally compiles only what changed. |
| 17 | 17 | |
| 18 | 18 | You can add "GWT.debugger();" statements to your Java code. |
| 19 | -his will force the JavaScript debugger to stop at this statement. |
|
| 19 | +This will force the JavaScript debugger to stop at this statement. |
|
| 20 | 20 | So you don't have to manually open the file in the dev tools and set a break point. |
| 21 | 21 | |
| 22 | 22 | ## Using Eclipse debugger for GWT SuperDevMode |
| 23 | 23 | |
| 24 | 24 | Debugging Java Code in the browser is very inconvenient (e.g. you have to manually open the files you already opened in Eclipse). |
| 25 | -Using Using Eclipse debugger for GWT SuperDevMode [[SDBG|http://sdbg.github.io/]] you can use Eclipse to debug SDM code running in Chrome. |
|
| 25 | +Using Using Eclipse debugger for GWT SuperDevMode [[SDBG|http://sdbg.github.io/]] you can use Eclipse to debug SDM code running in Chrome. We have created an update site that does daily checks for new master commits on the Github project. So, for the couraged among you, use http://p2.sapsailing.com/p2/sdbg as your update site. All others will probably want to use http://sdbg.github.io/p2. |
|
| 26 | 26 | |
| 27 | 27 | ### Starting a SDM debug session in Eclipse |
| 28 | 28 |