|Lost and Found|
|11/12/2015 8:26:51 PM|
|10/27/2015 9:41:43 PM|
|10/22/2015 10:26:36 AM|
|7/26/2015 11:01:17 PM|
|7/17/2015 2:45:21 PM|
|List all versions|
Summary: an IBM eclipse plugin for squirrel development
To find out what we can do for you, contact us today. We are available to talk to you via phone or the form in our Contact section. Our team aims to please as we offer a website that is everything that you require at prices that will not break your budget. Our friendly, experienced staff members are on hand and waiting to start creating and designing your online presence today.
SQDev requires the following to install and run:
To enable the squirrel perspective form the main eclipse menu Window/Open Perspective/Others select Squirrel
SQDev has two forms of syntax checking. One is internal to SQDev and attempts to identify common structure errors. The other is by executing an external Squirrel binary and capturing any errors it detects. Using both is recommended, as there are currently some errors only detected in one or the other (but both make your code better!).
SQDev's editor supports automatic syntax checking.
Every time a '.nut file is saved sqdev will invoke sq.exe and compile the file.
To enable (external) automatic syntax checking.
To debug your project.
IP address of the application(disables if localhost)
IP port of the application
if true the debugger ignores the IP Address and always connect to the local machine
if checked the debugger will run the executable specified in Interpreter
the application that has to be debugged
working directory of the application
command line parameters passed to the application at startup
suspends the application on the first squirrel line that gets executed
It is possible to set defaults for you debugger configuration.
Launch you application by pressing the debug button in the toolbar(the one with the green bug icon)
Switch to debug perspective, by pressing the debug button on the perspective toolbar(number 1 in the image)
You can navigate the call stack by selecting a function in the Debug View(number 2 in the image)
To add a breakpoint double click on the gray left border of the editor(see number 4 in the image)
To remove it, double click again on the breakpoint icon
To jump on a breakpoint select the breakpoint in the breakpoint view(see number 5 in the image)
The debugger will automatically jump to the file location if a unhandled exception occurs
Call stack's variables are displayed in the variable view(number 3 in the image)
Left click on the Expression view and select "Add Squirrel Watch Expression"(number 6 in the image)
The expression will be evaluated on a breakpoint or on the next step
After the application has been suspended by a breakpoint or by pressing the pause button in the debug view(number 2 in the image):
Note that you must be in debug perspective
You can terminate the application by pressing the stop button in the debug view(number 2 in the image)
You can suspend the application by pressing the suspend button in the debug view(number 2 in the image)