jgrasp handbook

More documents

Recommendations

Info

9.1 Running on Windows DRAFT, February 18, 2003, Page 74 The bin\jgrasp.exe file will start jGRASP in single-instance mode. Running jGRASP a second time will pop up the currently running instance. If you chose to associate file extensions with jGRASP during installation, clicking on an associated file will pop up the file in the currently running instance. A Windows application titled "jGRASP Control Shell", which initially runs minimized, displays the jGRASP output (including stack dumps if there is a crash) and allows the user to kill jGRASP if it locks up. It will first try a "soft kill", and if jGRASP does not exit within a few seconds, a "hard kill" will be issued. "bin\jgrasp.exe" will search for a java.exe to run jGRASP in the following manner: 1) get from "-a" command line parameter if present 2) get from JGRASP_JAVA environment variable if present 3) check the PATH for javac.exe - if found look for java.exe in the same place (avoids finding JRE before JDK) 4) check the PATH for java.exe - if it is found in the system directory, Windows directory, or any subdirectory of those, or if not found, check the registry for the distribution location of a Sun JDK installation. 5) check for the JRE bundled with jGRASP The method used to find java.exe and the java command used to start jGRASP will be displayed in the "jGRASP Windows exec" window. 9.2 Running on Mac OS X Double clicking on the "jGRASP Control Shell" file, or on "jgrasp/bin/macosx/jGRASP Control Shell" if jGRASP was manually installed, will start jGRASP in single-instance mode. Running jGRASP a second time will pop up the currently running instance. Clicking on an associated file will pop up the file in the currently running instance. An application titled "jGRASP Control Shell", which initially runs minimized, displays the jGRASP output (including stack dumps if there is a crash) and the command used to start jGRASP, and allows the user to kill jGRASP if it locks up. It will first try a "soft kill", and if jGRASP does not exit within a few seconds, a "hard kill" will be issued. The first time you run jGRASP it will create a soft link to a startup shell in /usr/bin or $HOME/bin. Then in a terminal shell you can run "jgrasp" and open files in an already running jGRASP with "jgrasp filename". 9.3 Running on Linux, Solaris, and other UNIX Similar single-instance mode executables exist for x86 Linux and SPARC Solaris. These can both be accessed through the bin/jgrasp shell script, which will also pass the location of the jGRASP installation to the correct executable so you don't have to. You can run the executables directly (they are in subdirectories of "bin" with obvious names) if you specify the location of the jGRASP installation through a JGRASP_HOME environment variable or "-j path" at the command line. A window titled "jGRASP exec", which initially runs minimized, allows the user to kill jGRASP if it locks up. It will first try a "soft kill", and if jGRASP does not exit within a few seconds, a "hard kill" will be issued. On other UNIX, bin/jgrasp should run jGRASP directly, without a single-instance shell. See Installing on Other Systems for information on compiling the native parts of jGRASP. For the "java" startup script, if the location of java is not specified through a "-a" command line parameter or JGRASP_JAVA environment variable, then "java" must be on the path.
9.4 Requirements for the Integrated Debugger DRAFT, February 18, 2003, Page 75 For both the Windows and UNIX/Linux startup programs, to use the integrated Java debugger, "java.exe" or "java" must be in the JDK directory structure (in /bin, where tools.jar is in /lib), unless the "-cp" command line argument or JGRASP_CLASSPATH environment variable is used. If "java.exe" is the redirecting startup program on Windows, the registry wil be searched for an appropriate JDK distribution. On Mac OS X, the integrated debugger will be available by default. 9.5 Command Line Arguments for the Single Instance Executables and Shells A filename can be given as the last argument. The leading dash for flags can also be a forward slash on Windows. -h - display a help message. -l line_number - select line_number for the filename argument. -g language - force a language for the filename argument. language can be C, +, J, A, V for C, C++, Java, Ada, and VHDL. -d directory - alternate settings directory. See "Command line arguments for jGRASP itself" below. -a JGRASP_JAVA - specify the java command used to start jGRASP. This can also be set in a JGRASP_JAVA environment variable. If not specified, "java" will be called on UNIX/Linux, and on Windows the PATH, then standard JDK locations will be searched for "java.exe". If a JRE is bundled with jGRASP, that VM will be used if no other is found. -j JGRASP_HOME - specify the root of the jGRASP installation. This can also be set in a JGRASP_HOME environment variable. The "jgrasp" shell script attempts to "locate itself", so this should not be necessary under normal circumstances. This should never be necessary on Windows. -cp JGRASP_CLASSPATH - specify a classpath to be used for jGRASP. This can also be set in a JGRASP_CLASSPATH environment variable. The "jgrasp.jar" file will always be prepended to this path. Under normal circumstances using this argument should not be necessary. -e JGRASP_EXTENSIONS - specify a path for jGRASP elements and user extensions that should persist between versions and may be supplied in optional packages. For now, the classes/system and classes/user subdirectories will be added to the classpath when any system Java compiler environment is used. This is just a convenient way to make library packages available to your Java programs. This can also be set in a JGRASP_EXTENSIONS environment variable. In Windows, a default location is chosen during installation, and will be retreived from the registry. Otherwise, the default is the "extensions" directory in the jGRASP distribution. -Jjvm_arg - pass jvm_arg to the JVM running jGRASP. For example, -J-Xmx90m will make the maximum size of the memory allocation pool for jGRASP 90 megs. 9.6 Command Line Arguments for jGRASP Itself -d directory - use directory as the settings directory instead of USER_HOME/.grasp_settings. directory must be a full path name. By using this, you can run two jGRASP sessions concurrently and they will not interfere with each other, or you can keep different settings for different users on the same system. -h - print a help message.
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: DRAFT, February 18, 2003, Page 73 i
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 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?