/srv/irclogs.ubuntu.com/2014/12/16/#xubuntu-devel.txt

bluesabre yes, agreed00:00
ochosi(the only thing we might have to keep in mind is to autoremove lls on the next LTS->LTS upgrade)00:01
bluesabreyeah, no big deal there00:02
ochosiif you wanna hack at xfpm-settings, i00:02
ochosi'd be up for another 30mins00:02
bluesabrewe're running out to the store now00:03
ochosioh right00:03
ochosibad timing00:03
bluesabreI'll get started on it though when I get back00:03
bluesabreput it in a branch so you can hack on it too :D00:03
ochosihm, just a quick question before you run out00:04
bluesabrek00:04
ochosicause i could add the tab to the glade file up front for you00:04
ochosibut then again, how would you wanna make it conditional?00:04
ochosibake it in via a separate builder file?00:04
ochosior just show/hide the tab in the code?00:04
bluesabrewe can selectively hide/show the tab00:04
ochosiright, then i can quickly hack at the ui file and post a diff00:06
ochosithen you have something to start with00:06
bluesabregreat, that would help a lot00:06
ochosii'll leave the gsettings-binds to you00:06
bluesabre:)00:06
ochosinote: this'll be based on xfpm-master00:07
bluesabrebbabl00:07
bluesabreok, thats cool with me00:07
ochosigood, ttyl00:07
ochosi(or actually, !ttyl :))00:07
ochosibluesabre: took a tiny bit longer than 30mins because i re-arranged everything from boxes to a table (cleaner code): http://i.imgur.com/VubvTHB.png00:57
ochosithis just mirrors the light-locker settings UI now00:57
ochosiobviously the security-frame in the system-tab has to be hidden when that tab is shown00:58
ochosi(for the duplicate lock-on-suspend option)00:58
ochosiand you have to create the callbacks and hook them up to gsettings00:58
ochosiand finally you have to fill the combobox for the auto-lock-modes00:58
ochosibut that's it00:58
ochosi(ok, i forgot: the late-locking option needs its own format in order to display seconds instead of minutes)00:59
ochosiexcuse the ridiculously long widget-names, but (1) consistency and (2) avoiding potential conflict with other widgets that might get added to xfpm-settings was the idea behind it01:05
ochosihttp://dpaste.com/301PJNA01:05
ochosithere ya go ^01:05
ochosiand i'm out01:05
ochosinighty all01:06
ochosiUnit193: just so you know, i assigned a mini-workitem to you, since you're now part of -dev ;)01:42
ochosiNoskcaj: btw, i tested bluez5 and found no issues so far. is there anything you're expecting to happen/break?01:43
Noskcajochosi, as long as blueman isn't breaking, we're all good01:59
NoskcajI have nothing to do with bluez5 now, just hoping it will be done soon02:03
Unit193ochosi: Right, though shouldn't do it yet, since xfpm still doesn't have it. :P02:24
brainwashochosi: you've marked the parole bug as invalid despite "Also, it does not matter whether the option to prevent the screen saver is on or off in parole preferences."09:09
brainwashis this problem not a bug in the parole code?09:09
ochosibrainwash: hm right, yeah, there seems to be a different problem, forgot about that one10:07
brainwashochosi: I was about to mark the ubuntu report as invalid also, but I noticed this little detail then10:07
brainwashIt's possible that fixing xdg-screensaver will make changes to the parole code unnecessary though10:09
ochosinah, there is something fishy there10:11
ochosinot sure, we'll have to look at it10:11
ochosiseems like it always prevents the screensaver, independently of the setting10:11
ochosiplus it resets it to default when the setting is off10:11
ochosiso there's definitely a problem here10:11
brainwashI'll take a closer look later, it shouldn't be that hard to fix10:16
ochosiokeydokey, bbl10:16
bluesabreochosi: I started work on xfpm and light-locker packaging last night, will probably get it done today... nothing to commit or upload yet11:02
bluesabreI think we used hoards of boxes because its difficult to nicely position elements otherwise, but we should be able to get by11:02
bluesabreusually a bit more limited with gtk211:08
ochosihey bluesabre 11:10
bluesabrehey ochosi11:10
ochosiwell actually i was using more tables, but hjudt redid it all with boxes because of the potentially long translations and stuff11:10
ochosianyway, for the light-locker tab it's fine to use a table11:10
bluesabreah, gotcha11:10
ochosixfpm packaging? you mean 1.4.2?11:11
bluesabreno, light-locker packaging11:11
bluesabrefor 1.5.111:11
ochosiah ok11:11
bluesabre:)11:11
ochosiah got it now :)11:11
bluesabreshould be pretty painless to plug light-locker in though, I think I can do it tonight11:12
ochosinice11:12
brainwashdo the elementary guys include light-locker into their settings interface?11:13
bluesabrethey will probably write a plug for it11:13
ochosii'll talk to the others about whether we want that patch upstream as well, since it detects light-locker and all11:13
ochosiyeah, they either have been working on it already or are working on it11:13
ochosibut also included in some security/privacy plug i think11:14
brainwashlight-locker-settings will not be maintained anymore?11:14
ochosinope11:14
brainwashok :)11:14
ochosieverybody can change settings via dconf-editor et al now11:14
bluesabreI'll probably do another patch to make lls work11:14
ochosimeh :)11:14
bluesabrenot everybody will use xfpm11:14
ochosii thought we were getting rid of maintenance load here11:14
ochosiyeah true, but then again, gsettings...11:15
bluesabrewe can ask for it to be removed from the archive then11:15
bluesabreI don't want something with our names on it to not work ;)11:15
ochosialso, there was a plan to have a cli switches to change light-locker's settings11:15
ochosibluesabre: well, we can just add a note: "works with light-locker <=1.4"11:16
ochosiimo that's enough11:16
bluesabreright11:16
bluesabrebut it would need to be removed from the archive11:16
ochosior saying "this piece of software is deprecated and only works with..."11:16
bluesabrewhere light-locker 1.5.1 will now reside11:16
ochosiyeah11:16
ochositrue11:16
bluesabreor we can just patch it for the new gsettings (minimal work) and users can enjoy it11:17
ochosii was actually thinking of the launchpad page for some reason11:17
ochosiheh, as you wish11:17
bluesabre:)11:17
ochosias long as you promise that we do this *after* the workitems i added last night11:17
bluesabreofc11:18
bluesabrells is not top priority11:18
ochosi(cause i know you love python and would much rather do that then work on xfpm)11:18
bluesabrebut Unit193, do not drop from the archive until I've uploaded the fixes for lls11:18
bluesabreotherwise will have a fun time trying to sponsor11:18
Unit193Archive being seed? :)11:25
ochosi:)11:25
Unit193bluesabre: I wasn't going to drop until xfpm got the fix, or until the new one was usable that is.  Besides, isn't Lubuntu the "only" other seeder of it?  They have xfpm (though, issues with OnlyShowIn=xfce)11:26
ochosiyeah, i think lubuntu is the only one11:28
ochosiwhat do -studio and myth- do?11:28
Unit193Don't know, but they don't directly seed it.11:28
Unit193Then there is also Debian #745509, but not really your problem.11:29
ubottuDebian bug 745509 in wnpp "RFP: light-locker-settings -- Simple configuration tool for light-locker." [Wishlist,Open] http://bugs.debian.org/74550911:29
Unit193ochosi: xscreensaver.11:31
bluesabrek11:36
bluesabregotta run, bbl11:36
ochosittyl bluesabre 11:36
ochosihmpf, indicator-sound is still a bit borked with gtk3.1411:38
ochosiyay custom widgetry11:39
bluesabreI'll also try to get indicator things added to the seed today, unless you guys want to poke it11:39
bluesabrereally bbl11:40
ochosiUnit193: ^ ?11:40
ochosik :)11:40
Unit193Hmm?11:40
ochosithe indicator things for ubiquity11:42
ochosi(at least i assume that's what bluesabre meant with "indicator things")11:42
ochosihas that commit of yours even been looked at/merged yet?11:42
Unit193I'd presume he means add indicator-{sound,application} to the packageset, because I know of nothing else.  And not that I know of, no.11:46
ochosihave you subscribed xnox to it yet?11:55
Unit193I may not have, yeah.11:57
ochosibluesabre: please don't forget to actually approve the MR: https://code.launchpad.net/~unit193/ubiquity/xfwm4-panel/+merge/24443712:11
Unit193Into Ubiquity itself? :)12:12
ochosiwell you asked for his review12:13
ochosinot sure xnox will approve if there's another MR-review pending12:13
=== meetingology` is now known as meetingology
=== Noskcaj_ is now known as Noskcaj
=== davmor2_ is now known as davmor2
=== genii is now known as ChristmasPresent
=== ChristmasPresent is now known as genii
=== holstein_ is now known as holstein
ochosiknome: thanks for replying to Ridell, i thought we don't have to actively opt-out of a1 (otherwise i'd have sent an email to -release earlier already)18:06
=== genii is now known as ChristmasPresent
=== ChristmasPresent is now known as genii
=== genii is now known as ChristmasPresent
=== ChristmasPresent is now known as genii
elfyochosi: we might not need to actively optout - but I got asked (same time as knome) so it's only polite to reply :)18:27
knomeochosi, what elfy said :)21:13
bluesabreochosi, Unit193: if there are panel indicator things, then yes23:52
ochosioh hey bluesabre 23:53
bluesabreotherwise, I was talking about libindicator et23:53
ochosioh, the python thingy for bluetooth?23:53
bluesabreyeah, that one23:54
bluesabrebut I can get to that tonight now that I am home23:54
ochosicool23:57

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!