Re: Waltop class?

Here are my two cents on the topic.  If I was designing "Class" field in libwacom from scratch, I'm not sure if I'd bother because it at best an ackward summary of the individual [Features].  If I were asked to convert today's Classes to generic names, it would be something like this:

Tablet PC - ISDV4's and Serial
Monitor with Digitizer - Cintiq's and DTx's
Simple Tablet (no rings or modes and no tool serial #) - Bamboo's
Simple Tablet + Mouse (no rings or modes and no tool serial # even though 2 tools)- Graphires
Complex Tablet with rings and/or Mode settings to change button or ring meanings. - Intuos's

WCLASS_ISDV4 can be used as generic name for "Tablet PC's".  WCLASS_CINTIQ can be used as generic name for "Monitor with Digitizer" (see issue below though).  WCLASS_BAMBOO and WCLASS_GRAPHIRE are both "Simple Tablets" with the later having a MOUSE.  I'm not really sure why we have 3 versions of WCLASS_INTUOS but they are all the "Complex Tablets".

Technically, there are "Simple Monitor's" (the DTx's) and "Complex Monitor's" (the Cintiq's are as complex as Intuos).  So our current classes are unbalanced.

Anyways, we can either re-use those classes in a generic sense or add generic versions.  If adding generic versions, I'm not if sure if 5 or more are even needing.  In [Features] section, BuiltIn tells differences between Tablet PC/Monitor vs Tablets and NumStrips/Ring/etc tell Simple vs. Complex.

Chris