From: Ping C. <pin...@gm...> - 2010-02-04 17:44:45
|
On Wed, Feb 3, 2010 at 10:22 PM, Favux ... <fav...@gm...> wrote: > On Wed, Feb 3, 2010 at 12:13 PM, Jim Henderson <hen...@gm...> wrote: >> There was some later discussion about needing >> to make the configuration easier to use and manage, and that work was in >> progress the last I heard. > > I think that would be much appreciated. I haven't heard of anyone > working on adding it wacomcpl since October or so. No one is working on it as far as I know. Nick, the author of the code, has not promised anything. His last post to the tracker was Dec. 19: http://sourceforge.net/tracker/?func=detail&aid=2878608&group_id=69596&atid=525126 His last email to the list was: ------------------------------------------ On Thu, Oct 29, 2009 at 9:31 PM, Nick Hirsch <nic...@gm...> wrote: > Yeah, I agree. My scripts were solely to demo the kernel code. I'd imagine > that a more robust method would be to use libpng and do everything in C/C++, > thus removing the dependency on Python. I tried that from the beginning but > found it faster to hack things together with Python. I can't make any > promises (I'm booked for a while), but if nobody else is up to it, I'll > probably eventually move this code into xsetwacom and wacomcpl. ------------------------------------------- So, Nick's code is only in the kernel. We need something in the X driver to initialize the images and to enable updating/changing them from the user land, which would be translated into xsetwacom commands. Without the proper X driver support and the corresponding xsetwacom, the current code is pretty much useless for end users. I merged the patch into linuxwacom since I felt the pressure. I was also hoping the code would draw a potential developer's attention and would bring us luck :). I don't plan to commit the patch to kernel.org until we have a solution that works for most end users. > Hopefully someone has or will pick it up. I can not promise anything since I am fullly booked for the next 6 months. Ping |