Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!duncan
From: duncan@csd4.milw.wisc.edu (Shan D Duncan)
Newsgroups: comp.sys.amiga
Subject: "modular" programs
Message-ID: <802@csd4.milw.wisc.edu>
Date: 7 Feb 89 04:48:10 GMT
Sender: news@csd4.milw.wisc.edu
Lines: 57



[might as well get all of my postings out at once!]

I followed the discussion of terminal programs with interest.

From that discussion specifically with Atalk III it seems clear that "ya
can't please all the people..."  AND "they get bigger and bigger and bigger"
(software not people necessarily)

Most of the time all I need is a way to communicate with our unix
system and perhaps download\upload files from time to time.

Given the state of software to this date how difficult would it be to
design a "modular" type of terminal software?  Forgive me for the use
of modular since it can mean different things to different people perhaps
what I really I mean by this term is a customizable terminal program.

Upon bootup  a menu is presented that goes through all of the possible
options available (i.e. (1) startup options usually handled by scripts
(number(s) to call, strings to send, delays), (2) transfer protocols
(kermit, zmodem, ymodem whatever), (3) terminal options (vt100, vt220,
addsviewpoint again whatever) (4) and the list goes on and on.

Once the options are selected then a custom version containing only the
code necessary and perhaps only the FEW options YOU want is *somehow*
produced to be run.  Then if any new options are provided  and if you need
or change your mind them make up a new version of the program program. 
As long as you do not wish to change anything then you should not need to
go through the setup procedure again.

 Of course I am being somewhat naive.  But there should be a way
to have a program that only executes the options you want without having 
to carry around all of the options everyone else wants but you could care
less about!  I know.  I know the most obvious answer to this is 

              *****"write your own!"***** :-)


I would guess that source code plus a "small" compiler necessary to "make"
only that program might work but would anyone go to the trouble  
to make life easier for the user if it meant more trouble for the publisher
:)  OR in the long run would it?

How about Arexx gluing together all the necessary parts (i.e. terminal
emulator, serial port, scripts, file transfer protocols, with only the
code actually being used in memory)?

Perhaps OOPS?

If I speak in ignorance - educate!   
I am looking forward to all of the education these musings might generate!
:-)

SIGH back to thesis typing.  

shan                     duncan@csd4.milw.wisc.edu