From 51f93a538fb7ceeb82c7bd82cdb1910bccddbda2 Mon Sep 17 00:00:00 2001
From: Steffen Schaefer <steffen.schaefer@oio.de>
Date: Wed, 4 Feb 2015 09:48:46 +0100
Subject: [PATCH] Adjusted SDM documentation and added launch config for Chrome
 debugging

---
 .../Debug SailingGWT SDM on Chrome.launch        | 16 ++++++++++++++++
 wiki/super-dev-mode.md                           | 14 ++++++--------
 2 files changed, 22 insertions(+), 8 deletions(-)
 create mode 100644 java/com.sap.sailing.gwt.ui/Debug SailingGWT SDM on Chrome.launch

diff --git a/java/com.sap.sailing.gwt.ui/Debug SailingGWT SDM on Chrome.launch b/java/com.sap.sailing.gwt.ui/Debug SailingGWT SDM on Chrome.launch
new file mode 100644
index 00000000000..928d304587c
--- /dev/null
+++ b/java/com.sap.sailing.gwt.ui/Debug SailingGWT SDM on Chrome.launch	
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<launchConfiguration type="com.github.sdbg.debug.core.chromeLaunchConfig">
+<stringAttribute key="applicationArguments" value=""/>
+<stringAttribute key="applicationName" value=""/>
+<booleanAttribute key="launchFile" value="false"/>
+<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
+<listEntry value="/com.sap.sailing.gwt.ui"/>
+</listAttribute>
+<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
+<listEntry value="4"/>
+</listAttribute>
+<stringAttribute key="projectName" value="com.sap.sailing.gwt.ui"/>
+<booleanAttribute key="showLaunchOutput" value="false"/>
+<stringAttribute key="url" value="http://127.0.0.1:8888/gwt/Home.html"/>
+<stringAttribute key="urlQueryParams" value=""/>
+</launchConfiguration>
diff --git a/wiki/super-dev-mode.md b/wiki/super-dev-mode.md
index 5edd38fdccc..f52edefca41 100644
--- a/wiki/super-dev-mode.md
+++ b/wiki/super-dev-mode.md
@@ -19,6 +19,8 @@ You can add "GWT.debugger();" statements to your Java code.
 his will force the JavaScript debugger to stop at this statement.
 So you don't have to manually open the file in the dev tools and set a break point.
 
+In addition, there's a composite launch configuration "SailingGWT All SDM.launch" that will start SDM for the SailingGWT modules as well as the Security UI modules.
+
 ## Using Eclipse debugger for GWT SuperDevMode
 
 Debugging Java Code in the browser is very inconvenient (e.g. you have to manually open the files you already opened in Eclipse).
@@ -29,16 +31,12 @@ Using Using Eclipse debugger for GWT SuperDevMode [[SDBG|http://sdbg.github.io/]
 To start SDM debugging in Eclipse, do the following:
 
 * Start the backend as you would always do.
-* Start GWT Super Dev Mode by launching "SailingGWT sdm.launch".
+* Start GWT Super Dev Mode by launching "SailingGWT sdm.launch" or "SailingGWT All SDM.launch".
 * Do not Click on the URLs provided in "Development view"!
-* Copy one of the URLs instead
-* Go to Run -> Run Configurations ...
-* Create a new configuration of type "Launch Chrome"
-* Paste the URL and select the UI project you launched SDM for
-* Save and run => A new instance of Chrome is started and you will see a debug session running in Eclipse
+* Run "Debug SailingGWT SDM on Chrome.launch"
+* A new instance of Chrome is started and you will see a debug session running in Eclipse
 * Your Eclipse break points will now work in the running debug session.
-
-The created and save run configuration can be used for subsequent launches.
+* You are free to change the URL or navigate to other pages in the automatically openend browser window (debugging will go on)
 
 ### Noteworthy information & Troubleshooting