Path: utzoo!attcan!uunet!convex!killer!ames!mailrus!ncar!gatech!kong!emory!stiatl!meo
From: meo@stiatl.UUCP (Miles O'Neal)
Newsgroups: comp.windows.x
Subject: Public Domain Widget Library
Message-ID: <1669@stiatl.UUCP>
Date: 18 Nov 88 22:47:30 GMT
Organization: Sales Technologies Inc., Atlanta, GA
Lines: 114


A while back, I tossed out the idea of having a widget library, where
people could donate widgets, and they would be publicly available. I
asked whether there was such a thing, and where, and if not, whether
others were interested.

I heard from nobody telling of such a thing.

I heard from several people who were interested in such a library.

So, this is announcing that I will start a

             PUBLIC WIDGET LIBRARY

Real Soon Now [ 8{) ]. Actually, within the next 2 weeks.

As this is a public service, I will solicit suggestions before starting it.

First, some ground rules. At least initially, for disk space reasons,
the library will not be directly accessable to the net. Widgets will be
stored on a system that is connected via TCP/IP to our net interface
system, but the two do not currently have a mail interface, due to
the different mfr's ideas about what standard is (grrr).

So, there will be an account available to the net, to which submissions
or requests will be directed. I will then take care of moving new source
to the library, or mailing out widgets to those requesting them. A directory
will also be available upon request.

I am thinking along the lines of having an account named xwidgets, to which
mail should be sent. The Subject line would indicate what was desired:

help     - send info describing how to use the library
dir      - directory of available widgets, version level, and status
           (untested, tested on Sun386, etc)
request  - request for materials; second word should be either:
           library - the whole thing, or
           <name>  - name of widget as published in the directory
submit   - the body of the mail message contains a submission
bug      - the body of the mail message contains a bug report
bug fix  - the body of the mail message contains a bug fix
question - the body of the mail message contains some question about
           the library system, a widget, or anything related
other    - the body of the mail message contains anything else

What have I missed? Does this look good to you?

I do not see this as a place for stuff readily available elsewhere,
such as on the MIT tapes. This is for "the rest of us", just to make
life easier for us.

For the time being, please either post responses, if they seem like
they ought to be public, or else send me email at

gatech!stiatl!meo

and let me have your thoughts.

Obviously, I can support shar format. Other formats may be acceptable;
just remember that any compression that results in anything other than
7-bit ASCII codes may have problems getting across the net. Suggestions
are welcome.

While I will at least look at anything that comes in, portable,
well-documented stuff will get first priority. I have a Sun 386i
available, and will eventually be able to test compile on some
other systems, but in the meantime will have to depend on the stuff
working as advertised. If anybody else is interested in being a test
site for widgets on other systems, let me know.

I will commit to be honest and release nothing I even suspect to be
dangerous. Neither my employer nor I will assume any liability for
any code sent from the library. For obvious reasons, only source
code will be considered.

I will expect the following to be provided:

all necessary source files, other than system include files,
a Makefile, preferably with the following targets:
   all
   install
   clean
   (others, such as link and man, are of course welcome),
a man page (similar documentation from non-Unix systems will
   be acceptable, but in addition to any input files, a printable
   version will need to be included)
a README file.

All source code and documentation must include a copyright notice.
If no copyright notice is provided, I will provide one.

Any widgets meeting these criteria, that I can compile & run, that work
well, that don't cause trouble, will go in the library. Other stuff
may or may not make it - probably will, with status notes attached.

I will usually respond to library correspondence within 3 working days,
unless I am not here, in which case I will try to get someone else to
cover for me. I will try to respond within 1 working day; obviously
this depends on my schedule (my employer likes some of my time, too 8{).

If there is interest, I could look into making libraries available
on tape or floppy; there would probably be some charge for this.

Please email or post your responses in comp.windows.x; it will be at least
a week before I can consider really starting this up, due to my current
schedule.


I am also considering posting a notice about the library, a current
directory and a request for widgets, once a month in comp.sources.x
or comp.windows.x - which is the correct group for this?


-Miles O'Neal     (gatech!stiatl!meo)