jgrasp handbook

More documents

Recommendations

Info

24.10 New Features in Version 1.4 Beta The Objective-C language was added. Message window contents can now be saved to file or printed. 25 How To 25.1 Change the language for a file: DRAFT, February 18, 2003, Page 118 To change the language of a file, select "Edit" / "Compiler Settings" / "File" on the CSD window menu. Choose the "Language Specific" tab on the settings dialog. Select the desired language from the "Language" combo box. Once a language is selected, jGRASP will remember this setting. Also, the icons in file dialogs and in the browse window will reflect this setting. 25.2 Drag files into jGRASP: Single or multiple files can be dragged onto the virtual desktop, or onto the control panel menu bar, to the right of the menus. The files will be opened in text mode. 25.3 Open a file in binary mode: Using the "File" / "Open File" menu on the control panel or the "File" / "Open" menu on the CSD window menu will bring up a dialog that has "Text" vs. "Binary" radio buttons. All other methods of opening a file will open it in text mode. Opening a binary file in text mode is likely to corrupt it, since all three types of line terminators will be converted to a single type when the file is saved. 25.4 Search for the selected text: F9 and Shift-F9 or Find and Shift-Find will search forward and backward for the selected text in a CSD window. This works across CSD Windows - the selected text does not have to be in the window being searched. 25.5 Make ".h" a default file extension for C or C++ files only: Default extensions can be set at the global or project level. Select "Edit" / "Compiler Settings" / "Global" or "Project" on a CSD window, or "Settings" / "Compiler Settings" / "Global" or "Project" from the control panel. Select "C" or "C++" from the "Language" combo box, whichever one you don't want to be the default. Select the "Extensions" tab, click the default box for extensions off, and add the desired extensions (without "h" or "H"). You can use Ctrl-C and Ctrl-V to copy the old extensions and paste them back after clicking the default box off. 25.6 Change the CSD include path for C or C++ files: To do this, you must create and use a new compiler environment. It usually makes sense to use that environment at the project level.
DRAFT, February 18, 2003, Page 119 Under "Settings" / "Compiler Settings" / "Project", select "C" or "C++" as the language. Select the current compiler environment and hit "Copy". Under the "Parsing" tab, you can specify include directories for CSD generation (one path per line, or with path separators on one line). Next, save the new or edited environment. On the settings dialog, select the new environment and hit "Use". If you have multiple project with different include paths, just create a compiler environment for each. Then, you can use jGRASP projects to easily switch between environments. 25.7 Get C and C++ files with lots of ugly macros or compiler extensions to parse: If you set up the CSD generation environment (include path, predefined macros) exactly like the environment your compile command sees, and set the parse mode to "All Files", and if no structures are partly in a header file and partly in a source file (like an included function header), and if the code is ANSI C, CSD generation should work for your code. Setting all that up can be a pain, and parsing thousands of lines of headers can be slow, so this is usually not an option, unless you just want to generate a CSD once for printing or viewing. If you can edit the code, the easiest thing to do is surround weird code with #ifndef _GRASP_IGNORE and #endif . _GRASP_IGNORE is set in the predefined macros for all compiler environments by default. For example: #ifndef _GRASP_IGNORE BEGIN_MESSAGE_MAP(CPrintApp, CWinApp) ON_COMMAND(ID_SETUP, CWinApp::OnFilePrintSetup) END_MESSAGE_MAP() #endif This is an MFC message map. Without the ifndef, if all headers are parsed and the include path is set correctly, a CSD will be generated for this structure, but the indentation will not be what you expect, because the real structure is not what you expect. For compiler extensions, setting predefined macros in the compiler environment can solve many problems. For example, you might define far to be nothing in an old 16 bit compiler. For your own code, it is a good idea to use macros that look like real code. For example, you should leave a trailing semicolon out of a macro so it will be required in the code.
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 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: 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?