FILE CKMKER.BWR MACINTOSH KERMIT "BEWARE" FILE February 1992 Version: Mac Kermit 0.99(102) / C-Kermit 5A(183) Last update: Sun Aug 23 14:37:35 1992 Frank da Cruz, Columbia University e-mail: fdc@watsun.cc.columbia.edu (Internet), FDCCU@CUVMA (BITNET/EARN) This document applies to the pre-pre-pre-pre-release of Mac Kermit 1.0. This is a work in progress. Many features remain to be filled in, refined, fixed, or even designed. Several volunteer programmers in scattered locations around the world are working on the new release as their schedules permit; additional skilled Macintosh C-programmer volunteer help would be most welcome! This is the first Mac Kermit version to have been built with the C-Kermit 5A file transfer protocol modules, so it incorporates all the latest protocol features of C-Kermit, including sliding windows and character set translation. As yet, there is no documentation for Mac Kermit 1.0 except this file and the C-Kermit documentation, which describes the commands you can give at the Mac-Kermit prompt in Mac Kermit's command window. This document contains information for both users and for implementors. Eventually everything will be sorted out and we'll have good user documentation. The Mac Kermit program is distributed in printable ASCII BinHex 4.0 form. Convert back into a runnable application using BinHex Version 4. Send comments, bug reports, etc, to me at the e-mail address above. SOURCE CODE Macintosh Kermit is written in C. The modules whose names start with "ckm" are specific to the Macintosh. These can be C source code (.c), header files for #include (.h), or resource files (.r). The makefile is ckmker.mak, which you should rename to kermit.make for use in MPW. The modules whose names start with "ckc" or "cku" are shared with other C-Kermit implementations: UNIX, VMS, OS/2, Amiga, OS-9, etc. The new version of Mac Kermit can be built using only MPW C 3.2 Final (NOT 3.0 or 3.1, and not any Beta version of 3.2) on the Macintosh. MPW 3.2 is required because Mac Kermit needs more than 32K of uninitialized global data space, and the limit in MPW 3.1 and earlier is 32K. It is probably not possible to reduce the size of the uninitialized global data area by more than about 3-4 more K (by converting array declarations to pointers and then mallocing the space at runtime), so we can't get below 32K, so therefore we must use the new MPW C 3.2 "32-bit everything" model ("-model far"). NOTE TO DEVELOPERS: References to the Pattern data type have to be changed to fit MPW 3.2's new redefinition (which, they say, was done to eliminate crashes on 68000-based CPUs). See quickdraw.h and Appendix J of the 3.2 Release Notes. When this is done, remove "-d dangerousPattern" from the C command line in the makefile. Many of the source files contain 8-bit characters. Make sure you have transferred them to your Mac correctly. Use text mode, but make sure character translation is turned off. Also, many of the ckm*.* files have lines longer than 80, which can prevent them from being transferred via certain kinds of e-mail (such as BITNET). NOTE TO DEVELOPERS: These source files need to be edited to ensure that all lines are less than 80 characters wide (after tab expansion), and 8-bit characters are all converted to "\ooo" ASCII octal notation (I tried using the \266 (delta) line continuation character in the kermit.make file to break up long lines, but it didn't seem to work.) The final release source code should contain only 7-bit ASCII characters, and no lines longer than 80. NEW FEATURES Multiple screen windows: for terminal emulation, command processing, text editing, server response, etc, managed in the normal Macintosh way, as well as with a new "Window" menu to select any Mac Kermit window explicitly. Cutting and pasting works among most of the windows, including double click to select a word, triple click to select a line. Material can be copied from the terminal window to other Mac Kermit windows, or to other applications. Pasting into the terminal window sends text to the remote computer. The terminal session can also be logged directly to a file. The Command window runs the C-Kermit command parser, just like on UNIX or VMS, and similar to MS-DOS Kermit. This gives you access to features that are not in the mouse/menu interface, most importantly the DIAL command and the script programming language, and allows the same script programs to be used by C-Kermit on UNIX, VMS, the Macintosh, the Amiga, OS/2, etc, and by MS-DOS Kermit (with proper precautions about portability). Text command files can be used as Mac Kermit startup files ("init files", like for C-Kermit or MS-DOS Kermit). Filenames can be referred to by their full path names in the SEND command, etc, for example "send diskname:foldername:filename", or by relative pathnames, e.g. "send ::foldername:filename". Window sizing (vertically only) using the size box, including the terminal emulation window. Scrollback in most windows, including the terminal window. Font selection in the terminal window. More efficient file transfer via sliding window packet protocol and longer packets. The window size may be as big as 31 (the theoretical maximum) and packets can be up to about 5000 characters long. File transfer character set translation (available only via the Command window). The commands are SET FILE CHARACTER-SET, SET TRANSFER CHARACTER-SET, and SET LANGUAGE. Locking shift packet protocol for efficient transfer of 8-bit data over 7-bit communication channels. Dynamic packet size adjustment to adapt to communication line quality. File transfer thermometer. Redesigned menus (but nowhere near final). Many bugs fixed. MISSING OR DESIRABLE FEATURES No Tektronix or ReGis graphics emulation (volunteers needed!). Missing VT320 features, including 132-column mode, and VT220, VT102, VT100, and VT52 submodes. No 3270 terminal emulation (volunteers?). No color support, e.g. ANSI color directives during terminal emulation. No "Print selection" and "Print screen" options selectable by mouse clicks (work is in progress). Presently, printing can only be done in the terminal window via escape sequences sent from the host. No SET KEY command -- key settings are accessible only through the menu interface. Maybe in a future edit. No Comm Toolbox support, e.g. for making connections thru MacTCP, LAT. No multiple sessions -- e.g. modem port in one window, printer port in another. The hard part here is not putting up another window, but associating all the varied and many communication, protocol, and terminal emulation parameters separately for each window (this is not just a programming problem, but also a user interface design issue). Internationalization of the user interface (this will be done before the final release). GENERAL BUGS File transfer display window is missing information (file name, as-name, size, thermometer) when sending files. Severe problems when running on a Mac (only under System 7?) that has SuitCase, Adobe Type Manager, or Mac Layers Keyboard loaded, ranging from messed-up screens (bad font spacing) to Kermit or Mac bombs. Hopefully this will clear up when the new Macintosh Extended Latin font is finished and integrated with Mac Kermit. Kermit's ID (signature) is KR09, which hasn't changed in years, so if you have a lot of different Kermit versions on your disk, clicking on a Kermit startup file will start a random version of Kermit, not necessarily the one you want. The ID should be updated to KR10 (files ckmker.mak = kermit.make, ckmdef.h, ckmker.r, ckmkr2.r, ckmsav.c). Starting one copy of Mac Kermit while another one is active (e.g. under MultiFinder) results in lots of errors for both Kermits. Kermit always initializes the modem port when it starts up (even if the startup file says to use the printer port), and this hangs up any other version of Kermit (and who knows what other programs) that might be using the modem port. Kermit should (a) not touch the communication device until it needs to do i/o (this would give the selection of alternate communication devices the opportunity to take effect first), and (b) should (if this is possible on the Mac) detect whether the communication device is in use already, and if so, give an appropriate error message. No support for CD and DSR modem signals -- this is a limitation of the Mac serial port hardware. Many bugs (malfunctions, hanging or bombing of the system, even the occasional destruction of files, etc) were reported for earlier releases (and non-releases) of Mac Kermit under System 7. Let's wipe the slate clean and see how this version fares. MENUS, WINDOWS, AND DIALOG BOXES The menus are not complete, and will be rearranged. They must fit on a small screen, even after translation into languages like Swedish, where the words are longer than English. See APPENDIX at the end of this file. Some of the dialog boxes violate the Human Interface Guidelines (HIG) from Apple, and need redesigning also. The edit menu Undo command doesn't work, and the Edit menu lacks a Select All command. In the file-send dialog box, an attempt to edit the "Send As" name results in deselecting the file and dimming the Send button. Typing a letter into a file dialog box tends not to scroll the file list. If you click on Load Settings in the File menu while the command screen is foremost, the terminal screen will come to the foreground. However, any characters you type still go into the command window. Load Settings should either leave you in whatever window you were in before, or else fully select the terminal window. Various confusion with cutting and pasting between windows, especially after a window that has been cut from is closed. Pasting text into the bottom of a text window does not cause the scroll bar to update; any text below the visible region cannot be scrolled to or otherwise viewed. (Workaround: save and reopen the file.) All blank lines are removed from text files upon opening. There is no way to select file and transfer character sets in the menus, or language rules. Furthermore, the present character-set menu applies only to the terminal emulation character set, and it lists many sets that are not implemented. These should be removed. The new menus should look approximately as shown at the end of this file, in the proposed menu design appendix. MAC KERMIT CHARACTER SET AND FONT BUGS There is presently no way for users to specify their own character-encoding translations. The translations for file transfer and terminal emulation are built in to Kermit. A point size of 7 is listed in the Font menu, but it can't be selected. Mac Kermit's built-in VT100 terminal font does not scale well to any size other than 9. Mac Kermit's VT100 font has entirely different character codes than all the other Mac fonts for the "special" (8-bit) characters. If you switch to, say, Courier for terminal emulation, all the special characters (accented letters, etc) come out wrong. Furthermore, Apple character encodings (like Quickdraw) lack certain characters (e.g. Icelandic Thorn and Eth) needed for Latin-1. The VT100 font is built into Mac Kermit, which means it can't be hooked in to Key Caps, so you can never find out what keys to type in order to send special characters. This also seems to cause some problems with SuitCase and friends. The font should be externalized, but then it becomes difficult to install Mac Kermit -- you can't just stick in the disk and run it, you have to install fonts first. It would be best to keep the font defined in Mac Kermit, but also have an external copy for the benefit of Key Caps. The VT100 font doesn't print correctly (accented characters, VT100 special and technical characters, etc). See the separate file, ckmker.fon, for a detailed description of these problems and a proposed solution. Proportional fonts can be selected during terminal emulation, but of course they don't look right because terminals use fixed-width fonts. Maybe proportional characters could be displayed within fixed-size boxes. Or maybe Kermit should only allow monospace fonts in its font menu. Selecting the Chicago font doesn't work at all (a mystery). TERMINAL EMULATION BUGS & LIMITATIONS Local echoing doesn't work very well. Window height can be changed, but not width. We need (at least) 132 column mode, and a terminal width menu selection (and correct response to VT "set width" escape sequences"). Keyboard handling is not independent of the keyboard driver -- it assumes the US keyboard driver. For example, Mac Kermit doesn't handle dead-key combinations used in France, Sweden, etc. Mac Kermit accesses the KCHR resource, which is a no-no for System 7. There is no way to find out how to type "special" (accented) characters during terminal emulation. This problem should be fixed when the new Extended Mac Latin font is finished and integrated with Kermit. Then you'll be able to access it from keycaps. There is no mechanism (such as SO/SI, SS2, or SS3) for sending 8-bit characters to a 7-bit host during terminal emulation. Mac Kermit does not respond to host-generated escape sequences to designate selected character sets to G0..G3, for example ESC - A to designate Latin-1 to G1. Mac Kermit should support: ESC ( Designates 94-byte character set to G0 ESC ) Designates 94-byte character set to G1 ESC * Designates 94-byte character set to G2 ESC + Designates 94-byte character set to G3 ESC - Designates 96-byte character set to G1 ESC . Designates 96-byte character set to G2 ESC / Designates 96-byte character set to G3 where the are: Size Character-Set A 96 ISO Latin-1 B 94 ASCII (default in G0, G1) 0 94 DEC Special Graphics 1 94/96 VT100 Alternate ROM 2 94 DEC Special Graphics %5 94 DEC Supplemental Graphics = DEC Multinational Char Set > 94 DEC Technical There is no mechanism for the user to explicitly designate character sets to G0..G3. See menu design in the Appendix for how to do this. Reportedly, trying to scroll the terminal window while data is being sent to it can crash the Mac (I can't reproduce this one, maybe it's fixed now... or maybe it only happens with SuitCase, etc, loaded). Various VT200/300 functions are not implemented, including the character-set related items mentioned above, UDKs, various DECDSR, DECRQM, and other report requests (UDK status, keyboard dialect, keyboard action, insert/replace mode, newline mode, cursor key mode, numeric keypad mode, 132 column mode, smooth scroll, reverse video, autowrap, palette request, UPSS state, tab stops). Various obscure bugs with VT320 character attributes (most frequently appearing when using the UNIX "more" command). Various failures with "vttest". Set Key dialog box should show what a key sends if it is "unbound". Set Key Macros should allow decimal and hex escapes as well as octal, like MS-DOS Kermit (or C-Kermit itself): \onnn = octal, \dnnn = decimal, \xnn = hex, \nnn defaults to decimal (of course changing the default will cause problems). C-Kermit already has code to parse these forms, as well as to handle grouping, e.g \{27}2 to send ESC followed by 2. Bad default mappings for many keys: Ctrl-1, Ctrl-2, etc, thru Ctrl-0. (Also Shift-Ctrl-1, etc). Ctrl-2 and Ctrl-Shift-2 should send NUL (ASCII 0). Ctrl-6 and Ctrl-Shift-6 should send Ctrl-^ (ASCII 30). The other top-rank number keys should send nothing when pressed with Ctrl. Reportedly, under System 7 some of these key combinations aren't even noticed. Others too: Ctrl-+, Ctrl-; have codes when they shouldn't, etc etc. Arrow keys occasionally send incorrect sequences. TO CHECK: Do arrow keys and numeric keypad keys respond correctly to: ESC = DECKPAM Set numeric keypad to application mode ESC > DECKNPNM Set numeric keypad to numeric mode CSI ? 1 h SM Set arrow keys to cursor mode CSI ? 1 l RM Set arrow keys to application mode Codes sent by arrow keys: Key Cursor Application Up CSI A SS3 A Down CSI B SS3 B Right CSI C SS3 C Left CSI D SS3 D Codes sent by keypad keys: DEC Mac Key Key Numeric Application PF1 clear SS3 P SS3 P PF2 kp = SS3 Q SS3 Q PF3 kp / SS3 R SS3 R PF4 kp * SS3 S SS3 S 0 kp 0 0 SS3 p 1 kp 1 1 SS3 q 2 kp 2 2 SS3 r 3 kp 3 3 SS3 s 4 kp 4 4 SS3 t 5 kp 5 5 SS3 u 6 kp 6 6 SS3 v 7 kp 7 7 SS3 w 8 kp 8 8 SS3 x 9 kp 9 9 SS3 y comma (,) kp + , SS3 l minus (-) kp - - SS3 m period (.) kp . . SS3 n Enter enter CR or SS3 M CRLF (newline ON) Similar comments about the DEC function keys F1..F20. They should be mapped in some fashion to the Apple function keys (F1..F15). Keyboard verbs should be assigned for all keys that send escape seqeunces, so users can remap them without having to know what the escape sequences are -- especially if the escape sequences can change based on host-controlled mode setting commands. See how MS-DOS Kermit handles this. A wealth of information about VT (and Heath) terminal emulation can be found in kermit/a/msvibm.vt (the online description of the MS-DOS Kermit terminal emulator) on watsun.cc.columbia.edu, or (in more complete form) in Appendices I and II of "Using MS-DOS Kermit", Second Edition, by Christine M. Gianone, Digital Press, 1991. COMMAND BUGS Various commands are missing or non-operational: DIRECTORY, CD, PWD, PRINT, etc. These should be filled in. (NOTE: there is something in the MPW 3.2 release notes that says how signal(SIGINT,xxx) can be used to catch "Command-."). The command window scrollback feature doesn't work until after you leave the command window and then reenter it. No filename completion when ESC or TAB is typed within a filename, no file lists are produced when "?" is typed in a filename, and yet there is no beep to indicate these features don't work (instead, the cursor disappears). Sometimes the TAKE command doesn't work (an alert box comes up: "Writing to console in applications is not support"). Sometimes it does work. We haven't narrowed this one down yet. Ditto for launching Kermit from a TAKE file (Kermit document containing text commands) (this works fine for me, but one user reported that whether it works depends on the file's name!). Some SET commands have no effect, in particular all the SET TERMINAL commands, SET FILE NAMES, ... These should be filled in, i.e. hooked in with the Macintosh code so that both pieces of the program (Mac menu and C-Kermit command parser) use the same variables. The SET CARRIER command should be removed (the Mac hardware doesn't handle carrier). (Done in edit 178) The READ command doesn't work (gets "Unknown IO error: -51", followed by "zclose(): I don't know what kind of file this is: 9"). The PAUSE command should wake up immediately (and fail) if the user hits a key or clicks the mouse. Some of the \v(...) built-in variables don't work right: directory, home, host. \v(directory) should show the name of the current folder. \v(host) should show the Appletalk node name (if any) of the Macintosh. \v(home) should probably show the name of the current disk volume. SET LINE should be converted to use a keyword table (the choices are MODEM and PRINTER). (Well, not really -- we still want them to be able to type real device names...) Messages displayed by the DIAL command, by script execution, etc, do not appear on the command window screen until the next prompt appears. In fact, this seems to be true of the messages displayed by any command, but most other commands finish quickly and a prompt is issued right away, so you don't notice this effect except for DIAL, etc. SET DIAL DISPLAY ON doesn't work at all (even though dialing itself works fine). The TRANSLATE command seems to work, except if you want it to display the results on the screen instead of writing them to a file (in which case it writes the output to a file called "/dev/tty" -- oops!). (Fixed in 178 -- now if no output file is specified, the translated text goes into the response window.) In SEND, TRANSMIT, TRANLATE, and other commands that accept Macintosh filenames, you can't include spaces in the filename. To refer to filenames containing spaces at the Mac-Kermit> prompt or in command files, replace the space by \32, for example: Mac-Kermit>send This\32is\32a\32File FILE TRANSFER PROBLEMS Some apparent problems with very long packets (like 9000), not that anybody really should be using them. An official, invertible translation between ISO Latin-1 and Apple Quickdraw does not exist (or, at least, we don't know about it). Extended Mac Latin is used in this version. This set is specified in the separate file, ckmker.fon, which also discusses the other character-set and font-related issues. When downloading a file to the Mac, the file mode (text or binary) as announced in the sender's Attribute packet is not picked up by Mac Kermit, you have to click the text or binary button in the File Defaults Settings menu first. When using the SEND command to specify the full or relative pathname of a file to send (including disk or folder names), Mac Kermit doesn't strip the disk or folder name (fixed in 178). Incoming MacBinary files are not recognized automatically -- you have to click the MacBinary button beforehand. (Not really a bug, just a desirable feature. Apparently some other Mac communication programs can do this.) The text-mode file transfer translations between Latin-1 and Apple Quickdraw are somewhat arbitrary. See ckmker.fon for the proposed new translation, which will be installed in a future edit. When sending files, the file transfer display thermometer only works on the second and subsequent files in a file group, so you never see it when sending files unless you use the MSEND command from the command window or click on "All files in folder" in the Send dialog box. There is no way to set the ID signature (associated application) of an incoming file. They all become MacWrite documents (except if downloading in MacBinary mode.) There should be a way to specify the ID for an incoming file, or at least make it a TeachText file instead of MacWrite. (NOTE: MPW C 3.2 has a new function for doing this: fsetfileinfo() -- see release notes.) If a file server disk goes away (e.g. because the connection dropped) in the middle of a file transfer, The Mac hangs and has to be rebooted with the programmer button. In the file-send dialog box, there is no way to mark selected files for sending (e.g. shift-click, shift-drag). You can only send a single file, or else all the files in a folder. (But you can use MSEND in the command window to send a selected list of files.) The file transfer display / dialog-box needs a button for "retransmit the last packet" to let the user wake up a transfer that seems to be stuck. Maybe also a "send XON" button to let the user try to break an XOFF deadlock. SET FILE DISPLAY NONE should be able to disable the file transfer display window altogether, for "silent running", for example, for people who want to incorporate Kermit into their BBS software. It would also be nice if the file transfer display showed the name of the current folder. The "find a new unique filename" algorithm is not great. It starts with the filename, if it exists, appends ".0", then ".1", etc, up to ".99". However, this doesn't guarantee that the newly created version will be higher than all the others. If .1 and .3 exist, Mac Kermit will create .2. The File Settings menu selection "Supersede existing files of the same name" doesn't seem work. But SET FILE COLLISION (in the command window) works correctly (except for APPEND, which acts like OVERWRITE). When a REMOTE command is given from the command window, the Response window does not pop up to show the response. However, if you select the Response window in the Window menu, you'll see the server's responses have been collected there. To be checked: . Mac Kermit's reaction to incoming Attribute packets. Will it reject a file on the basis of size? (It should) . I'm pretty sure (but not positive) it reacts correctly to the encoding/character-set attribute. But it should show the active character-set conversion in the file transfer display, or at least include it in the after-the-fact statistics display. SERVER MODE 1. Mac Kermit server mode in general (NOTE: these haven't been checked recently, maybe they are fixed)... Sending a text file to the Mac Kermit server works fine. Getting a text file from the Mac Kermit server also works fine, except the status screen still says "Receiving". REMOTE SET FILE TYPE BINARY, sent by a client to the Mac Kermit server, works. Binary file transfers in both directions work fine. There is, of course, no way for the client to put the Mac Kermit server into MacBinary mode, because as far as the Kermit protocol is concerned, MacBinary is an unknown file type. REMOTE DIRECTORY sent to the Mac Kermit server, doesn't work (It sends back an E-packet saying "Can't list directory"). FINISH works, the file transfer status screen disappears, but the File Transfer top-level menu item remains highlighted. 2. MacBinary transfers with the Mac Kermit server. OK, now we want to transfer files in MacBinary mode with a Mac Kermit server. We click on MacBinary in the File Settings menu, then put Mac Kermit in server mode. GETting a file from the Mac Kermit server: screen display says "Receiving" (instead of sending). Giving a REMOTE HELP command to the server apparently makes it forget it's in MacBinary mode. A subsequent GET has Mac Kermit sending the data fork only (empty), in binary mode. Putting it back in MacBinary mode manually, and a subsequent GET, gives checksum errors. Then Mac Kermit forgets it's in MacBinary mode again. In general, there seems to be a lot of problems with Mac Kermit remembering that it's in MacBinary mode. This is no doubt because Mac Kermit keeps its own private variables (one for text / binary / macbinary, another for data / resource / both fork(s)) instead of using Kermit's built-in "binary" variable. This needs to be reworked. APPENDIX: MENU DESIGN (DRAFT!) Top-level menu: ------------------------------------------------------------ File Edit Settings Special Transfer Window ------------------------------------------------------------ File ------------------------------ New Open... Close Save Save As... ------------------------------ Take Command File... Take Commands from Window ------------------------------ Page Setup... Print Screen... Print Selection... Log Session to Printer... Cancel Printing (Printer buffer status?) ------------------------------ Chain to Application... Quit ------------------------------ The Page Setup dialog should include a section that tells what to do with host-initiated printing (transparent print or autoprint): ------------------------------ (x) Send to printer ( ) Save in Printer window ( ) Save in file... ( ) Discard ------------------------------ Edit ------------------------------ Undo ------------------------------ Cut Copy Paste Clear Select All ------------------------------ Settings ------------------------------ Load Settings... Save Settings... ------------------------------ Communications... Kermit Protocol... File Transfer Defaults... File Transfer Character Sets... Terminal Characteristics... Terminal Character Set... ------------------------------ *-Shift-1..*-Shift-9 Active Menu *-Keys Active Key Macros... Key Modifiers... ------------------------------ Here is the terminal character sets dialog. It's sort of an ISO 2022 tutorial. The first section "designates" character sets to graphics areas G0..G3. Only one radio button can be pushed in each column, but multiple buttons can be pushed in a row. A 96-byte character set (Latin-1 and DEC MCS are the only ones) may not be designated to G0 (ISO rule). If Latin-1 or DEC MCS are chosen, G0 is automatically forced to ASCII. The second section "invokes" the selected graphics areas to GL and GR. Only one button can pushed in a row. ------------------------------------------------------------------- Terminal Character Sets G0 G1 G2 G3 US ASCII (x) ( ) ( ) ( ) ISO 8859-1 Latin-1 (x) ( ) ( ) <-- Note: No G0 here (dim) DEC Special Graphics ( ) ( ) (x) ( ) DEC Technical ( ) ( ) ( ) (x) DEC Multinational ( ) ( ) ( ) <-- Note: No G0 here (dim) British/UK ( ) ( ) ( ) ( ) Canadian French ( ) ( ) ( ) ( ) Dutch ( ) ( ) ( ) ( ) Finnish ( ) ( ) ( ) ( ) French ( ) ( ) ( ) ( ) German ( ) ( ) ( ) ( ) Italian ( ) ( ) ( ) ( ) Norwegian/Danish ( ) ( ) ( ) ( ) Portuguese ( ) ( ) ( ) ( ) Spanish ( ) ( ) ( ) ( ) Swedish ( ) ( ) ( ) ( ) Swiss ( ) ( ) ( ) ( ) ------------------------------------------------------------------- Graphics Left (GL): (x) ( ) ( ) ( ) Graphics Right (GR): ( ) (x) ( ) ( ) ------------------------------------------------------------------- For file transfer character sets, the "Language rules" apply only if ASCII is checked in one (not zero or two) of the first two columns), otherwise the language rules buttons should be dim. ------------------------------------------------------------------- File Transfer Character Sets File Character Set Transfer Character Set Language rules (x) Apple Quickdraw (x) Transparent (x) None ( ) ASCII ( ) ASCII ( ) Dutch ( ) ISO Latin-1 ( ) ISO Latin-1 ( ) German ( ) Icelandic ( ) Scandinavian ------------------------------------------------------------------- THE COMMUNICATIONS SETTINGS DIALOG Here we need a couple changes in terminology: 1. "Baud Rate" is "incorrect". It should say "Transmission speed" or "Transmission Rate", or (if that's too long), simply "Speed". 2. "Drop DTR on Quit" is obscure. It should say "Hangup on Quit". FILE SETTINGS DIALOG: ------------------------------------------------------------------- ( ) Attended: dialog on each file received (x) Unattended: with the following defaults: File Names: (x) Converted ( ) Literal Filename Collisions: (x) Backup ( ) Append ( ) Discard ( ) Overwrite ( ) Rename ( ) Update [ ] Keep partially received files Transfer Mode: (x) Text Fork: (x) Data ( ) Binary ( ) Resource ( ) MacBinary ------------------------------------------------------------------- THE TERMINAL SETTINGS DIALOG Change "[ ] Accept 8 Bit Characters" to: Character size: (x) 7 bits ( ) 8 bits THE PROTOCOL SETTINGS DIALOG (OK) THE SPECIAL MENU: Special ------------------------------ Hangup Send Break Send Long Break Send XON Reset Terminal ------------------------------ Log Session... Dump Screen... Log Transactions... Log Packets... Log Debugging... Call Debugger... (dim if no debugger loaded) ------------------------------ THE TRANSFER (File Transfer) MENU: Transfer ------------------------------ Send file... Receive file... Get file from server... ------------------------------ Show statistics ------------------------------ Change directory ------------------------------ Change remote directory Delete remote file... List remote files... Remote help Remote host command... Remote Kermit command... Remote space... Remote type... Remote who... Send file to server for printing... ------------------------------ Finish server Logout server ------------------------------ Enter server mode ------------------------------ THE WINDOW MENU Lists the names of the windows. It should be modified to check or highlight the currently active window. Assuming that font changes can be made to work in all windows, we should move the Font item to here, and have it invoke a submenu, applying to the current (checked) window (the whole window? A selection within a window?) (We have to move the Font menu because there isn't enough room for 7 menu items in the top-level menu.) For example: Window ------------------------------ X Terminal Window (X = checked) Command Window Response Window Untitled-1 ------------------------------ Font -> ------------------------------ ------------------------------ 9-point 10-point 12-point 14-point 18-point ------------------------------ Avant Garde Bartholemew Bookman Chicago (etc) ------------------------------ (End of ckmker.bwr)