Xref: utzoo comp.sys.amiga:33532 comp.sys.amiga.tech:5030
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!accuvax.nwu.edu!tank!eecae!cps3xx!golden
From: golden@cps3xx.UUCP (golden james)
Newsgroups: comp.sys.amiga,comp.sys.amiga.tech
Subject: Re: Standard File Requesters
Summary: Mr. Ferguson has the right idea!
Message-ID: <2915@cps3xx.UUCP>
Date: 10 May 89 06:57:31 GMT
References: <0914.AA0914@amigash> <941@sactoh0.UUCP> <11583@well.UUCP>
Reply-To: golden@cps3xx.UUCP (golden james)
Distribution: comp.sys.amiga,comp.sys.amiga.tech
Organization: Engineering, Michigan State Univ., E. Lansing
Lines: 23

In article <11583@well.UUCP> shf@well.UUCP (Stuart H. Ferguson) writes:
>to write well, which leaves developers with few alternatives.  The end
>result is that almost everyone has almost no programs with file requesters
>they like.
>
>There are some PD file requesters -- but what if you don't like them?
...
>How about a "filerequester.library?"  It could be spec'ed as having a 
>known interface that anyone could write towards -- from both sides.
>Developers would have access to a generic file requester from within
>their programs, users would see a consistent interface, AND users could
>choose the requester they want from as many possible
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>filerequester.library's as could be written.  You could use the Dillon
>fr.library, or the Schwab fr.library, or the RJ ...

Or even a FileReq.device - who knows?  Just drop your favorite in the
right drawer, and you'll have an instant common user interface to all
your favorite (participating) programs.  Great Idea!!

   Mike Golden
   Physiology Undergraduate
   Michigan State University