rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (01/14/90)
An MIT X Consortium draft standard of the Input Extension is now available for Public Review. This draft standard establishes a mechanism for dealing with additional input devices (beyond a single keyboard and pointer) within the X server. The objective of Public Review is to determine if the current draft is acceptable as a Consortium standard. Public Review can result in changes to the draft standard. Public Review of the Input Extension is scheduled to end April 16, 1990. The X community is encouraged to review the draft and submit comments by electronic mail to input-ext@expo.lcs.mit.edu You may send written comments to Bob Scheifler Laboratory for Computer Science 545 Technology Square Cambridge, MA 02139 Comments sent to other addresses are not guaranteed to be considered. Commentors should take the review process seriously, and should: 1. Identify objectionable wording in the document. 2. Suggest specific alternative wording. and most importantly: 3. Provide a rationale for the suggested change. Commentors should also carefully distinguish between: 1. Problems that they regard as intolerable and that must be corrected before the document becomes a standard. 2. Aspects that they don't like but could live with for a few years until a future revision of the standard. 3. Additional functionality that they can live without in an initial standard but would like to see in a future revision. A Consortium committee will review the comments and respond to commentors. The Input Extension documents (protocol, encoding, and library) are available as part of the X11R4 distribution, in the directory mit/doc/extensions/xinput/, and separately via anonymous ftp to expo.lcs.mit.edu in the directory /pub/DOCS/input/. The documents are also available via the archive server xstuff@expo.lcs.mit.edu, by sending a message with the Subject: line of "send docs input/<itemname>" and an empty message body, where <itemname> is one of: Makefile Format S.aformat TitlePage TitlePage.p protocol.mm encoding.mm library.mm.1 library.mm.2 Some mailers produce mail headers that are unusable for extracting return addresses. If you use such a mailer, you won't get any response. If you happen to know an explicit path, you can include a line like path foo%bar.bitnet@mitvma.mit.edu or path bar!foo!frotz in the body of your message, and the daemon will use it. If you simply cannot obtain the Input Extension from the network, you may request a paper copy by writing to: Michelle Leger Laboratory for Computer Science 545 Technology Square Cambridge, MA 02139