jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 110 A %FLAGS, %ARGS, %FLAGS2, or %ARGS2 variable must be surrounded by whitespace; the others need not be. To put a percent symbol in a command, use %%. To put a double quote in a quoted string, use %'. Variables that are related to files, paths, and classes may be prepended by MAIN_ or main_ . In that case, the main file will be used in the substitution, or if a main file was not specified, the current file will be used. 23.2.1.7 CSD Page CSD generation settings. Auto Generate CSD - if on, a CSD is generated at load time, after a template is inserted, etc. Show Data Syms. - if on, data and type symbols are shown. Intra-Stmt. Align - if on, parenthesis and assignment symbols are aligned. Indent Braces - if on, curly braced in C, C++, and Java are indented to match the enclosed block. Left Align - (experimental) if on removes the initial three-space indent when the CSD is removed. Turning this setting off and on can change comment alignment. Show Unit Symbols - if on, package/method/function symbols are shown. Show Boxes - if on, boxes are drawn around major code structure headings (packages, methods, functions, etc.). Force Newlines - if on, each statement is forced to a new line. Auto Indent - if on, hitting return will insert whitespace even with the CSD, space and tab indentation of the previous line. Soft Tab - if on, spaces are used instead of tabs, for the tab key, block indent, and auto indent. Font Size - CSD font size in pixels. Tab Size - width of a tab in characters. For variable-width fonts, the with of a "W" is used. 23.2.1.8 Colors Page (global settings only) Colors for lexical types, CSD and background color, and message and I/O window colors. Click the "Use Default" checkbox off and click on the color square to change the color. 23.2.1.9 Font Page (global settings only) Font attributes for lexical types, and font for CSD, message, and I/O windows. Also, the choice of font and whether or not it should be antialiased. Antialiasing generally improves the appearance of text at higher resolutions (or large font sizes), but at low resolutions it may make text harder to read. On some systems, bold and italic fonts will not align with the plain font and/or each other. 23.2.1.10 Font Size Page (global settings only) CSD Font Size - base size of the CSD Window font. Message Font Size - base size of the message and I/O window font. Font Scale - scale factor for all fonts.
23.2.1.11 View Page DRAFT, February 18, 2003, Page 111 These are global defaults for settings that appear on the CSD window view menu. The view menu settings are temporary. 23.2.1.12 Sources Page (Global and Project Settings Only) Allows the search path for jGRASP to be specified. This path will be used for click-to-error in the jGRASP message windows as well as for finding classes shown in the call stack of the integrated debugger for Java. These are used when the message or call stack reference contains a relative path name or a Java class name. They are searched in order. If this is not set, only the working directory for the command that produced the message will be searched. If this is set, and one of the paths is "working directory", the working directory will be searched at that point. In most cases you will need to include "working directory" as one of the paths, probably the first. Paths are entered one per line, and must be absolute. This can be used, for example, to get click-to-error to work for JDK classes in Java stack dumps, if you have the JDK sources. In that case, the root of the JDK source tree (the directory containing the java, javax, etc. directories) should be on one line, and "working directory" on another. If you have Java sources and classes in separate directories, or use a make file in one directory with sources in another, you should specify the source directory or directories and not "working directory". 23.3 Compiler Environment Dialog This dialog allows a compiler environment to be created, edited, or viewed. These environments specify compile and run commands, working directories, and error formats. • Name Field - name of the environment. Not editable for system environments. • Copy Button - copy the environment to the clipboard. • Paste Button - paste the environment from the clipboard. • Export Button - save the environment to file. • Import Button - load the environment from file. • Commands Page • Parse Page • Macros Page • OK Button - save the environment and close the dialog. • Save Button - save the environment without closing the dialog. • Clear Button - clear all the settings. • Reset Button - reset the dialog to the current state of the environment. • Cancel Button - close the dialog without saving the environment. 23.3.1 Commands Page This page specifies settings for Compile, Compile and Link, Check, Run, Debug, and (for Java) Run as Applet and Debug as Applet commands. For each command a working directory and error format can be specified. If a compile command is empty, that command will not appear on the "Compiler" menu of the
Page 1 and 2:
The Table of Contents Index Handboo
Page 3 and 4:
DRAFT, February 18, 2003, Page ii 4
Page 5 and 6:
DRAFT, February 18, 2003, Page iv 1
Page 7 and 8:
DRAFT, February 18, 2003, Page vi 2
Page 9 and 10:
Overview of jGRASP DRAFT, February
Page 11 and 12:
DRAFT, February 18, 2003, Page 3 sp
Page 13 and 14:
DRAFT, February 18, 2003, Page 5 Pr
Page 15 and 16:
DRAFT, February 18, 2003, Page 7 Co
Page 17 and 18:
11 Control Structure Diagram (CSD)
Page 19 and 20:
1 Installing jGRASP DRAFT, February
Page 21 and 22:
2.1 Creating a New File DRAFT, Febr
Page 23 and 24:
In the upper right corner of the CS
Page 25 and 26:
2.2 Saving a File DRAFT, February 1
Page 27 and 28:
2.4 Loading a File DRAFT, February
Page 29 and 30:
DRAFT, February 18, 2003, Page 21 4
Page 31 and 32:
DRAFT, February 18, 2003, Page 23 O
Page 33 and 34:
2.7 Line Numbers DRAFT, February 18
Page 35 and 36:
DRAFT, February 18, 2003, Page 27 T
Page 37 and 38:
2.9 Running a Program DRAFT, Februa
Page 39 and 40:
3 The Control Structure Diagram (CS
Page 41 and 42:
DRAFT, February 18, 2003, Page 33 n
Page 43 and 44:
Selection (cont’d) switch (when b
Page 45 and 46:
3.4 CSD Templates DRAFT, February 1
Page 47 and 48:
3.6 Reading Source Code with the CS
Page 49 and 50:
Consider the fragment at right with
Page 51 and 52:
4 Projects DRAFT, February 18, 2003
Page 53 and 54:
4.2 Adding files to the Project DRA
Page 55 and 56:
4.4 Generating Documentation for th
Page 57 and 58:
4.5 Jar file Creation and Extractio
Page 59 and 60:
DRAFT, February 18, 2003, Page 51 I
Page 61 and 62:
DRAFT, February 18, 2003, Page 53 j
Page 63 and 64:
DRAFT, February 18, 2003, Page 55 M
Page 65 and 66:
DRAFT, February 18, 2003, Page 57 a
Page 67 and 68: 5.5 Displaying Dependencies Between
Page 69 and 70: 5.8 Saving the UML Layout DRAFT, Fe
Page 71 and 72: DRAFT, February 18, 2003, Page 63 b
Page 73 and 74: DRAFT, February 18, 2003, Page 65 t
Page 75 and 76: DRAFT, February 18, 2003, Page 67 V
Page 77 and 78: DRAFT, February 18, 2003, Page 69 T
Page 79 and 80: Part 2 - Reference DRAFT, February
Page 81 and 82: DRAFT, February 18, 2003, Page 73 i
Page 83 and 84: 9.4 Requirements for the Integrated
Page 85 and 86: 13 Known Bugs DRAFT, February 18, 2
Page 87 and 88: Unicode support - this will require
Page 89 and 90: Section 3. Disclaimer of Warranty D
Page 91 and 92: * . * DRAFT, February 18, 2003, Pag
Page 93 and 94: DRAFT, February 18, 2003, Page 85 A
Page 95 and 96: DRAFT, February 18, 2003, Page 87 S
Page 97 and 98: 17.13 Projects DRAFT, February 18,
Page 99 and 100: 17.18 Jar/Zip Extractor Dialog DRAF
Page 101 and 102: DRAFT, February 18, 2003, Page 93 e
Page 103 and 104: 18.8 Find Dialog / Page DRAFT, Febr
Page 105 and 106: DRAFT, February 18, 2003, Page 97 s
Page 107 and 108: \xnn hexadecimal representation of
Page 109 and 110: DRAFT, February 18, 2003, Page 101
Page 113 and 114: 22.5 View Menu DRAFT, February 18,
Page 115 and 116: • CSD Page • Colors Page • Fo
Page 117: DRAFT, February 18, 2003, Page 109
Page 123 and 124: 23.4.3 UML Print Settings Page Marg
Page 125 and 126: File syncing may cause jGRASP to lo
Page 129 and 130: flags..............................
show all

jgrasp handbook

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?