This should be in the FAQ.
Using the Debug Modules
Smart GWT LGPL, Pro, Power, and Enterprise come with debug / readable versions of the Smart GWT JS files that may be useful during development.
To enable the use of debug modules, you will need to change the <inherits> lines in the application's GWT module file to reference the debug versions of the Smart GWT modules: Edition Original <inherits> New <inherits>
LGPL <inherits name="com.smartgwt.SmartGwt"/> <inherits name="com.smartgwt.debug.SmartGwtDebug"/>
Pro <inherits name="com.smartgwtpro.SmartGwtPro"/> <inherits name="com.smartgwtpro.debug.SmartGwtProDebug"/>
Power <inherits name="com.smartgwtpower.SmartGwtPower"/> <inherits name="com.smartgwtpower.debug.SmartGwtPowerDebug"/>
Enterprise <inherits name="com.smartgwtee.SmartGwtEE"/> <inherits name="com.smartgwtee.debug.SmartGwtEEDebug"/>
The convention is that the names of debug GWT modules end with "Debug".
If using the NoScript modules, you will need to change the <inherits> lines Edition Original <inherits> New <inherits>
LGPL <inherits name="com.smartgwt.SmartGwtNoScript"/> <inherits name="com.smartgwt.debug.SmartGwtNoScriptDebug"/>
Pro <inherits name="com.smartgwtpro.SmartGwtProNoScript"/> <inherits name="com.smartgwtpro.debug.SmartGwtProNoScriptDebug"/>
Power <inherits name="com.smartgwtpower.SmartGwtPowerNoScript"/> <inherits name="com.smartgwtpower.debug.SmartGwtPowerNoScriptDebug"/>
Enterprise <inherits name="com.smartgwtee.SmartGwtEENoScript"/> <inherits name="com.smartgwtee.debug.SmartGwtEENoScriptDebug"/>
and change the <script> tags in the application's HTML file to the debug modules instead of the normal Smart GWT modules. For example:
<script src="myapp/sc/modules-debug/ISC_Core.js"></script>
<script src="myapp/sc/modules-debug/ISC_Foundation.js"></script>
<script src="myapp/sc/modules-debug/ISC_Containers.js"></script>
<script src="myapp/sc/modules-debug/ISC_Grids.js"></script>
<script src="myapp/sc/modules-debug/ISC_Forms.js"></script>
<script src="myapp/sc/modules-debug/ISC_RichTextEditor.js"></script>
<script src="myapp/sc/modules-debug/ISC_Calendar.js"></script>
<script src="myapp/sc/modules-debug/ISC_DataBinding.js"></script>
<script src="myapp/sc/modules-debug/ISC_Drawing.js"></script>
Alternatively, the <isomorphic:loadISC> and <isomorphic:loadModules> tags support a useDebugModules attribute:
<isomorphic:loadISC skin="Enterprise" useDebugModules="true"/>
Also could one Sample in the showcase be written to have try catch throw logic per gwt and added to the FAQ.
Using the Debug Modules
Smart GWT LGPL, Pro, Power, and Enterprise come with debug / readable versions of the Smart GWT JS files that may be useful during development.
To enable the use of debug modules, you will need to change the <inherits> lines in the application's GWT module file to reference the debug versions of the Smart GWT modules: Edition Original <inherits> New <inherits>
LGPL <inherits name="com.smartgwt.SmartGwt"/> <inherits name="com.smartgwt.debug.SmartGwtDebug"/>
Pro <inherits name="com.smartgwtpro.SmartGwtPro"/> <inherits name="com.smartgwtpro.debug.SmartGwtProDebug"/>
Power <inherits name="com.smartgwtpower.SmartGwtPower"/> <inherits name="com.smartgwtpower.debug.SmartGwtPowerDebug"/>
Enterprise <inherits name="com.smartgwtee.SmartGwtEE"/> <inherits name="com.smartgwtee.debug.SmartGwtEEDebug"/>
The convention is that the names of debug GWT modules end with "Debug".
If using the NoScript modules, you will need to change the <inherits> lines Edition Original <inherits> New <inherits>
LGPL <inherits name="com.smartgwt.SmartGwtNoScript"/> <inherits name="com.smartgwt.debug.SmartGwtNoScriptDebug"/>
Pro <inherits name="com.smartgwtpro.SmartGwtProNoScript"/> <inherits name="com.smartgwtpro.debug.SmartGwtProNoScriptDebug"/>
Power <inherits name="com.smartgwtpower.SmartGwtPowerNoScript"/> <inherits name="com.smartgwtpower.debug.SmartGwtPowerNoScriptDebug"/>
Enterprise <inherits name="com.smartgwtee.SmartGwtEENoScript"/> <inherits name="com.smartgwtee.debug.SmartGwtEENoScriptDebug"/>
and change the <script> tags in the application's HTML file to the debug modules instead of the normal Smart GWT modules. For example:
<script src="myapp/sc/modules-debug/ISC_Core.js"></script>
<script src="myapp/sc/modules-debug/ISC_Foundation.js"></script>
<script src="myapp/sc/modules-debug/ISC_Containers.js"></script>
<script src="myapp/sc/modules-debug/ISC_Grids.js"></script>
<script src="myapp/sc/modules-debug/ISC_Forms.js"></script>
<script src="myapp/sc/modules-debug/ISC_RichTextEditor.js"></script>
<script src="myapp/sc/modules-debug/ISC_Calendar.js"></script>
<script src="myapp/sc/modules-debug/ISC_DataBinding.js"></script>
<script src="myapp/sc/modules-debug/ISC_Drawing.js"></script>
Alternatively, the <isomorphic:loadISC> and <isomorphic:loadModules> tags support a useDebugModules attribute:
<isomorphic:loadISC skin="Enterprise" useDebugModules="true"/>
Also could one Sample in the showcase be written to have try catch throw logic per gwt and added to the FAQ.