Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!mit-eddie!uw-beaver!microsoft!bradch From: bradch@microsoft.UUCP (Bradford Christian ms1) Newsgroups: comp.sys.amiga Subject: Re: Standardization Keywords: spam Message-ID: <1077@microsoft.UUCP> Date: 20 Oct 88 05:39:10 GMT References: <1304@nmtsun.nmt.edu> <4166@boulder.Colorado.EDU> Reply-To: bradch@microsoft.UUCP (Bradford Christian ms1) Organization: Microsoft Corp., Redmond WA Lines: 24 So, I've been lurking about this news thing for about a month now, and figgure it's about time to try to make a contribution... I agree that there is a great need for a standard file requestor, but I also do not necessarily want the same requestor as Joe Blow. Rather than speccing standard file requestors, we'd all be better off if a standard application interface to a file requestor were specified (and endorsed by C-A, of course). Then, file requestors could be created as exec libraries and dynamicly linked with the applications that need them. This would allow everyone to have their own "standard" file requestor. I'm sure there are enough people out there who think they can create the ultimate file requestor, and some of them will put their creations in the public domain. This idea applys to many other objects that appear in various applications. Color requestors immediatly come to mind. Wouldn't it be great if you could use your favorite color requestor in EVERY program that let you pick a color? BradCh _ /) My opinions are not usually the same as my employers'. \`o_O' (But then, whose are...) =( )= Ack! U