[05:40] <woobydooby> sup, any idea when mir 0.24 will land in 16.10?
[05:40] <duflu> woobydooby: As soon as we have confirmed it doesn't break Unity8 and friends :)
[05:40] <woobydooby> oh, ok :D
[05:42] <duflu> It's a big one too
[05:43] <woobydooby> yeah, i've seen it's in a silo or something
[05:43] <woobydooby> a silo is like a ppa?
[05:43] <woobydooby> if i install 0.24 from the silo and it doesn't work can i revert?
[05:44] <duflu> woobydooby: I believe a silo is just a PPA. You can revert if you have 'ppa-purge' installed
[05:44] <woobydooby> ppa purge or something
[05:44] <woobydooby> great then :D muhahaha
[05:44] <woobydooby> thanks duflu
[05:45] <woobydooby> hm.. btw.. kde conversation worlk okish on mir
[05:45] <duflu> woobydooby: Thank you too. Please add your findings to https://code.launchpad.net/~mir-team/mir/0.24/+merge/300589
[05:45] <woobydooby> there are some problems with the menu and other things but it's usable on unity8 desktop
[05:45] <woobydooby> using it right now
[05:46] <duflu> Unfortunately silos are often bloated beasts with lots of projects changing at the same time. Difficult to narrow down regressions
[05:46] <woobydooby> :( we need to move to snaps
[05:47] <woobydooby> snap refresh mir ))
[05:47] <woobydooby> i've heard snaps cure cancer
[05:47] <woobydooby> but i'm not sure if it's true
[05:52] <duflu> Snaps don't reduce the number of ABI/API breaks in a release necessitating multi-project updates unfortunately
[05:54] <woobydooby> oh i see :> so you also need to update qtmir and unity compositor and stuff along with mir
[05:55] <woobydooby> ok, so looks like 0.24 is in the Mir staging ppa
[05:55] <woobydooby> so.. after update i'll have mir 0.24 but all above will probably break, right? i will not be able to run unity8 desktop
[05:55] <woobydooby> but i'll be able to play with mir in a vt
[05:59] <duflu> I'm not sure actually. Depends which PPA/silo...
[06:00] <duflu> I need to go visit the winter air for a while
[06:01] <woobydooby> hehe
[06:03] <woobydooby> lp  ~mir-team/+archive/ubuntu/staging
[06:14] <woobydooby> dufu can an abstraction layer above mir help with the abi breaks? (not coder here, just thinking), so then.. mir can move much faster, you'll probably also need to update the abrsraction layer with mir but will not break the stuff above
[06:16] <RAOF> Welcome to lp:miral :)
[06:17] <woobydooby> OMG! that's so cool! like totally cool
[06:17] <woobydooby> :P
[06:35] <woobydooby> konverstaion eating 200% cpu, i've seen this with all qt5 apps
[06:36] <woobydooby> back to irssi
[06:41] <woobydooby> kde apps
[11:23] <greyback> alan_g: your MPs are landed in trunk
[11:24] <alan_g> greyback: thanks
[11:24]  * alan_g looks forward to POC Qt compositing landing too
[13:01] <greyback> alan_g: another bump from qtmir: https://code.launchpad.net/~gerboland/miral/qt-bump-to-qtmir-529/+merge/301168
[13:02] <alan_g> greyback: ack. On my list
[13:03] <greyback> alan_g: and I'd like your thoughts on a design matter I'm hitting. Please see https://code.launchpad.net/~gerboland/miral/qt-add-window-model-mir-side/+merge/301074
[13:03] <greyback> just scan for the comments, I try to explain what I'm doing there
[13:12] <alan_g> greyback: what's the question?
[13:13] <greyback> alan_g: for one, I need to duplicate much of the miral::WindowInfo object, so that I can pass it across thread boundaries. I'm making my own copy
[13:14] <greyback> I was considering adding a deep-copy method to WindowInfo
[13:15] <greyback> but size & position are not included in that structure, but in the pointed-to Window
[13:16] <greyback> hence just making my own WindowInfo struct, copying most of miral::WindowInfo into it
[13:16] <alan_g> greyback: miral::WindowInfo::WindowInfo(WindowInfo const& that) :
[13:16] <alan_g>     self{std::make_unique<Self>(*that.self)}
[13:16] <alan_g> That's a deep copy
[13:16] <greyback> ah. I missed that
[13:18] <greyback> ok, I just need to see about window size & position
[13:18] <alan_g> It doesn't deep copy the Window properties
[13:18] <greyback> yeah
[13:24]  * alan_g has an ambition to remove the member functions from Window, but hasn't achieved that yet
[13:28] <greyback> oh good to know