Hi Peter, Chris, Ping, and interested readers,

Thank you everyone.  I've tried to take the comments into account and
come up with an action plan.  It avoids sample scripts set to default.

Again this is just a stop gap until a gui comes along.  And might
result in some usable feed back for the gui.  Given the manpower
shortage I'd prefer all of you working on the driver anyway and not on
a configuration gui.  You've got enough to do already.  Hopefully some
more developers interested in working on the gui will step up shortly.

Also to clarify my sloppy writing, when I was referring to man
xsetwacom I was including 'xsetwacom list parameters' etc. as part of
the "manual".

ACTION PLAN
1)  Delete the two configuration pages.
2)  Consolidate them to one HOW TO page.  Title - Tablet Configuration
?  (Don't really like it, suggestions?)

3)  Introduction on how to use xsetwacom and the man pages.
4)  Show example sections i.e. modular format:
      stylus
      eraser
      cursor
      touch
        1 FG
        2 FG
    using 0.10.11 parameter names.  This would show all valid settings
(eventually) for each input tool.  All set to default with default and
range in the comments.

5)  Separate pad section.  This would contain a sample selection of
various tablet model pads.
6)  What values should be used for the tablet buttons?  Any
suggestions?  Or leave blank?

7)  One sample script using the BambooPT combining some of the above
but using only best guess as to what parameters a user would typically
want to change and the values they might pick.  This would be an
example of how to combine the modules.  And make a point of it
starting with #!/bin/bash.
    Include tips on what parameters to change for known bugs.
    Keep it as standard xsetwacom commands without any BASH optimizations like:
      DEV="Wacom Cintiq 12UX2"
      STYLUS="$DEV stylus"
      PAD="$DEV pad"

      xsetwacom set "$STYLUS" Suppress 4
      xsetwacom set "$STYLUS" RawSample 2
    can always change to them later if desired.

8)  Instructions on how to add the user's script to start up.
9)  Instructions on how to make 'profiles' and place in Launchers.

10)  Should I add instructions on how to make settings permanent, i.e.
static configuration?  Using say a 52-wacom-options.conf in
/etc/X11/xorg.conf.d/ for X server 1.8 and up?  Still can't configure
dependent devices in X server 1.9.  But for e.g. the BambooPT can be
split into Pen and Finger snippets.  Something like:

Section "InputClass"
        Identifier "Wacom class options"
        MatchProduct "Wacom BambooFun 2FG 4x5 Pen"
        MatchDevicePath "/dev/input/event*"
        # Add Options below.
        Option "Area" 0 0 14720 9200
EndSection

Section "InputClass"
        Identifier "Wacom class options"
        MatchProduct "Wacom BambooFun 2FG 4x5 Finger"
        MatchDevicePath "/dev/input/event*"
        # Add Options below.
        Option "Area" 0 0 480 320
EndSection


Would the above be acceptable?

Favux

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to