jgrasp handbook

More documents

Recommendations

Info

8 Installing jGRASP 8.1 Important Notes DRAFT, February 18, 2003, Page 72 This is jGRASP version 1.5.0. Check http://www.eng.auburn.edu/grasp for the latest version of jGRASP. jGRASP is written in Java. Java 1.2 or higher must be installed on your machine in order to run jGRASP. The full JDK 1.3 or higher (not the JRE) is required in order to use the integrated Java debugger. jGRASP does not include any compilers. The JRE bundled version and all other versions of jGRASP do not include a Java compiler. In order to compile programs you must have a compiler installed. 8.2 Which JVM to Use If you have downloaded a JRE bundled version of jGRASP, this is not a concern. Otherwise, Sun JDK 1.4 is suggested. When jGRASP starts, you may get a message telling you that jGRASP has known problems or minor problems, or has not been tested on your system. To use the integrated Java debugger, JDK 1.3 or higher is needed (and you should develop under 1.3 or higher also). 8.3 Installing from the Self-Extracting exe on Windows Before running the installation file, you should close all applications. If a file from a previous installation is in use, the installer may give you a "Can not copy file" or "File in use" message. This would happen, for example, if you had the readme.txt file open in MS Word. If this happens, iconify the installer, close the file or the application that is using the file, pop the installer back up, and click "Retry" on the error dialog. If the installer will not run, you will have to install manually. On Windows NT, if you have Administrator access, the start menu items and desktop shortcut will be installed for all users. 8.4 Manual Installation on Windows Unzip the distribution file in the directory where you wish to install jGRASP. This will create a jgrasp directory containing all the files. Add a shortcut or start menu item to jgrasp\bin\jgrasp.exe. 8.5 Installing on Mac OS X Unzip and untar the .tar.gz file, if this did not happen automatically when you downloaded. You can use Stuffit Expander or from a terminal, "gunzip jgrasp*.tar.gz" then "tar xf jgrasp*.tar". Then double click on the .pkg file. A root password is required to install. The first time you run jGRASP, the CSD font will be installed on your system, and a soft link to the jgrasp startup script (for command line execution) will be created in /usr/bin or your $HOME/bin directory. 8.6 Manual installation on Mac OS X Unzip the distribution file in the directory where you wish to install jGRASP (you can use Stuffit Expander to do this). This will create a jgrasp directory containing all the files. You can then click on "jgrasp/bin/macosx/jGRASP Control Shell" to run jGRASP. The first time you run, the CSD font will be
DRAFT, February 18, 2003, Page 73 installed on your system, and a soft link to the jgrasp startup script (for command line execution) will be created in /usr/bin or your $HOME/bin directory. If you want to create a "normal" OS X application, copy the "jgrasp/bin/macosx/jGRASP Control Shell.app" directory, then move the original "jgrasp" directory into the new "jGRASP Control Shell.app/Contents/Resources" directory. 8.7 Installing on x86 Linux, SPARC Solaris Unzip the distribution file in the directory where you wish to install jGRASP. This will create a jgrasp directory containing all the files. You may want to add the "bin" subdirectory of this directory to your execution path or create a soft link to .../jgrasp/bin/jgrasp from a directory on the executable path. 8.8 Installing on Other Systems Unzip the distribution file in the directory where you wish to install jGRASP. All the functions of jGRASP will work except for the compile and run functions. If you are on a Unix system other than Linux or Solaris, you can build a "wedge" program in order to use the compile and run functions of jGRASP (C compiler and knowledge of how to use it is necessary). The source can be found at jgrasp/src/linux_run.c . The executable must be jgrasp/jbin/sys_run . The source for a client-server shell can be found at jgrasp/src/linux_exec.c . That executable can have any name; it is only used externally. For the best chance of success, compile with default optimization. Please contact us if you succeed in doing this. We can incorporate your executables in a future release of jGRASP. If you are on a system other than Windows or a UNIX variant and have a good knowledge of system programming on your system, you can build a wedge based on the UNIX wedge sources found in jgrasp/src . The executable must be jgrasp/jbin/sys_run. 8.9 Network Administration jGRASP supports common settings for all users on a network. The common settings directory can be specified at installation time if using the self-extracting exe on Windows. Otherwise, in the "data" directory of the installation, edit the file called "admin". Specify the directory to be used for administrator settings in this file. This should be the only contents of the file, and not be followed by a line feed or carriage return. Use a full path to specify the directory. This directory must be accessible and readable by all users, and writable only for administrators. You should select a location outside the jGRASP distribution, so that you can continue to use the settings after upgrading. When an administrator (anyone with write access in the common settings directory) runs jGRASP, menu items that allow you to change administrator settings will appear on the control panel settings menu. Also, when copying or creating compiler environments, you will have the choice of creating them for all users or just the current user. 9 Running jGRASP jGRASP requires a Java 1.2 or better virtual machine and system classes to run. You can get the latest JDK from Sun Microsystems. You will probably need about 48 Megs of memory to run jGRASP, but this depends on the virtual machine, jit compiler, and which other applications you run concurrently.
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: Part 2 - Reference DRAFT, February
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 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?