Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!sdcc6!babymilo!lindwall
From: lindwall@babymilo.ucsd.edu (John Lindwall)
Newsgroups: comp.sys.amiga
Subject: Re: Printer icon (was: Why is everyone bitching about Workbench)
Message-ID: <13710@sdcc6.ucsd.edu>
Date: 30 Oct 90 03:15:43 GMT
References: <6895@sugar.hackercorp.com> <15446@cbmvax.commodore.com> <400@ra.abo.fi>
Sender: news@sdcc6.ucsd.edu
Organization: CSE Dept., UC San Diego
Lines: 47
Nntp-Posting-Host: babymilo.ucsd.edu

In article <400@ra.abo.fi> rosenber@ra.abo.fi (Robin Rosenberg INF) writes:
> [How will a print-service icon know file formats?, Good suggestion to use
>  Arexx to send print message to appropriate application]
>
>A few things needs to be standardized.
>1. Can the application receive messages?
>2. What is the name of the rexx port?
>
>Suggested solution(s) to
>1) This is tricky. I know of no way. So why not take a chance. Let
>   the printer launch the application and IF a rexx port comes up
>   with a name according to (2) then send the commands. IF no port
>   comes up within some period of time. Just skip it.

Or perhaps, create a Rexx-port name-server, which maintains a list of
(<Application-name> <Arexx-port>) bindings.

To refine the idea:  Since there is no standard
for naming of rexx commands, a generic 'print' command will not always
have the desired effect.  Therefore, I submit the (grandiose, naive, etc)
idea of having the applications submit their (<AppName><PortName>) pair
along with mappings of common functions, (e.g.  Print, Display, ???).

Thus when I run SuperWordProcessor, it contacts the name-server and tells
it:
	"I am SuperWordProcessor, my Arexx port is called FooPort.
	   I support printing with the command 'DumpThisJunk'
	   I support file display with the command 'ShowThisJunk'
	   I support functionX with the command 'DO_X_OnThisJunk'
	etc..."

>
>2) The rexx port has the same name as the Application.
>   or A tooltype says REXXPORT=name_of_rexxport. The latter applies
>   if present.

But many (most?) applications do not do consistent naming in this way,
a more complex scheme should be considered.  Or else, enforce the naming
convention (but as I've learned Amiga-types don't like standardization :) )

>Comments, flames >nil:,  ideas?

Good thinking, I hope we see more discussion on this topic.  Using Arexx
to its potential is a dream of mine.
-- 
John Lindwall			lindwall@ucsd.edu
"Oh look at me! I'm all flooby! I'll be a son of a gun!" -- Flaming Carrot