Re: Griffin Powermate evdev setup

2009-04-29 Thread David Hagood
I'd like to ask a more general question about devices which, like the Powermate, don't really fit into either the "Keyboard" or "Pointing device" classes: To what extent *should* X support these devices? Let's examine a ShuttlePro - a jog wheel, a spinner, 15 buttons. It's not really a keyboard,

Re: clarification requested: apparent termination of xrx project due to deletion of lbx from xorg

2009-03-17 Thread david . hagood
> On Tue, Mar 17, 2009 at 4:02 PM, wrote: > 4) javascript code dynamically creates a node (something like this) > < embed type="x-application/embedded-xapp" >params="/usr/bin/xclock" width="100" height="100" /> > >and adds that node to the browser DOM model (location

Re: clarification requested: apparent termination of xrx project due to deletion of lbx from xorg

2009-03-17 Thread david . hagood
> On Tue, Mar 17, 2009 at 1:20 PM, Jim Gettys wrote: > > it's the npapi plugin capability that i want - the ability to plug in > an arbitrary XWindows application into a web browser - not the X > compression. it looks like LBX was utilised in rxr because it was not > just a channel for x-window e

Re: Adding support for a (multi-)touchscreen - where best to add it?

2009-03-16 Thread David Hagood
On Mon, 2009-03-16 at 11:05 +1000, Peter Hutterer wrote: > that's probably because they advertise a button/axis combination that evdev > does interpret correctly, or because they're posting the axis information > wrongly. I had my hands on an HP Touchsmart for a short while and it was > posting x/y

Re: Adding support for a (multi-)touchscreen - where best to add it?

2009-03-13 Thread David Hagood
On Fri, 2009-03-13 at 11:43 +1000, Peter Hutterer wrote: > On Thu, Mar 12, 2009 at 01:40:29PM -0400, Chris Ball wrote: > I agree. getting something sensible in the kernel prevents us from replicating > the "one X driver per device" hilarity. > Once we have that support in the kernel, we can look a

Re: Adding support for a (multi-)touchscreen - where best to add it?

2009-03-12 Thread david . hagood
> That's odd; perhaps they didn't get the right HAL properties added. > The N-Trig (multi) touchscreen on the Dell Latitude XT and HP Touchsmart > TX2 works out of the box for touch with evdev GIT HEAD. (Clicking via > screen taps requires a patch to map BTN_TOUCH to BTN_LEFT, though.) > > - Chri

Re: Adding support for a (multi-)touchscreen - where best to add it?

2009-03-12 Thread david . hagood
> Hi David, > > My intuition is that adding the reporting to the kernel and hooking it > up through the standard evdev driver would be the right way to go; evdev > already has single-touch support working fairly well. Interesting, because the touchpanels I've used were NOT recognized by evdev at a

Adding support for a (multi-)touchscreen - where best to add it?

2009-03-12 Thread david . hagood
I am working with a (somewhat new-ish) touchscreen system which supports Multi-touch reporting, based upon an eGalix controller. Unfortunately, this is NOT currently supported under Linux (when will these vendors wake up to the fact that the embedded world is moving away from Windows(tm)?) I don't