[18:39] <OvenWerks> OK all, there is a new test version of controls available. Lots of stuff in the GUI doesn't work (or at least it doesn't do anything).
[18:40] <OvenWerks> I will probably be removing the presets and tablet tabs before release as I don't see myself getting there.
[19:33] <OvenWerks> I took a look at wacom tablet setup... I am confused :P
[19:35] <OvenWerks> About the only thing I found that _I_ understood, was that it is indeed a /dev/input device, the same as keyboards mice and joysticks (and wiimotes).
[19:35] <OvenWerks> (create a painting by waving a wiimote around in the air)
[19:36] <OvenWerks> krytarik: What I have done so far with -controls is up and a package is available. I have left the whole GUI in for now even though most of it doesn't work.
[19:38] <OvenWerks> krytarik: I have moved the preset/profile box onto a tab, but it does nothing... and will for a while. Audio is working it's way towards working on my system, but not the upload yet. tablets I can't even start on because I don't know where to start. :)
[19:39] <krytarik> OvenWerks: Any chance to drop the previously mentioned excess changelog entry too then? :P  (As well as fix the changelog of -default-settings.)
[19:39] <OvenWerks> but that is ok, because I think the audio page will be a while anyway.
[19:40] <OvenWerks> krytarik: what would you like it to say? Just back to where it was?
[19:40] <OvenWerks> Some one had put a release note in it when it had not been released.
[19:40] <krytarik> Yeah, that was Ross, this time.
[19:41]  * OvenWerks has been running with turbo turned on and the CPU speed changes even more than ondemand ever did.
[19:41] <OvenWerks> ok, will put it back.
[19:43] <krytarik> No, merging the two sections was right - just separate the changes per author then - and drop any excess ones.
[19:43] <OvenWerks> 0.64 UNRELEASED just Ross' last fix
[19:44] <OvenWerks> I will commit as a change log fix, but not in the changelog itself.
[19:44] <krytarik> Like referring to intermediate changes within the same version, or to ones that have even been uncommitted.
[19:45] <krytarik> And particularly when it pertains the changelog itself.
[19:47] <OvenWerks> revision 303 look ok?
[19:51] <krytarik> Yeah - but well, now it's back to a single, last author - so could as well drop Ross' name at the top there.
[19:51] <OvenWerks> krytarik: wrt -controls. I have a tab for basic ubuntustudio setup. This is for those who install our metas rather than our iso. It just completes the process. I am hoping to detect if it needs to be set and have -controls open with the tab active in that case but not normally.
[19:51] <OvenWerks>  :)
[19:52] <OvenWerks> krytarik: would you like another commit?
[19:54] <krytarik> Well, I guess it depends on if there are any changes from anyone more than him foreseeable until the next release.
[19:54] <OvenWerks> I have a tab for system tweaks that is sort of universal with the cpu governor and boost off/on. Theses are now dropdowns with the name of the governor on them and boost of and on.
[19:55] <OvenWerks> Anyway, install -controls and see what it does now and looking at the audio part will show where it is going
[19:55] <krytarik> Otherwise, could also dial back the both last commits completely and force-push it - then it's like before indeed.
[19:56] <krytarik> (And this time autobuild wouldn't fail on that even.)
[20:02] <OvenWerks> krytarik: I am not sure I want to add jackd to the depends.
[20:03] <krytarik> Uh, I'm referring to what we were just talking about, -default-settings.
[20:04] <OvenWerks> ya, i've kind of gone beyond that
[20:06] <krytarik> On -controls, you just need to drop the "* Fix changelog version." entry.
[20:07] <krytarik> Whichever way, before release.
[20:07] <OvenWerks> krytarik: next commit I will fix that
[20:09] <OvenWerks> It is already fixed on my system.
[20:09] <OvenWerks> I will probably add something to -settings too when I get -controls done. SO it will take care of itself.
[20:13] <krytarik> Also, since neither of us is expected to be the uploader too, it's fine like that anyway - and I used to do it that way for my own changes.
[20:13] <OvenWerks> https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild says -settings was successfully built.
[20:25] <OvenWerks> krytarik: FYI, my plan just now for controls is to get the audio tab working and remove the tabs for presets and tablet for this release. I think that may be as far as I get. The best thing would be for me to actually have a tablet and work with it... but the cheapest I can find just now locally is $100... for something I don't really need.
[20:27] <krytarik> Yeah, just read that in the log - just leave that to eylul then! :P
[20:28] <eylul> huh?
[20:28] <eylul> hi Krytarik and OvenWerks
[20:28] <krytarik> Hiii. :D
[20:28] <OvenWerks> o/
[20:28] <eylul> leaving what to me? 
[20:29] <OvenWerks> tablet settings design
[20:29] <krytarik> All the fancy and tablet stuff.
[20:29] <eylul> oh dear god. hahaha. sorry ovenwerks, I didn't expect you to go this fast :D
[20:29] <eylul> (not a bad thing!)
[20:30] <OvenWerks> Audio will take a while I think... or at least be more lines than the whole file so far :P
[20:30] <eylul> heheh
[20:31]  * OvenWerks should be doing the easy parts first...
[20:32] <eylul> in terms of wacom tablet, the main issue is that button setup changes based on every single tablet, based on what version it is and what size it is. (larger tablets have more buttons on them.. or none at all.. in some cases :D)
[20:32] <OvenWerks> eylul: how many people use more than one tablet?
[20:33]  * eylul has an intuos, a cintiq companion and a bamboo. (although she doesn't really use the bamboo)
[20:33] <OvenWerks> eylul: that is, would this be a set once or all the time.
[20:33]  * eylul ducks the incoming object
[20:34] <eylul> its actually pretty common for people to have 2 tablets: one with a screen, another one an intuos/intuos pro it seems
[20:34] <OvenWerks> eylul: have you looked at the /dev/input/directory?
[20:35] <OvenWerks> are there any subdirectories that start with by-*?
[20:35] <eylul> nope?
[20:35] <eylul> I do see a list of items that says "event" 
[20:35] <eylul> by-id    event1   event12  event15  event2  event5  event8  mice    mouse2
[20:35] <eylul> by-path  event10  event13  event16  event3  event6  event9  mouse0  mouse3
[20:35] <eylul> event0   event11  event14  event17  event4  event7  js0     mouse1
[20:35] <OvenWerks> the by-id subdir could be useful
[20:36] <eylul> actually
[20:36] <OvenWerks> by-path should have links that are solid
[20:36] <eylul> we should be using libwacom I think?
[20:37] <OvenWerks> that is the event 6 might point at a different device every time, but the by-path may be able to always point to the save device when it shows up.
[20:37] <eylul> let me check
[20:37] <OvenWerks> probably. I don't know how it works.
[20:38] <eylul> actually
[20:38] <eylul> I think for wacom we might go through by-iD
[20:38] <OvenWerks> At least it has enough info to figure ut which event* is which.
[20:38] <OvenWerks> by-id is easiest, that is what I use for dual keyboards
[20:38] <eylul> actually OvenWerks hang on a sec
[20:39]  * eylul digs through script folder to find the wacom script
[20:41] <eylul> I would expect we would use xsetwacom to set up the wacom
[20:41] <eylul> not go through dev/input
[20:41] <eylul> unless there is a reason for going much lower level. 
[20:41] <eylul> which is entirely possible
[20:42] <eylul> http://linuxwacom.sourceforge.net/wiki/index.php/Xsetwacom
[20:44] <OvenWerks> eylul: the very small amount of stuff I read on it suggested that because the event* changes things could not be setup static. but if the is an automatic way that works that is great.
[20:45] <eylul> I expect we would not be going through events at all
[20:46] <OvenWerks> so the idea is to have a script/device and be able to set that up?
[20:46] <eylul> ok so there are different levels of how we can handle this.. and I think it will take a while to get all the way through with some 
[20:48] <eylul> 1) implement basic wacom settings. there is currently no solutions out there that has a GUI, that can set up a wacom tablet. That is: map keys of the tablet to a bunch of buttons, set pressure curve, and map the area of the tablet to an area of the screen. There is a commandline utility: xsetwacom
[20:48] <eylul> (there is a couple of GUI solutions but one: doesn't QUITE work and requires building it, other sort of rigs gnome wacom settings back into XFCE at the moment
[20:50] <OvenWerks> So existing solutions are DE dependant?
[20:50] <OvenWerks>  :P
[20:50] <eylul> 2) deal with actual button mapping for intuos and cintiq tablets (problem: every single model has different buttons and they are mapped in different ways to the xsetwacom button list. I saw one of the GUI solutions have a database of this, but it deals with it)
[20:50] <eylul> yup, and they still aren't really amazing
[20:51] <OvenWerks> The DEs are broken... there are standards.
[20:51] <eylul> :D
[20:52] <eylul> 3) there is currently NO solution, that allows presets that maps settings by software. (this is a feature that exists when you use the drivers on windows and mac, and is pretty much required feature)
[20:52]  * OvenWerks went through too much with DEs and "standard" menu files
[20:52] <eylul> so.. long story short: this is complicated
[20:52] <eylul> :D
[20:52] <eylul> hahah
[20:53] <OvenWerks> So you want to have both a map editor and a map installer utility.
[20:53] <eylul> we should probably look into the 2 gui options that are out there, before starting to code this thing.. but yeah.. I am not entirely sure if we can fork them.. or we are better off starting from scratch
[20:53] <eylul> eventually
[20:54] <OvenWerks> The map installer/loader would be the easier part.
[20:54] <eylul> yes
[20:54] <OvenWerks> udev should handle that behind the scenes
[20:54] <eylul> how so?
[20:55] <OvenWerks> you plug the tablet in, udev sees it and loads the right map...
[20:55] <eylul> right
[20:55] <eylul> well it already loads something
[20:55] <eylul> but having it run a custom command would be nice
[20:56] <OvenWerks> That is how pulseaudio does things with new audio devices
[20:56] <OvenWerks> (and what we want to do too)
[20:57] <eylul> *nods* essentially
[20:57] <OvenWerks> eylul: what udev runs right now has to be something that is ok to run before login.
[20:57] <eylul> ok
[20:58]  * eylul is trying to get to ubuntu docs
[20:58] <OvenWerks> What we would need to do is to look at what is there at login and run any needed "custom" commands and then get udev to run them for us or at least signal it needs to be done as the user.
[20:59]  * OvenWerks is seeing why you want presets.
[21:00] <eylul> :D
[21:00] <eylul> I already have a document somewhere in the wiki about this
[21:00] <eylul> I am trying to find them
[21:01] <OvenWerks> Getting something to run at session start should be quite easy.
[21:02] <OvenWerks> look for file exists in /dev/inputs/by-id to tell if things are plugged in then run the mapping commands.
[21:03] <OvenWerks> The mapping commands would be the high level ones
[21:03] <OvenWerks> Do those commands have to be removed when the device disappears?
[21:03] <OvenWerks> Can two units run at the smae time?
[21:04] <eylul> https://wiki.ubuntu.com/UbuntuStudio/FeatureDefinitions/WacomScripts
[21:04] <eylul> good question
[21:04] <eylul> *goes to try
[21:04] <OvenWerks> Can you choose from between two or more units that are currently plugged in?
[21:04] <eylul> actually I don't need to try this
[21:04] <eylul> yes
[21:05] <eylul> because when you send a command to xsetwacom, one of the parameters is the device you are setting
[21:05] <eylul> its like having 2 mouses
[21:05] <OvenWerks> so using two at the same time could be confusing.
[21:05] <eylul> I don't think anybody would do it, (unless they accidentally forgot something plugged in) but theorically it is possible
[21:06] <OvenWerks> what I am asking is if it would be worthwhile having something that disables one of them, leaving only one active.
[21:06] <eylul> I don't think it is a problem we need to urgently deal with, although really, its a question of having a drop down of: choose the device you are setting
[21:06] <eylul> I wouldn't bother
[21:06] <OvenWerks> Ok, as happens it s not too hard :)
[21:06] <eylul> I would rather not disable anything
[21:07] <OvenWerks> it is just a matter of setting up something that "grabs" the input so that x can't use it.
[21:08] <eylul> OvenWerks I really am not sure we are supposed to do that
[21:08] <eylul> there is a wacom driver already. 
[21:08] <eylul> and a lot of the low level issues are already handled
[21:09] <eylul> what we need is a gui to interface with it
[21:09] <eylul> so there is something already listening for all tablets, and listing them, and knowing if there is a tablet
[21:10] <OvenWerks> a GUI editor that made a script that it then ran would not be too hard. Editing in real time might be harder.
[21:11] <eylul> I think a gui editor that under the hood creates a script gets a lot of the work done
[21:11] <eylul> after all those of us who use wacom create a script manually
[21:12] <OvenWerks> It would be nice to have one script and a set of config files.
[21:12] <OvenWerks> config=map file maybe?
[21:12] <eylul> there is a script with a lot of hardcoding in the page I linked to you
[21:12] <eylul> *nods*
[21:13] <eylul> that actually makes sense
[21:13] <eylul> eventually we can have preset files