Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!keating
From: keating@rex.cs.tulane.edu (John W. Keating)
Newsgroups: comp.windows.ms
Subject: Windows Communication Package Ideas
Message-ID: <5750@rex.cs.tulane.edu>
Date: 18 Jan 91 05:56:07 GMT
Sender: keating@rex.cs.tulane.edu
Organization: Computer Science Dept., Tulane Univ., New Orleans, LA
Lines: 34
Keywords:

This is a start to a comm program wish list that I had started earlier in
the year.  I'm still working on the money to get myself a copy of MSC, so
it has been in the closet for a while.  Looking for spave, I decided to
dust it off and see if the net had any ideas or comments...

---

What I would like in a comm program:

<1> Seperate entrees for each number, including:
    o Name field.
    o Longer Description / note field.
    o Phone Number field.
    o Baud autoradio buttons.
    o Data bits autoradio buttons.
    o Stop bits autoradio buttons.
    o Delete / Backspace
    o Terminal emulation preference. (see <2>)
    o Preferred transfer protocols. (see <3>)

<2> Terminal emulation:
    o Standard ANSI, VT-100, VT-52
    o Ability to add in new emulations with a minimum of effort.
	~ Some kind of TERMCAP set?

<3> Transfer protocols
    o Seperate add-in modules for each protocol
	~ May or may not be feasible.  What I envision is something
	  in the line of a standard language for protocols.  I don't
	  really know enough of how the algorithms work to say whether
	  this is workable.

    o Multi-window mode for working with multi-tasking systems.

...