Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JR-Comm 1.10 Features
Message-ID: <72@faatcrl.UUCP>
Date: 18 Aug 90 17:24:47 GMT
References: <ias3N10w162w@valnet.UUCP>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 41

joseph@valnet.UUCP (Joseph Hillenburg) writes:

>1) 2.0 compatibility - Reason: I don't want to pick up a new copy of 
>JR-Comm, tehen have it break when I get OS 2.0.

Will have it with 1.01.

>2) ARexx - Reason: Why not?
>3) Scripts -Although, if ARexx is properly implemented,  this won't be 
>neccesary.

Probably for 1.2.

>4) XPR support.

Definately for 1.1.

>5) IBM Color and Mono wrapped up into one.

Are you refering to 16 colors w/blinking attribute?  If so, maybe in the
future, but not now.  If not, what are you refering to?

>6) The following XPR protocols: XPRxmodem, XPRymodem, XPRzmodem, 
>XPRjmodem, XPRkermit, XPRascii, XPRSealink(?), and XPRsadie.

I'll put the hooks in there for XPR, but I won't be writing the XPR modules
except for the CIS B+ one since I'll be removing that protocol from the 
program.  As for ZMODEM, an XPR module could never acheive the throughput
that the internal code gets, so that will remain internal.

>7) Less "undesirable features". (bugs)

This goes without saying...

>Circumstances prevent me from mailing John (Jack?) Radigan a registration 
>form. J.P. Radigan, if you are reading this, please send me a form. I 
>would gladly register if you did. (My PaintJet is in the Shop).

Ok, will do.

  -jack-