The following is a list of issues debugging a SmartGWT application. The environment is:
11/26/2015
Instead of using the SmartClient debug mode, as detailed in #2, it’s better to configure as detailed in #1 and adding the following to the html page:
Presently, the only suitable environment for debugging a GWT application is in Internet Explorer (:rolleyes:), since code can be reloaded without reloading all code, and the page itself. Plus, you can still debug directly in Eclipse, as opposed to the ridiculous browser development environments; this is only debugging in GWT classic mode. Super dev mode is completely useless.
Unfortunately, this means you won’t have any of the amazing development plug-in’s available for Firefox, particularly Selenium IDE.
SmartGWT LGPL 5.0p
GWT 2.7
Eclipse Luna 32-bit, debug in superdev mode, internal server (Jetty 8.1)
Chrome 46.0.2490.86 m
Firefox 42.0
Internet Explorer 11.0.9600.18097 (update version 11.0.25)
Any change in any environment module will render this information useless, seeing how often things change in this very unstable technology.GWT 2.7
Eclipse Luna 32-bit, debug in superdev mode, internal server (Jetty 8.1)
Chrome 46.0.2490.86 m
Firefox 42.0
Internet Explorer 11.0.9600.18097 (update version 11.0.25)
11/26/2015
- Configuration 1:
- gwt.xml inherits:
<inherits name="com.smartgwt.SmartGwtNoScript"/>
<inherits name="com.smartgwt.tools.SmartGwtTools"/>
<inherits name="com.smartclient.theme.enterprise.Enterprise"/>
<inherits name="com.smartclient.theme.enterprise.EnterpriseResources"/> - html script includes:
<script src='rexweb/sc/modules/ISC_Core.js'></script>
<script src='rexweb/sc/modules/ISC_Foundation.js'></script>
<script src='rexweb/sc/modules/ISC_Containers.js'></script>
<script src='rexweb/sc/modules/ISC_Grids.js'></script>
<script src='rexweb/sc/modules/ISC_Forms.js'></script>
<script src='rexweb/sc/modules/ISC_RichTextEditor.js'></script>
<script src='rexweb/sc/modules/ISC_Calendar.js'></script>
<script src='rexweb/sc/modules/ISC_Drawing.js'></script> - results:
- Chrome: page loads without errors in console, all scripts load, app fails to start
- Firefox: same as Chrome
- IE: reference to __fireReplyCallback fails because RPCManager is undefined. Source map resolves this to SmartGwtEntryPoint.java, line 34, init(), probably the first reference in the JS.
- gwt.xml inherits:
- Configuration 2 (ref. https://www.smartclient.com/smartgwt...ugModules.html):
- gwt.xml inherits:
<inherits name="com.smartgwt.debug.SmartGwtNoScriptDebug"/>
<inherits name="com.smartgwt.tools.SmartGwtTools"/>
<inherits name="com.smartclient.theme.enterprise.Enterprise"/>
<inherits name="com.smartclient.theme.enterprise.EnterpriseResources"/> - html script includes:
<script src='rexweb/sc/modules-debug/ISC_Core.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Foundation.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Containers.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Grids.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Forms.js'></script>
<script src='rexweb/sc/modules-debug /ISC_RichTextEditor.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Calendar.js'></script>
<script src='rexweb/sc/modules-debug /ISC_Drawing.js'></script> - results, all three browsers:
- 200 additional scripts are downloaded
- 11 images failed to download, all referenced from /sc/skins/standard/images, even though the theme is “enterprise”. The Enterprise folder does exist under /sc/skins, however. Some variable isn’t being set correctly under debug mode.
Rectified by adding to html:
<script type="text/javascript" language="javascript" src="rexweb/sc/skins/Enterprise/load_skin.js"></script>
- gwt.xml inherits:
Instead of using the SmartClient debug mode, as detailed in #2, it’s better to configure as detailed in #1 and adding the following to the html page:
<script src='rexweb/sc/client/application/RPCManager.js'></script>
If RPCManager isn’t moved into your module’s sc folder, extract it from the SmartGWT JAR and add it yourself, but best to put it under a folder other than the module folder, which will be altered by future compiles.Presently, the only suitable environment for debugging a GWT application is in Internet Explorer (:rolleyes:), since code can be reloaded without reloading all code, and the page itself. Plus, you can still debug directly in Eclipse, as opposed to the ridiculous browser development environments; this is only debugging in GWT classic mode. Super dev mode is completely useless.
Unfortunately, this means you won’t have any of the amazing development plug-in’s available for Firefox, particularly Selenium IDE.
Comment