=== Unit193 changed the topic of #xubuntu-devel to: Xubuntu Development | Support at #xubuntu | https://dev.xubuntu.org/ | Release Schedule: https://ubottu.com/y/bb | Daily testing with results: http://iso.qa.ubuntu.com/
=== el is now known as elky
=== elky is now known as el
[10:13] <bluesabre> The next daily builds of xfce4-settings should finally work again
[10:14] <bluesabre> Wasn't paying attention, broke when libgarcon-2- became libgarcon-gtk3-
[16:21] <pleia2> knome: thank you
=== el is now known as elky
=== elky is now known as el
[21:44] <ochosi> bluesabre, Unit193: what would be really nice is if we could start the 18.04 cycle by switching to sn-plugin and pa-plugin from the start so we have some time to figure out quirks so that we can decide to revert before the release if necessary
[21:45] <bluesabre> ochosi: I fully agree
[21:45] <ochosi> hopefully ninetls will do another release soonish
[21:45] <ninetls> I will
[21:46] <ochosi> and then we should consider some of the other gtk3 components
[21:47] <ochosi> or: gtk3/gdbus
[21:47] <ochosi> xfconf would be a candidate to consider
[21:47] <ochosi> also tumbler
[21:47] <ochosi> if we switch some of these components to 4.13 it could make development/porting easier for ppl
[21:48] <bluesabre> ochosi: will you be around tomorrow evening (this time)?
[21:48] <ochosi> good question, i can certainly try
[21:48] <bluesabre> flocculant and I are planning to meet
[21:48] <ochosi> ok
[21:48] <ochosi> for an 18.04 brainstorming?
[21:48] <bluesabre> It might be good to have a development meeting to kick it all off
[21:48] <bluesabre> Yeah
[21:48] <ochosi> makes sense
[21:49] <bluesabre> Unit193: it'd be cool if you could join in too :)
[21:49]  * ochosi wouldn't mind re-trying video-chat again at some point
[21:49] <ochosi> anyway, let's try tomorrow then
[21:49] <bluesabre> Awesome
[21:49] <ochosi> you could send out a reminder email with the exact time
[21:49] <ochosi> maybe more ppl wanna join
[21:49] <bluesabre> I'm going to get the PPAs updated tonight/tomorrow morning, will go ahead and make it formal meeting for 11 minutes from now tomorrow
[21:50] <ochosi> sounds good
[21:50] <ochosi> yeah, we also need a plan for what to put in the staging PPA
[21:51] <ochosi> ninetls: if you wanna join too that'd be welcome!
[21:51] <bluesabre> Yeah, that was the main discussion we were planning to have
[21:51] <bluesabre> I'll go ahead and put together a loose agenda as well
[21:51] <ochosi> great
[21:53] <ninetls> ochosi: but I'm using arch :D
[21:53] <ochosi> hrmm, i think i really should do an xfpm release again soon... tons of translations and several fixes by eric
[21:53] <ochosi> ninetls: that's your problem! ;)
[21:53] <ochosi> anyway, gotta get some sleep
[21:53] <ochosi> night all!
[21:53] <ninetls> NO ARCH BEST DISTRO YOU DONT UNDERSTAND!!11
[21:54] <ninetls> oh, I'm in irc, not on reddit
[21:54] <bluesabre> :D
[21:54] <bluesabre> nighty ochosi
[21:54] <ninetls> ochosi: night!
[21:54] <bluesabre> ninetls, you can just toss our changes into AUR and profit ;)
[21:57] <ninetls> bluesabre: what changes? I'm not too closely read this chat
[22:04] <ninetls> bluesabre: also, since you still here, I have small question about gtk :>
[22:05] <ninetls> how can I check whether gtkcontainer has any children? I can use gtk_container_forall and pass boolean pointer to it
[22:05] <ninetls> maybe there is something better?
[22:07] <ninetls> I didn't found anything simple like "gtk_container_is_empty" or "gtk_container_has_children"
[23:21] <bluesabre> ninetls: g_list_length (gtk_container_get_children (container)) == 0;
[23:21] <bluesabre> bbl