AREXX
2 messages in this thread
Hey, all,
What's the easiest, most efficient, least costly,
most rewarding, least time consuming, most honorable,
and least carcinogenic way to add AREXX support to a product?
I remember reading somewheres that there are degrees
of support, but for the past 6 months we've been working on
an MSDOS (AARRGGGGHHHHHHHH!) product, and I haven't quite kept
abreast of current developements. Any help would be greatly
appreciated. . .
R. G. Marquez \|//
_oo // ECHiDNA
Basically, your program must have a message port set up to send and recieve
ARexx messages.. this is pretty easy. next you should have a logical subset
of your prog.s functions made accessible by remote ARexx messages, as well
as the interactive interface. eventually you will have a command language
for your program, which other ARexx scripts can use. A next level of
support would allow
your user to run rexx programs from within your app., allowing them to
construct macros for doing complex things in your prog., or for
coordinating data and operations between several applications… How much
of this is relevant to your prog. depends on its function
etc. but some programs are really well suited to being run as remote
processors while others are solely useful as interactive tools.