com.smartgwt.client.docs

Interface RemoteDebugging

public interface RemoteDebugging

Remote Debugging

In Pro and better builds (and also the Eval build), the Smart GWT Developer Console supports debugging remote pages, including those running on mobile devices. With remote debugging, you can use all of the powerful debugging features of the Developer Console - the component hierarchy (Watch tab), client/server requests (RPC tab), logs and log categories - using the large screen and physical keyboard of a desktop machine.

Using Remote Debugging

To enable remote debugging on a page, just add isc_remoteDebug=true to the page URL. For example:

http://localhost:8080/?isc_remoteDebug=true

Note in the URL above, set localhost to the actual hostname or IP address of the machine running the SDK.

You'll also need to be sure that your isomorphicDir has been set up correctly and that messaging is enabled on your server as noted below.

Then direct your desktop browser to the Developer Console in the system/helpers/ subdirectory of your isomorphic dir - typically:

http://localhost:8080/showcase/sc/system/helpers/Log.html

At top right of the page, you will see a "Remote" dropdown that lists the devices and URLs that have registered for remote debugging (by passing the isc_remoteDebug parameter). As you roll over the available remote targets in this dropdown, the target page will glow blue to make it easy to tell which page you will be selecting for debugging - this is particularly handy when you have a lot of devices. Pick the page to debug and just starting using the Developer Console as normal.

If you reload the page on your mobile device, the remote Developer Console automatically re-establishes the connection. And any settings - such as Logging Preferences or Watch tab settings - automatically persist as they normally would.

Licensing

Anyone with a Pro or better license can use the Remote Debugging feature. Under the covers, the Remote Debugging feature actually uses the Real-time Messaging module, which is not a Pro feature. However we've rearranged things so that Pro users can use Real-time Messaging just for Remote Debugging. This does mean that, if you are upgrading your environment to the current release and you don't already have Real-time Messaging, you will need to follow the installation steps normally required for Real-time Messaging before the Remote Debugging feature will work. See the Messaging documentation for details.

See Also:

Debugging