You can also use Show Program Structure to edit your programs and to compile them, but not to run them; however, Xemacs is better at indenting your programs and highlighting Resolve/C++ keywords.
After you have opened a file, you can maximize the editing window. (Of course, you can also maximize the main jGRASP window.) To get the following process to work if your file is not a main program file, you will need to first change each occurrence of "case_select" to "switch" and comment out each line that begins with "#include". Now you can see why you might actually want to go to all this trouble. From the "View" menu of the Edit window, select "Generate CSD". (You may also want to find the "Generate CSD" button on the toolbar.) Note how control structures ("if" and "while" statements together with their bodies) are marked in the left margin. Find one of these statements, and insert a semicolon (';') in the worst possible place, changing, say, "if (large < small)" to "if (large < small);". Generate CSD again to see how this statement is marked now. (By the way, "CSD" means "Control Structure Diagram".) Try removing or inserting a single brace ('{' or '}') and generating CSD to see what happens. (A parse error is noted in "jGRASP Messages"; knowing that a particular file has syntax errors is better than just knowing that a whole program, with all its included files, has them.) Hopefully, these displays will prove helpful to you.
You may want to close your jGRASP edit session without saving the file because jGRASP can disturb some of the indentations that you prefer. Xemacs will continue to respect the indentations that you (and/or we) have already established in the file. Also, you'll probably note that Xemacs is a lot faster at scrolling; jGRASP runs on the Java virtual machine (thus the 'j' in "jGRASP"), and Java's display methods (constituting Swing) are still somewhat slow.
On the other hand, if the indentation and speed issues don't bother you and you wish to use jGRASP to edit and compile your programs, you can. After saving the file, a choice of "Make" from the "Compiler" menu will compile your program. (There is also a "Make" button on the toolbar.) Compilation-time errors will be highlighted in the Edit window. You can click on error messages in the "Compile Messages" window, and the corresponding location in the Edit window will be highlighted. Note that you can remove CSD; this can make editing a bit easier. Also note that "Run" doesn't work because our executables are not named "a.out"; you can run the program from a terminal window (or from xemacs).
First, you need to learn the current actual path to your account's home directory. In a terminal window, type "cd" <Enter> "pwd" <Enter> to display this path. It may look something like "/home/4/leia".
You may or may not be using a personal component catalog, but the compiler is already configured to try and look there. You can also configure jGRASP to find #included files there; here's how. In the control panel's "Settings" menu, choose "Global CSD Window Settings . . .". In the "Languages" tab, make sure the Language chosen is C++. In the "Environment" sub-tab, select "local: Resolve/C++". Click on the "Copy" button. Click on the "Parsing" tab. Replace the tilde character, "~", with the current actual path to your account's home directory (e.g., "/home/4/leia"). Click the "Save" button. Click the "OK" button. With "user: Resolve/C++" selected, click the "Use" button, and notice how the "Current Environment" selection changes. Click the "OK" button. Now jGRASP will also look in your personal component catalog (if you set it up and use it) for #included files.
jGRASP may not find all #included files located in your current project's catalog unless you take the following steps. In the control panel's "Settings" menu, choose "Global CSD Window Settings . . .". In the "Languages" tab, make sure the Language chosen is C++. In the "Environment" sub-tab, select "user: Resolve/C++". Now, here's a difference from the directions given above: click on the "Copy" button. In the top edit window, change "Copy of Resolve/C++" to the name of your current project, say "Lab02". Now click on the "Parsing" tab. Replace the dot character, ".", with the current actual path to your project's directory (e.g., "/home/4/leia/Lab02"). Click the "Save" button. Click the "OK" button. With "user: Lab02" selected, click the "Use" button, and notice how the "Current Environment" selection changes. Click the "OK" button. Now jGRASP should find all #included files located in your current project's catalog.