jgrasp handbook

More documents

Recommendations

Info

DRAFT, February 18, 2003, Page 90 Max. Results Per File - specifies the maximum number of matches that will be reported for each selected file. 17.15 Help Us Test CSD Generation You can help us test the jGRASP CSD generator by running the autotest on groups of your source files. The autotest dialog is on the "Tools" menu of the control panel. See autotest dialog for a description of its use. 17.16 Generate Documentation Dialog Target Directory - the directory in which the "javadoc" documentation will be generated. Using a projectrelative path will allow this setting to be valid if the entire project is moved (even to a different operating system). Additional Doc. Command Flags - additional flags to the "javadoc" command. This is useful for linking to Java API docs on the local system or the web. For example: local file: -link “file:///C:/j2sdk1.4.0/docs/api” Sun website: -link "http://java.sun.com/j2se/1.4/docs/api" Generate - generates documentation using the current project-level "Document" command for Java. 17.17 Jar Creation Dialog This dialog allows the user to create a jar file for the files in the current project. • First Page • Second Page 17.17.1 First Page Project Files - selects the type of files from the current project to include in the jar file. The files are shown in the window below. Additional (non-project) Files - the "Add" button allows the user to add arbitrary files to the jar file. Using a relative path (the default) means that the correct files will be used if the entire project is moved to another directory. The "Delete" button will delete selected files from the window. 17.17.2 Second Page Jar File - the name of the jar file to be created. Uses a project-relative path by default. Jar Root Directory - the root of the jar directory. Filenames in the jar file will be relative to this directory. This is initially set to the first common ancestor of all the files and package roots in the jar, and by default it is project-relative. Any ancestor directory of this default will work. To reset the default value, delete the current value, hit "Back", then hit "Next". Main Class - the name of the main class in the jar file. If specified, running "java -jar" on (or possibly clicking on) the generated jar file will run that class. The combo-box gives a choice of classes with entry (main) methods.
17.18 Jar/Zip Extractor Dialog DRAFT, February 18, 2003, Page 91 This dialog allows the user to extract files from a jar or zip archive. Once an archive is opened, all files or selected files can be extracted to a directory using "Extract Files". Files can also be dragged from the window and dropped elsewhere. 18 CSD Window "CSD window" is the name given to source code editing windows in jGRASP. The CSD Window supports dropping of text (drag and drop). The title bar displays the language, file name, and modified state (it shows "(edited)" if modified). Note that CSD generation is not considered a modification, because even though it may change the text it will not change the code structure. The CSD window may be split horizontally or vertically for a dual view of the text. This can be done by using the "Split View" submenu of the "View" menu. The split state of the window is remembered when a file is closed and reopened. A tool bar is provided for commonly used functions. The default position of this bar is above the text, but it may be floated or moved to the bottom (or the sides, which is not very useful). It may also be removed using the "View" menu. A message bar displays the insert/overstrike mode state, and the current cursor line and column, character code at the cursor, and topmost visible line. If the view is split, the topmost visible line of both views is displayed. The default position of this bar is below the text, but it may be floated or moved to the top (or the sides, which is not very useful). It may also be removed using the "View" menu. CSD windows maintain an internal "primary selection" as is found on XWindow systems. Selecting text in one window will unselect it in another. The F9 key will search for the current selection, and Shift-F9 will search backward for the current selection, in a CSD Window. The Find key and Shift-Find will do the same thing (if your keyboard has a Find key). • File Menu • Edit Menu • View Menu • Templates Menu • Compiler Menu • Run Menu • CPG Menu • Mouse Button Actions • Folding • Marks • Bookmarks • Breakpoints
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: 17.13 Projects DRAFT, February 18,
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 119 and 120: 23.2.1.11 View Page DRAFT, February
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?