I did a rough screengrab + mock up of what I'm thinking of to replace the tablet input devices dialog.
http://wiki.inkscape.org/wiki/index.php/Tablet_Dialog
Any suggestions, workflow points, etc?
Jon A. Cruz wrote:
I did a rough screengrab + mock up of what I'm thinking of to replace the tablet input devices dialog.
http://wiki.inkscape.org/wiki/index.php/Tablet_Dialog
Any suggestions, workflow points, etc?
It already looks much better than the current dialog. :) A few questions to start:
* Are the config types (Basic, Inking) going to be hard-coded in, or can I create other configs? * How would I switch to a different active config? * What if I have two or more tablets...would the configuration for the first tablet be copied over to the second by default, or do I need to manually copy my settings over the first time I use the tablet?
Thanks,
John
On Mar 6, 2008, at 3:23 AM, John Bintz wrote:
It already looks much better than the current dialog. :) A few questions to start:
- Are the config types (Basic, Inking) going to be hard-coded in,
or can I create other configs?
The whole point is to have things user-friendly and user-defined. So one can set up many custom configurations.
- How would I switch to a different active config?
However you want to. :-)
There will probably be menu items, or a popup button somewhere, and in the dialog there might be a checkbox on the config's overview pane and also a right-click menu item for "Set as active configuration".
I was also hoping to get some auto-detect switching when appropriate. There could be a config setup for the normal pen, and one set up for the 6D Art pen. Then when you bring one of those to the tablet it can switch config, which will change the behavior of the cursor/puck/ mouse to do what matches your main tool.
Or it could also switched based on hardware config. If you sometimes have two tablets and sometimes have one, you could have configs for both one and two and we can see what's installed when we start the app.
- What if I have two or more tablets...would the configuration for the
first tablet be copied over to the second by default, or do I need to manually copy my settings over the first time I use the tablet?
I was actually expecting that one config would handle one or more tablets. Just the coding part of "or more" opens things up a lot, I think.
Of course for that, we'll need to have feedback from users who have more than one tablet.
On Thu, Mar 6, 2008 at 12:49 PM, Jon A. Cruz wrote:
I did a rough screengrab + mock up of what I'm thinking of to replace the tablet input devices dialog.
http://wiki.inkscape.org/wiki/index.php/Tablet_Dialog
Any suggestions, workflow points, etc?
I'd love to see something in the lines of http://www.alexmac.cc/tablet-apps/
Also, how does one-tablet-several-pens configuration fit your proposal?
Do we want to care about things like http://www.wacom.com/art_pen/index.cfm in a way of providing different presets?
Alexandre
On Mar 6, 2008, at 3:36 AM, Alexandre Prokoudine wrote:
I'd love to see something in the lines of http://www.alexmac.cc/ tablet-apps/
I might be looking at features like that later but...
* it is a bit low-level * it is very specific to an individual manufacturer's product, so is not as generic * it is done by another app that works today
Those are the main factors for me saying "later" or "next version"
Also, how does one-tablet-several-pens configuration fit your proposal?
It should fit very well. For Wacom tablets with tool id it appears that X11 will get configured with separate devices for each pen. Gdk is giving me a list of all devices (mouse, pen, back-of-pen, extra- buttons-on-the-side-of-the-tablet each are the four devices I get with a base Intuos3 setup)
That's actually a lot of why I'm doing this. To get those buttons and sliders on the side of my tablets handled nicely, getting them to appear as a single "tablet" would make management easier.
Do we want to care about things like http://www.wacom.com/art_pen/index.cfm in a way of providing different presets?
Yes. The more feedback we get from people with such devices, the better.
However I'm thinking that once we make config easier, people will start telling us a lot of points they wish to be changed/enhanced.
On Thu, Mar 6, 2008 at 9:02 PM, Jon A. Cruz wrote:
- it is a bit low-level
- it is very specific to an individual manufacturer's product, so is not as
generic
Quoting Alexander Macdonald who wrote this app: "I've written my tablet-apps programs to read the pressure and tilt data using gtk so as long as aiptek devices appear as standard Xinput tablets and work in things like the gimp they should already be supported."
- it is done by another app that works today
Just like Agave ;-), tablets-apps is a UNIX-only app so far.
Alexandre
On Mar 6, 2008, at 10:40 AM, Alexandre Prokoudine wrote:
On Thu, Mar 6, 2008 at 9:02 PM, Jon A. Cruz wrote:
- it is a bit low-level
- it is very specific to an individual manufacturer's product, so
is not as generic
Quoting Alexander Macdonald who wrote this app: "I've written my tablet-apps programs to read the pressure and tilt data using gtk so as long as aiptek devices appear as standard Xinput tablets and work in things like the gimp they should already be supported."
I think there are two things going on.
First is the reading of values. We're using GTK calls also, so it should work everywhere.
Second is the setting of response curves and such. That's where the low-level config and tricks come in. In fact, I believe that to pull that off he uses an external invocation of xsetwacom.
On Fri, Mar 7, 2008 at 5:52 AM, Jon A. Cruz wrote:
Quoting Alexander Macdonald who wrote this app: "I've written my tablet-apps programs to read the pressure and tilt data using gtk so as long as aiptek devices appear as standard Xinput tablets and work in things like the gimp they should already be supported."
I think there are two things going on.
First is the reading of values. We're using GTK calls also, so it should work everywhere.
Second is the setting of response curves and such. That's where the low-level config and tricks come in. In fact, I believe that to pull that off he uses an external invocation of xsetwacom.
Fair enough :)
But while providing generic configuration control, can we make extra configuration possible and pluggable for particular devices so that response curves could be easily added when required at a later stage?
Alexandre
Jon A. Cruz wrote:
On Mar 6, 2008, at 3:36 AM, Alexandre Prokoudine wrote:
I'd love to see something in the lines of http://www.alexmac.cc/tablet-apps/
I might be looking at features like that later but...
- it is a bit low-level
- it is very specific to an individual manufacturer's product, so is
not as generic
- it is done by another app that works today
Those are the main factors for me saying "later" or "next version"
Quick question - will this WM settings/app work with Inkscape, or would Inkscape setting override the applet's settings?
If the latter, then I agree that a similar dialog would be pretty awesome. Maybe you can steal some code?
JF
On Mar 6, 2008, at 1:17 PM, Joshua Facemyer / Impressus Art wrote:
Quick question - will this WM settings/app work with Inkscape, or would Inkscape setting override the applet's settings?
If the latter, then I agree that a similar dialog would be pretty awesome. Maybe you can steal some code?
I believe that the device mode is already covered in GtkInputDialog and is at the higher level that I'll be working at. That also means we'll fight over that setting.
The response curve is low-level driver settings as far as I'm aware of, and is very platform specific. It works on X11, but not on Windows or native OS X. In those latter two cases you'd end up fighting with the commercial drivers and config apps that Wacom ships.
However, if I limit things mainly to the higher level info and items, then it works cross platform.
participants (4)
-
Alexandre Prokoudine -
John Bintz -
Jon A. Cruz -
Joshua Facemyer / Impressus Art