Changes between Version 18 and Version 19 of JavascriptDebugging

Timestamp:

Mar 3, 2013, 5:57:11 PM (11 years ago)

Author:

Yves

Comment:

--

JavascriptDebugging

@@ -20 +20 @@
 A yellow warning message is displayed in the game if the debugger is enabled.
 
-[[Image(enabled_warning.jpg)]]
+[[Image(enabled_warning.jpg, 25%)]]
 
 == Using the debugger ==
@@ -26 +26 @@
 First start the game and make sure that the debugger is enabled. Then open 0ad/source/tools/jsdebugger/index.html in a web browser.
 
-[[Image(after_startup.gif)]]
+[[Image(after_startup.gif, 25%)]]
 
 The debugger will load a list of script files loaded by the engine (1). Because no file is loaded at the moment, the file panel in the middle (2) will be empty. On the right side (3) you see all (or most) commands that are available.  On the bottom left side (4) there's a list of currently running script interface instances. They can all be different threads, but that's not necessarily so. Because the scripts are running and we haven't triggered a breakpoint yet, the callstack window (5) is empty. The values window (6) contains the three root nodes for values you can watch (locals, this, global) but they are empty at the moment.
@@ -41 +41 @@
 The file panel displays a file with line numbers, syntax highlighting and even some basic syntax validations. However, it only displays the file and you can't edit it there directly. You see breakpoints and can toggle breakpoints by klicking left beside the line numbers. The yellow line shows you at which line the execution is currently halted.
 
-[[Image(debugging_alpine_lakes.gif)]]
+[[Image(debugging_alpine_lakes.gif, 25%)]]