1xtrap(1) General Commands Manual xtrap(1)
2
6 xtrapreset, xtrapinfo, xtrapstats, xtrapout, xtrapin, xtrapchar, xtrap‐
7 proto - XTrap sample clients
8
10 xtrapreset [ -d[isplay] display ]
11 xtrapinfo [ -d[isplay] display ]
13 xtrapstats [ -d[isplay] display ]
15 xtrapout [ -f script ] [ -e ] [ -d[isplay] display ] [ -v ]
17 xtrapin [ -f script ] [ -d[isplay] display ]
19 xtrapchar [ -v ] [ -d[isplay] display ]
21 xtrapproto [ -d[isplay] display ]
23
25 These commands are SAMPLE CLIENTS provided with the XTrap X Server
26 Extension Sources, Version 3.3. XTrap is an X Server extension which
27 facilitates the capturing of server protocol and synthesizing core
28 input events. Information on how to obtain these sources can be found
29 in the SOURCES section below.
30 The xtrapreset command is the simplest XTrap client in that it merely
32 performs an XQueryExtension() against XTrap. The name "reset" is his‐
33 torical. The display argument is parsed by the X Toolkit and specifies
34 the display where XTrap is to be loaded; see X(1).
35 xtrapinfo displays general configuration information as a result of an
37 GetAvailable XTrap request to the specified server. It is simply
38 designed to test the request/response mechanism of the XTrap extension
39 and client library as well as display the configuration information
40 that it finds.
41 xtrapstats tests the event and request vectoring of the server exten‐
43 sion by configuring XTrap to collect usage statistics on all core input
44 events and requests. It has a primitive command-line interface for
45 showing the counters, zeroing out the counters, and quitting the pro‐
46 gram.
47 xtrapout tests the output transport from the XTrap extension to the
49 XTrap client library. As an aside, since xtrapout has the capability
50 of "recording" events and requests it receives, xtrapout is ideal for
51 providing input to test xtrapin. Since events are the only concern for
52 the input transport, the -e flag can be specified to indicate that all
53 input events (and only events) should be recorded by xtrapout. script
54 is specified primarily for non-U*IX machines which don't support I/O
55 re-direction easily. The -v flag is used to force recording of all
56 requests and input events.
57 xtrapin is used to test the input transport to the XTrap server exten‐
59 sion. As stated earlier, it's input can be provided by xtrapout using
60 the -e qualifier. While it's primary function is for testing XTrap and
61 serving as an example for XTrap functionality, it can reasonably used
62 as a primitive "playback" client for X sessions.
63 xtrapchar parses ANSI character sequences including application program
65 sequences to synthesize input events to X Window servers using the
66 XTrap server extension. The intent of this program is to serve as a
67 sample implementation for interfacing character-based alternative input
68 sources into X servers (e.g. voice recognition systems). Another
69 application might be "remote keyboards". The -v flag causes the pro‐
70 gram to display XTrap configuration information and echo's characters
71 processed to stdout. If present, this must be the first argument.
72 Note: xtrapchar has only been used with Digital Workstations using the
74 LK201 compatible keyboard. Though reasonable effort was done to main‐
75 tain portability, no claims are made as to the current level of porta‐
76 bility to non-DEC servers for this program.
77 The xtrapproto command is a regression test designed to test the basic
79 XTrap protocol between a client and server. If a given implementation
80 is suspect, the results of this test should be sent to an XTrap imple‐
81 mentor and/or developer.
82
84 -d[isplay] display
85 Specifies the server to record from or playback to; see
86 -e Record only (and all) events. Should be used when creating input
88 for
89 -f script
91 The pathname of the script to be recorded / played back.
92 -v Verbose mode.
94
96 X Toolkit Error: Can't load DEC-XTRAP extension
97 The XTrap X server extension has not been linked into the specified X
99 server.
100
102 Sources have been posted on UseNet systems via anonymous ftp.
103 They are:
104 East Coast (USA): export@lcs.mit.edu:contrib/XTrap_v32*.tar.Z
105 West Coast (USA): gatekeeper@pa.dec.com:X11/contrib/XTrap_v32*.tar.Z
106
109 Digital participated in the X Consortium's xtest working group which
110 chose to evolve XTrap functionality into a new extension for X11/R6
111 known as the RECORD extension (XTrap input synthesis functionality is
112 currently covered by the XTEST extension). It is strongly suggested
113 that users of XTrap technology begin developing against RECORD/XTEST
114 as it is the intention of the X Consortium to drive these two extensions
115 in the standards process for providing the protocol capturing/synthesis
116 functionality. Some members of the xtest working group are actively
117 researching migration issues between XTrap and RECORD. If you'd like
118 to contribute, please participate! Contact your local X Consortium Rep
119 for details on how to be added to the xtest mailing list.
120 If you encounter problems, have questions, etc. with XTrap, please contact
122 via mail, phone, etc. at:
123 Ken Miller
125 miller@zk3.dec.com
126 (VOICE) 603-881-6221
127 (FAX) 603 881-2257
128 or paper mail at:
130 Digital Equipment Corp.
132 Ken Miller @ ZKO3-3/Y25
133 110 Spitbrook Rd.
134 Nashua, NH 03062
135 Naturally email is preferred and will get the fastest response.
137
139 X(1)
140 xtrap(1)