🚀 go-pugleaf

Archive-name: xcb-1.1
Submitted-by: fbm@ptcburp.ptcbu.oz.au (Farrell McKay)

This is to announce the second release of xcb, an X11 program for
providing easy access to your X server cut buffers.

Xcb has been ported to a wide variety of sites and environments
since its initial release several weeks ago.  This release provides
a few minor bug fixes and enhancements, and adds support for
non-standard (non-ANSI) C environments.

You can obtain xcb by sending me an email message, or by ftp
from export.lcs.mit.edu (fetch the file contrib/xcb-1.1.tar.Z).
Xcb was also posted to the comp.sources.x newsgroup three weeks
ago, but has not yet been processed by the moderator.  It should
appear there sometime later this year.  ;-)

Many thanks go to all those people who took the time to send
back their comments/suggestions/patches after the last release.
Your feedback has not been in vain, even though there are few
new features in version 1.1.  Stay tuned for the next exciting
episode.

And once again, *be warned*, using this program can be addictive.  :-)

Enjoy.
Farrell.
--
      -m-------  Farrell McKay,                   fbm@ptcburp.oz.au
    ---mmm-----  Pyramid Technology Aust.,        ...!munnari!ptcburp.oz!fbm
  -----mmmmm---  Research Park, Bond University,  +61 75 950256
-------mmmmmmm-  Gold Coast, Qld 4229, AUSTRALIA  +61 75 722475 FAX
----------------------------- README -------------------------------------------

What is xcb?
============
Do you ever wish you could cut two or more separate pieces of text
at once from a window?  Do you ever need to save the output from one
command for reuse in several subsequent tasks?  Do you ever find
yourself wanting some easy means of globally exporting data, e.g.
to a parent shell, to another xterm or application, or to another
machine or user?  If you answer yes to any of these questions, then
xcb is for you.

Xcb provides access to the 8 cut buffers built into every X server.
It allows the buffers to be manipulated either via the command line,
or with the mouse in a point and click manner.  The buffers can be
used as holding pens to store and retrieve arbitrary data fragments,
so up to 8 different pieces of data can be saved and recalled later.
The program is designed primarily for use with textual data.

What is so good about this release?
===================================
This release provides a few minor bug fixes and enhancements,
and adds full support for non-standard (non-ANSI) C environments.
It should be of most interest to people using non-ANSI C compilers
or C libraries, e.g. SunOS users.  See the CHANGES file for a
full list of modifications.

Yes, but has it been ported to WHIZ-IX 12.1A.00x, on SRS-80 27-bit CPUs?
========================================================================
Xcb has been ported to a wide variety of sites and systems.
In no particular order, the machines and operating systems known
to be running xcb include:-

	o  OSx (5.1a)  -  Pyramid MIS-2/02
	o  DC/OSx (1.0)  -  Pyramid MIServer-S 1/32 r3000
	o  AT&T SYSV (SVR3.2, SVR4)  -  i386
	o  HP-UX (lots of versions)  -  HP 9000/710,720,730,750
	o  SunOS (4.1)  -  Sun3, Sun4, Solbourne Series5, SPARCstations
	o  SPARC/OS (1.1)
	o  Irix (4.0)  -  SGI
	o  ULTRIX (4.2)  -  DECstations
	o  UNICOS (6.1)  -  Cray Y-MP
	o  ConvexOS (10.0.2)  -  Convex 3100
	o  DYNIX (V3.0.17.10)  -  Sequent Symmetry S81
	o  AIX (?)

Xcb was initially written for pure ANSI C compilers.  It has now been
adapted for both ANSI and non-ANSI compilers.  It is in use in both
X11 R4 and R5 environments.  The current version is built directly 
on top of Xlib, rather than on any toolkit library.

So, it will compile, will it?
=============================
Yes!  The only compile time switch in the source is -DAIXV3.  If you
have an AIX version 3 system, you may need to add this switch
to the Imakefile or Makefile.std.  Also, AT&T SVR4 sites need libnsl.a 
during linking.  If you are using SVR4, and you don't like Imakefiles,
you will need to add -lnsl to the LDFLAGS in Makefile.std.

Ok, where is it available?
==========================
Versions of xcb can be obtained.....

	o  from the comp.sources.x newsgroup, or any of its archive sites.
	o  or by ftp, from export.lcs.mit.edu in the file contrib/xcb-1.1.tar.Z
	o  or by sending me an email message.

What are the coming attractions?
================================
Version 2.0 is already under construction.  Some of the main features
on the list for the next release include:

	o  support for X resource specifications
	o  standard Xt style command line switches 
	o  compatibility with the OpenWindows/XView environment
	o  variable number of cut buffer windows

Who is to blame?  Where do I send complaints?
=============================================
Blame me.  The xcb factory is in the sunny Gold Coast region of
Queensland, Australia.  Don't bother trying to find us - even
the postman has trouble getting here sometimes.

If you ever get around to compiling and installing xcb on your machine,
please tell me.  I am interested in tracking the size of xcb's user base.
I am also interested in bug reports, porting problems, comments,
suggestions, patches, etc. etc.  If typing a mail message seems like
too much bother to you, then just run the "ack" script enclosed.  It
will do all the work for you.

Enjoy.
Farrell McKay (fbm@ptcburp.ptcbu.oz.au)
August 1992