In message <[EMAIL PROTECTED]> Jim Gettys writes:
: So what you are saying is that something like xscribble becomes central
: to input in general on handheld devices: it takes relatively raw input
: and then tells X what to do when it needs to.  Building it into the
: core X server seems wrong to me: by definition, we won't get it right:
: I think we should regard it as though it were a window manager: a separate
: application providing some of the UI.
: 
: The issue I see is how to arbitrate among more than one application that
: might want/need the high resolution digitizer device...  We'll certainly
: be running something like scribble continuously, but other apps may need
: more than what the X core protocol gives them.  If the Xinput stuff can
: adaquately handle this situation (other applications in addition to
: the scribble app), then we have a rational course of action.
: 
: I guess it is time to go look at the Input extension and see if it can 
: deal with digitizers adequately in the general case and whether it has 
: any grab/replay notion.  My book is at home, I'll try to remember to get 
: a copy and stare at it some tomorrow.

For what is worth....

I have a program that will read the newton keyboard input stream and
feed it to the X server via the XInput extention.  It deals well with
all key events that I throw at it, as well as dealing fairly well with
the kludge mouse events that I had in it for a while (I ripped them
out because I could more easily do mouselike things with the keyboard
via window manager mappings, etc).  This stuff is much lower
resolution than the digitizer input that you're talking about, but it
does show that at least investigation down this path might be
warranted.

This works well.  It certaily is entertaining to have two different
keyboards that both do the right thing.  I'm even able to use the
serial keyboard on machine X to control the X server on machine Y.  It
is very flexible, at least for keyboard input.

I'd imagine that scribble would recognize the drawn letters and conver
them to key press key release events.  I'd also imagine that a virtual
keyboard would do the same sort of thing.

Warner

unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++        Please use [EMAIL PROTECTED] for           ++
++                        kernel-related discussions.                      ++

Reply via email to