On Thu, Feb 03, 2011 at 04:01:07PM -0800, Jason Gerecke wrote: > On Thu, Feb 3, 2011 at 11:20 AM, Adam Bark <[email protected]> wrote: > > > > I figure the code is 0.10.10 so until it hits 1.x I won't assume > > anything. As for Favux's comment you don't have to update immediately > > it's only just been checked in so won't be in a release for a little while. > > > > Assuming 0.x will have unstable interfaces is great, but I've noticed > some projects retain a vestigal "0." prefix for several years, despite > being mostly stable (VLC is the poster-child for this, taking 13 years > to hit 1.0). I'm new to the list (joined a few days ago) so I don't > really know the project history or roadmap very well, but if the point > releases are any indication of interface stability, then "major > changes" happen about every two years. That's pretty stable, despite > its 0.x status.
linuxwacom has been around since 2002 now. if you count commits, we've had 78 commits to xdrv/ between 2002 and 2009 and 788 to xf86-input-wacom since the fork (figure is a few weeks old). pure lines changed values are similar for both time periods, give or take a few. interface stability is nice, but at the same time not guaranteed at this point because too much of the driver is being refactured. there will be a version 1.0 but at this point I'm not optimistic enough to predict when exactly. > On Thu, Feb 3, 2011 at 1:54 PM, Peter Hutterer <[email protected]> > wrote: > > would something like: > > xsetwacom get <device name> RelWUp > > "RelWUp is obsolete. Please use RelWheelUp instead" > > This seems like the best solution to me. I'm all for making things > more readable, but we shouldn't suddenly pull the carpet out from the > people who have been using the existing xsetwacom interface for > literally years... xsetwacom changed/broke a few times since 2009 already and many interfaces have changed. e.g. changing return value for "get mode" from 0/1 to Relative/Absolute. I had to jump through hoops to support a few old interfaces until I noticed that they are largely there for two reasons: "they've always been there" or for technical reasons that are now either obsolete or were never there to begin with (e.g. wacomcpl/libwacomxi). if something is broken, it should be fixed, even if it causes pain in the short term. Cheers, Peter ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
