[00:59] Ovenwerks, send me info on dev workflow or docs related on contributions. [01:14] b0id: OvenWerks is mostly focused on Studio Controls, the source for which is at https://github.com/ovenwerks/studio-controls, but I think he's drumming up something new which may or may not be Ubuntu Studio-related. [18:58] b0id[m]: That question confuses me. Like I have missed the first half of the conversation. [18:59] Eickmeyer: which tool kit did you use for uninstaller? [18:59] OvenWerks: kdialog [18:59] And zenity for the progress indicator [19:00] Eickmeyer: I was wondering if it maade sense to combine installer into it. Installer does not deal well with hidpi screens [19:01] but it sounds like it is written in bash? [19:02] I've been considering a rewrite of installer into kdialog or zenity for a while since it really doesn't need that much. Really zenity would be best as it can monitor progress a whole lot better than kdialog. [19:02] Kdialog is just easier for initial dialogs. Right now I'm working on a rewrite for edubuntu. [19:02] Trying to use zenity alone. [19:03] basically, tk/tcl or fltk seem to suffer from not dealling with DE font sizing. [19:04] Either toolkit would be so much better on HighDPI. [19:04] Right, that was part of my initial concern a while back, but we kicked that can down the road. [19:04] Not pyqt? [19:05] PyQt would work, but I know Kdialog because I know Bash scripting best. [19:05] :) [19:06] Also, I'm thinking about GTK desktops, which still outnumber Qt desktops in the Ubuntu flavor world. [19:06] I am assuming you want to stay away from gtk/glade [19:07] Well, studio-controls still uses gtk/glade, right? [19:07] gtk/glade would probably be easiest because we have some experience [19:07] yes [19:08] I think ouyr menueditor was glade as well [19:08] So, I have no problem with that, especially because it still blends with the desktop and works well with non-Qt desktops. [19:09] If we want a starting point the menu editor would be the better of the two. Controls is based on someone elses start and is not really cleaned up [19:09] menu edit was from a frsh start. [19:11] Whatever you think is best if you want to lead the charge on this. [19:12] How's the progress on controls? [19:13] Eickmeyer[m]: I will be working on a songbook like app at some point but I have gotten something working via waydroid for now. [19:13] Cool! [19:15] controls needs work. mostly autojack. I did some work on it but am going to have pull some of it out I think. I was trying to combine pw and jack in the same calls and it looks like I am better to just add a bunch of if pw skip kinds of thing and do pw separate... better for my mental health [19:16] PW has mostly all it's own calls for everything we need anyway. [19:18] At some point I may have to change everything jack to jackd instead of jackdbus unless I start jackdbus manually instead of with dbus calls. When started with dbus calls, jackdbus sometimes uses pw jack libs which is a mess. [19:21] I see. Well, if it's any help, the file/symlink is pipewire-jack.conf in /etc/ld.so.conf.d like you recommended. Without that, pw-jack is disabled. [19:21] that is the same mechanism I am using. [19:23] It is for cases where jack is used as a pw devicde. [19:23] Right, I followed your lead so that we're keeping the same file. [19:24] I'm modifying /usr/sbin/ubuntustudio-pwjack-config so that it can not only set the default buffersize, but also enable/disable which basically deletes or creates that symlink on demand. Obviously it will require a reboot after the ldconfig is run, but it will tell the user. [19:24] gotta run... I'm the driver. [19:26] Ah, have fun. [19:27] When I can, I will push what I have to github so I can pull to this machine. So I can work on it when my wife is home. She prefers my presence in the same room :) [19:27] So does mine. LUL [19:27] Part of the reason we got this machine