|
From: Peter H. <pet...@wh...> - 2010-01-18 03:30:07
|
On Wed, Jan 13, 2010 at 05:33:03PM -0800, Ping wrote: > On Wed, Jan 13, 2010 at 3:48 PM, Peter Hutterer > <pet...@wh...> wrote: > > So a new package would in one way or another also include upstream > > maintainance. And identifying which tools actually need to go into this repo > > :) wacdump and possibly wacomcpl, not sure about what else. > > > > On that note, Ping, how is wacdump different from evtest? I'm feeling lazy > > today.. > > wacdump is specific for Wacom device and it is an UI, i.e., you see > all data on the same screen. So, it's a bit more end user and Wacom > user friendly. evtest is a general input device and more developer > oriented tool. But, if we consider the effort of maintaining tools > which don't add too much information to the output, I would say we > should just update the relevant webpages to direct users to "evtest" > and "xinput" in the future. > It is possible to improve the evtest output to provide a different output format that's more end-user friendly though the exercise may be futile. there's not a single repository for it so even if you change one version, others will linger around. xinput is a bit easier, so if there's some other output that you consider worth having we can look into adding it to xinput. > I prefer to obsolete wacdump and xidump development for the next > generation of linuxwacom. > > What do you guys think? I'd welcome this choice. Cheers, Peter |