This section covers some of the common methods used for debugging JavaScript and GI code.
Alert messages
Alert messages can be used as a powerful debugging tool. This section covers how to use them and some of the pros and cons of using alert messages.
Log messages
Log messages set in the GI code are a very powerful way to monitor the flow of an application and track status and values. This section covers how to setup log messages and monitor the message log and some of the pros and cons of using alert logs.
Application Monitor
The Application Monitor is a special type of log message monitor. It creates a separate window for a application that is running in a browser. This section covers how to setup the Application Monitor and some of the pros and cons of using alert logs.
MyEclipse AJAX Debugger
MyEclipse is a Java / JavaScript IDE that provides a very powerful JavaScript debugger that allows for complete debugging of JavaScript code. It is a paid subscription product (very reasonably priced), but has a trial version available to determine if you want to utilize the application. This section covers the basics of using the AJAX debugger on a GI application.
FireBug Debugger
FireBug is a FireFox plugin for debugging JavaScript applications. This section covers the basics of using FireBug to debug a GI application.
Stop GI Error capture
A note in here if anyone else is trying to debug the infamous "Uncaught Exception" that has ZERO decent information. If you're getting the uncaught exception, try turning off the "trapping" that GI is doing by executing the following: jsx3.lang.NativeError.stopErrorCapture(); This greatly improves the amount of information available in FireBug, etc.
Make your own build for debugging purpose
Lastly, I was only able to debug my app after doing a source build. The guide here GI Build Tools - Introduction and Set Up was very very useful.
