🚀 go-pugleaf

In article <yorkw.658814848@stable.ecn.purdue.edu> yorkw@stable.ecn.purdue.edu (Willis F York) writes:
   Ever see MFF+ (MicroFiche Filer +) I don't have the Manual handy but the
   Arexx commands are Annoying "Named"  here are a few top'o my head
   suggestions to help smooth out commands/ports

Huh? I use MFF+ on a regular basis. Off the top of my head, it's the
BEST example of how to do an ARexx interface I've run into. I _think_
you're complaining about case sensitivity - and MFF+ isn't case
sensitive. Commands can be issued in any case. Please provide more
details if this isn't the case.

   Have the port name in Lowercase letters.
   use all lowercase. (I spent an Hour figering oou why somthing wasen't working
   , Aress was upper casing the portname and i needed to ad some ' marks)

Actually, to solve your problem, the port name needs to be in UPPER
case, not lower. That way, you don't need to quote the port name.

   Give Nice names to the commands but avoid LONG command names.
   Mff+ is a good bad example of this.

And LSE is a good example of going to far the other way (all the
commands are two-character sequences, with possible two-character
arguments).

   To get WB to front (I think this is right) the command is .
   "MFF+_to_Back"
   . (Descripitive but annoying)
   All the other commands are equally weird.
   the Case is Mixed also, which has caused problems.

The commands are listed in mixed case; MFF+ is quite happy swallowing
them in whatever case you wish to use.

   (MFF uses a Weird way of Macros which are rexx scripts in single quotes
   and commands.mff which are normal rexx stuff.

That's not wierd, that's normal. Looks just like wshell (or mg3, for
that matter). It's what ARexx provides by default when you send a
macro to ARexx from the application.

	<mike
--