Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!gvlv2!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga
Subject: Re: JrComm 1.0
Message-ID: <1501@faatcrl.UUCP>
Date: 18 Jul 90 14:36:21 GMT
References: <31705@cup.portal.com> <619@cbnewsb.ATT.COM>   <5213@darkstar.ucsc.edu> <31850@cup.portal.com>
Distribution: na
Organization: FAA Technical Center, Atlantic City NJ
Lines: 25

Doug_B_Erdely@cup.portal.com writes:

>Well, I guess its my turn to complain! :)  Why o WHY! did jack waste time
>on Skypix graphics when we are STILL missing a very basic, yet important
>part of any term program on just about any computer? I am refering to
>scripts/ARexx port. I would rather see both, but just providing hooks into
>ARexx would be great! At this point this is the single reason WHY I have
>not registered/used JRComm. The idea being you register the software that
>does what you need. The program does not provide what *I* need, so that
>means $30 bucks less for Jack, simple!

Simple.  There seemed to be a need at the time (over a year ago) for a
Skypix emulation in a comm program that had more going for it then the
bare minimum.  Also, since the word had gotten out that ARexx was to be
incorporated in Workbench 2.0, I figured that I would concentrate on the
emulations and protocols first and then work on Scripts and Arexx afterwards.

I also miss scripts and ARexx, and plan to correct that deficiency soon, but
the fatc remains that the large body of comm users have little need for ARexx
much less scripts, so I went the route I did.

As for registering, do as you will, but if you're using the program with any
regularity you *should* register.  If not, no huuhuu. 

  -jack-