Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!orca!mesa.dsd.es.com!rthomson
From: rthomson@mesa.dsd.es.com (Rich Thomson)
Newsgroups: comp.windows.x
Subject: Input Extension Support in Xt Translations
Message-ID: <1991Jan9.201237.24959@dsd.es.com>
Date: 9 Jan 91 20:12:37 GMT
Sender: news@dsd.es.com
Reply-To: rthomson@mesa.dsd.es.com (Rich Thomson)
Organization: Design Systems Division, Evans & Sutherland, SLC, UT
Lines: 26
Originator: rthomson@mesa
Nntp-Posting-Host: 130.187.85.21

Is there any work in progress on supporting the X Input Extension in
the Xt Translation Manager?  Specifically, I'd like to write
applications that didn't have to understand the input extension to
work with extension devices.  I should be able to take a widget and
augment it's translation table with an entry for an extension device
to control an action, i.e.:

    <KNOB_BOX: DeviceMotion>: DrawPixel()

It seems that the only thing needed is to augment the existing String
to Translation converter (and possibly some of the event handling).

This would go a long way towards integrating tablets, dial boxes,
button boxes, etc., into the X environment.  Toolkit literate
applications wouldn't need anything except a recompile (and not even
that if they used shared libraries and dynamic linking) to take
advantage of these input devices.

Any comments?

						-- Rich
-- 
  ``Read my MIPS -- no new VAXes!!'' -- George Bush after sniffing freon
	    Disclaimer: I speak for myself, except as noted.
UUCP: ...!uunet!dsd.es.com!rthomson		Rich Thomson
ARPA: rthomson@dsd.es.com			PEXt Programmer