jgrasp handbook

More documents

Recommendations

Info

22.9 UML Settings Dialog DRAFT, February 18, 2003, Page 106 Settings for the UML diagram. All of these settings take effect when the diagram is updated. Exclude By Type of Use - external objects (dependencies of objects in the project that are not themselves in the project) can be left out of the diagram. Exclude By Type of Class - JDK classes and interfaces, just the class java.lang.Object, and synthetic classes (those generated by the compiler that don't correspond to any source code class), can be left out of the diagram. New Node Layout - specifies which layout is applied to objects as they are added to the project. 23 Settings • General Info • CSD Window Settings Dialog • Print Settings Dialog 23.1 General Info for Settings There are three levels of CSD window and print settings in jGRASP; global, project, and file. Global settings apply to all files. Project settings apply to all files when the associated project is selected (there is a default project if none has been selected). File settings apply to a specific file. Each global setting can be overridden by a project setting, and each project setting by a file setting. In order to change the setting at any level (override the setting at the next level down), the "Use Default" checkbox must be checked. If it is not checked, the current default setting is displayed, and is not editable. Note that this default setting is not a fixed value, but the value of the corresponding setting at the next level down (which can be changed), or for global settings, the system default value (which could change with a new release of jGRASP - but won't unless absolutely necessary). In most cases, you will want personalized settings to apply to all CSD windows, in which case you should edit the global settings. If you use a variety of compiling environments for different projects, you would most likely edit compiler settings at the project level. Since the settings of the current project apply to all files, a single file can be used in different projects without conflict. File level settings would most commonly be used to override the default language for the file, and to add any file-specific compiler flags. Some settings, such as the CSD colors and font, can only be set at the global level. 23.2 CSD Window Settings Dialog This dialog is used to set most properties not related to printing. The CSD Text and Font pages are available only for global settings. • OK Button - apply the settings and close the dialog. • Apply Button - apply the settings without closing the dialog. • Reset Button - reset the dialog to the currently active settings. • Cancel Button - close the dialog without saving the settings. • Languages Page
• CSD Page • Colors Page • Font Page • Font Size Page • View Page • Sources Page 23.2.1 Languages Page Language specific settings page on the CSD window settings dialog. • Language Combo Box • Environment Page • Flags/Args/Main Page • HTML Page • Extensions Page • Variables 23.2.1.1 Language Combo Box DRAFT, February 18, 2003, Page 107 The "Language" combo box specifies the language for which settings are being viewed or edited, and for file level settings, the language of that file. 23.2.1.2 Environment page "Compiler Environments" specify the compile and run commands (Make, Compile, Compile and Link, Semantic Check, Run, Debug, and for Java, Run Applet and Debug Applet), working directories, error formats, and environment variables. System compiler environments, supplied with jGRASP, can be viewed or copied, but not edited or removed. Local compiler environments, created by the administrator, can be edited or removed only by an administrator. These have names beginning with "local:". User compiler environments, created by the user, can be edited or removed by the user. These have names beginning with "user:". To use a compiler environment, select it in the list, then hit the "Use" button on the environment page (to the right of the list). This will immediately activate the environment, there is not need to click "Apply" or "OK" on the settings dialog. Use - use the selected environment (immediately applied). New - create a new environment using a compiler environment dialog. Copy - copy the selected environment using a compiler environment dialog. It must be saved under a new name. View - for system environments, view the environment using a compiler environment dialog. Edit - for user created environments, edit the selected environment using a compiler environment dialog.
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: 22.5 View Menu DRAFT, February 18,
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

Create successful ePaper yourself

Delete template?

Save as template?