jgrasp handbook

More documents

Recommendations

Info

-v - print the version number. 10 Using Help This help is best viewed in a browser that supports frames, or from jGRASP. If you are using jGRASP, the frame on the left side can be one of: • Contents - links to major subjects. • Index - alphabetized list of links to subject headings. • Search - a search of the help text. Clicking on any link will change the page in the frame on the right side. The search page searches for sections containing all words entered in the "Search" field. 11 Control Structure Diagram (CSD) DRAFT, February 18, 2003, Page 76 The Control Structure Diagram, or CSD, is an algorithmic level diagram intended to improve the comprehensibility of source code by clearly depicting control constructs, control paths, and the overall structure of each program unit. The CSD is an alternative to flow charts and other graphical representations of algorithms. The major goal behind its creation was that it be an intuitive and compact graphical notation that was easy to use manually and relatively straightforward to automate. The CSD is a natural extension to architectural diagrams, such as data flow diagrams, structure charts, module diagrams, and class diagrams. A primary purpose of jGRASP is to provide for automatic generation of the CSD for source code written in Java, C, C++, Ada, and VHDL (support for additional languages is planned). 12 Interface Terminology These terms are used throughout this documentation. Control Panel - the top-level jGRASP window. CSD Window - the source code editing windows. Virtual Desktop or Desktop - the optional desktop window that contains CSD windows. Tab Page or Page - one page of a tabbed window. Menu Accelerator - a function key or control-key combination that performs the same function as a menu item. Swing - also called JFC, the Java gui class library that jGRASP uses. Complier Environment - a group of settings that specify how jGRASP will interface with a particular compiler.
13 Known Bugs DRAFT, February 18, 2003, Page 77 Check the known bugs list at http://www.eng.auburn.edu/grasp/ for an updated list of known bugs, if you are not already there. Check the future plans page for a list of future features. Here is the bug-fix history. Back up your work - this is a Beta release, and has not been thoroughly tested. Save and back up your work frequently. 13.1 Our Known Bugs On Windows NT, a 16 bit process that is run with the %CY flag (console mode) can not be killed until the virtual DOS machine initializes and starts the process (which can take several seconds). If this happens, the process can be killed by closing the console, which will initially be iconified. The "Left Align" CSD setting does not work correctly. The code is not shifted before a save or compile, among other problems. Windows native printing - CSD and text fonts will sometimes not be the same size (note: improved from "usually" to "sometimes"). The CSD font is not as symmetrical and "perfectly rendered" as it is on the screen or with JVM printing. 13.2 Bugs Caused by Java, Swing, or Window Manager Problems These are difficult or impossible to work around. The eventual "fix" for them is (or will be) to get a newer version of the JDK. Many of them apply only to old versions of the JDK. jGRASP may crash (most likely at startup) with "at sun.awt.font.NativeFontWrapper.initializeFont(Native Method)" at the top of the stack dump. When using the integrated Java debugger, jGRASP and the target process will sometimes lock up. This is most likely due to bugs in the JDK, and happens much less frequently with the HotSpot vm and newer versions of the JDK. Note that on a dual processor NT or Win 2000 system and JDK 1.3 or earlier, this may happen frequently, making the integrated debugger effectively unusable. On some JDK versions, the Help window will sometimes not come up, and a stack dump will be generated, the first time help is used. If this happens, help will not work until you shut down jGRASP and restart it. Performance is bad and there is much unnecessary repainting with the Mac Look-And-Feel. The help browser is not suitable for browsing the web. HTML display in Swing is limited and very buggy. The jGRASP help pages are constructed so as to work within the limitations and work around the bugs. On some UNIX/Linux VMs, running jGRASP through the single-instance shell will cause the JVM to crash at shut-down. This seems to be harmless. Windows installation may randomly fail. If it does, try it again. Closing a CSD window will cause an exception on Blackdown and Sun Linux JDK 1.2.2. jGRASP will lock up when closed on these systems (you'll have to kill it manually). We will probably not work around the bug that causes these problems unless it is not fixed in the corresponding 1.3 releases. For now, do not use these systems unless you're willing to put up with the problems, and shut down now and then if you're opening and closing a lot of windows, because memory is leaked each time a window is closed. Font problems on Windows JDK 1.2.2 (not seen on older or newer versions). If you use bold or italic text properties, text in CSD windows will appear normal, bold, or italic at random. Click in the wrong place - when clicking in an unselected CSD window in the virtual desktop, the click position will be offset by the size of the border and menu. This can cause the cursor to move to an unintended location, the wrong text to be selected, the scrollbar to be activated (and probably stuck
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: 9.4 Requirements for the Integrated
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 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?