On Thu, Feb 3, 2011 at 1:54 PM, Peter Hutterer <peter.hutte...@who-t.net> wrote: > On Thu, Feb 03, 2011 at 01:10:21PM -0600, Favux ... wrote: >> I for one am not excited by the proposed changes. I just finished >> updating most of the xsetwacom scripts to be xf86-input-wacom >> compatible and going through that again does not appeal. I've had >> enough folks bewildered or complaining about the switch from >> ClickForce to Threshold. >> >> I definitely see the benefit of going to more naturally readable >> names. But the motivation for some changes escape me. Why add a >> whitespace and make for e.g. Button2 become Button 2? Yes it is a >> little more readable but that breaks all stylus button and tablet >> (pad) button scripts. > > this was the one change that wasn't motivated by a UI "improvement" but > rather by a code improvement. xsetwacom carried around 32 structs that were > near identical except for the button number at the end. > I tried to hack around this but ended up putting exceptions into several > places making the code end up worse. This was the simplest and most > straightforward change with the least code obfuscation. > > Mind you, this one was the exception, I think all the others could be argued > that they do improve the interface. > >> However if Peter feels the changes are necessary...ok. While I >> realize it would be a major pain would it be possible for a transition >> period? Say 6 months or even longer. Where both versions would work >> and the transition is documented in 'man xsetwacom'? Yes, crufty >> code, but with a deadline. And say implemented at a point release? > > would something like: > xsetwacom get <device name> RelWUp > "RelWUp is obsolete. Please use RelWheelUp instead" > > be acceptable? A mapping table like this is easy to maintain.
Thank you everyone who shared your thoughts with us. If we don't get more feedbacks before Monday (Greenwich Mean Time ;), this patchset, with the above implementation added for both the "get" and "set" options, will have my "Acked-by". Does this work for you, Peter? Ping ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
