[01:54] didrocks, we got a release! awesome man, thanks! [01:57] Saviq: yw ;) [01:57] you should go to bed as well! [01:57] Saviq: you missed some fun though [01:57] like launchpad ppa not uploading the binary package [01:57] (beeing in some kind of freeze to add arm64…) === salem_ is now known as _salem [05:58] bregma: https://bugs.launchpad.net/unity/+bug/1223671 seeing FTBFS now that cu2d starts to be about operational again [05:58] Launchpad bug 1223671 in Unity "Unity FTBFS week 37, failing tests" [Critical,New] === duflu_ is now known as duflu [06:29] veebers: hii [06:58] lol... I like how Saviq puts "Needs Information" comments on his own merge requests [08:48] greyback: good morning [08:49] mzanetti: hye [08:49] greyback: I messed up with the review (once again) :D [08:49] app.desktopFile doesn't exist any more [08:49] I'll fix it [08:49] mzanetti: oh dear [08:50] greyback: but I guess now it's the time to switch to the real model stuff anyways [08:50] greyback: also, I need to align the items in the launcher to the dash. [08:51] greyback: is it true that as long as an app is contained in the appmanager model, it's shown in the dash too? [08:51] mzanetti: yes [08:51] so basically I just display everything in there [08:51] ok. /me is on it [08:52] ack [08:56] mzanetti, :PPP [08:56] Saviq: ? [08:56] mzanetti, "Needs information" [08:56] haha [08:58] Saviq: yesterday evening, after flashing my device with -b it took like half an hour to compile unity and it went really hot... [08:59] Saviq: so I decided to give cross compiling a go. But seems I'm hitting a bug in Qt's cmake files. Do you know anything about it? [08:59] mzanetti, oh yes! [09:00] Saviq: I thought we could quite easily set this up... just extracting a pbuilder tarball in /opt. I've prepared a toolchain.cmake file already... so run_on_device could quite easily be changed to cross-compile, given we manage to get around that bug [09:01] mzanetti, there's people working no this [09:01] mzanetti, you' [09:01] ve got mail [09:04] Saviq: hmm... my approach would have been to go with just an armhf chroot for the build root and using the cross gcc from the host system. [09:04] Saviq: from what I understand in that mail they want to do it for real in the desktop system by supporting all multiarch stuff in there [09:04] Saviq: which might be quite nice for us. But might be an additional issue when trying to get this stuff running on e.g. windows [09:04] or other distros [09:05] mzanetti, well, yeah, it's a more complete solution, where you can easily build a package etc. [09:05] Saviq: you can do that in the chroot too [09:06] mzanetti, I know, that's what's happening there, although a more "proper" way maybe - obviously the net result would be to be able to cross-build in buildd / PPAs [09:06] mzanetti, either way, it worked for me after having tweaked some things [09:07] Saviq: so you patched the Qt cmake files to actually regard CMAKE_PREFIX_PATH? [09:08] mzanetti, https://code.launchpad.net/~unity-team/unity8/cross-building/+merge/179248 shows what I changed in unity8's code, and an email from me in that thread describes what else needed to happen [09:09] mzanetti, the MultiArchCross.cmake fixes are in distro [09:09] cool... I'll give it a try in some lazy evening [09:09] mzanetti, I had to hardcode CMAKE_INSTALL_LIBDIR [09:37] greyback: hi! [09:37] greyback: I see yesterday unity8 got published - all was ok? [09:41] sil2100: there are still some branches to go. But yeah getting there [10:10] * greyback back in 40 [10:14] nic-doffay, here? [10:15] Mirv, ping [10:37] Saviq: pong [10:37] Mirv, hey, just wanted to let you know if you want to save time on builders - https://lists.ubuntu.com/archives/ubuntu-devel/2013-June/037380.html [10:38] Mirv, when I built qtdeclarative yesterday, it took some 20 mins on my laptop to just optipng them... [10:38] Saviq: as gerry is away, https://code.launchpad.net/~mzanetti/qtubuntu/register-application-interface/+merge/185010 [10:38] I can only imagine how long that takes on armhf builders... [10:38] Saviq: ah yeah sorry, I noted the link but didn't reply. indeed that export NO_PNG_PKG_MANGLE=1 is worthwhile in some cases. [10:39] optipng is really, really slow [10:39] Mirv, obviously if there's a separate package with assets (that's Architecture: all) the gain is smaller [10:39] for either doing more rapid Qt builds or alternatively permanently for our upstream projects === Guest72454 is now known as karni [10:40] Mirv, but still worth thinking of [10:40] mzanetti, happrovd [10:40] cheers [10:40] Saviq: yes, it could be helpful for the daily release of some packages (or all) === alan_g is now known as alan_g|afk === MacSlow is now known as MacSlow|lunch [10:48] Saviq: btw we shouldn't have panda builds anymore, which is great :) but the optipng takes ages on even high-end x86 in some cases [10:48] Mirv, yeah [10:48] Mirv, that was sent back when we didn't have the calxeda setup yet ;) === alan_g|afk is now known as alan_g [11:01] Saviq: and another one: https://code.launchpad.net/~mzanetti/unity-mir/register-app-interfaces/+merge/185017 [11:02] mzanetti, happroved [11:29] seb128, I forgot so many times... you know that settings app is laid out wrong on maguro? it seems to use a preset width for the items in the grids [11:29] seb128, and they're not horizontal-aligned evenly [11:29] seb128, also, "Language & Te..." is cropped here [11:29] Saviq, no, I don't know about that ... do you have a screenshot? [11:29] seb128, sure, sec [11:30] Saviq, thanks [11:30] Saviq, bonus point if you file a bug (https://bugs.launchpad.net/ubuntu-system-settings/+filebug) and include it [11:34] seb128, bug #1223827 [11:34] bug 1223827 in ubuntu-system-settings (Ubuntu) "Home page misaligned on Galaxy Nexus" [Undecided,New] https://launchpad.net/bugs/1223827 [11:35] seb128, we actually have a ResponsiveGridView for such use cases in unity8 [11:35] seb128, I always thought it could earn its place in the SDK [11:36] Saviq, I wonder what is wrong with the standard grid :/ [11:36] seb128, it's not dynamic [11:36] seb128, you need to set the item width / height manually [11:37] and the item count per row [11:40] Saviq, well we have "columns: width / unitys.gu()" and width: for the elements [11:40] Saviq, it does work/wrap correctly on resize on the desktop [11:40] Saviq, but indeed you have cases where it eats a marging [11:41] seb128, then maybe there's just not enough space so that it misaligns? [11:41] Saviq, right, that logic works fine where the width a multiple of the item width [11:42] is a multiple* [11:44] seb128, yeah, you need to adapt the item width size [11:44] Saviq, you need to fix a variable somewhere... [11:44] seb128, and work with a minimum / maximum [11:45] seb128, sure, have a look at ResponsiveGridView in unity8 [11:45] Saviq, so ranges? [11:45] if resolution is in [..] 4 items [11:45] in [...] 5 items [11:45] etc? [11:45] seb128, not resolution, but width [11:45] then have width_item = width/number [11:45] Saviq, right [11:45] seb128, minimum_width <= item_width < maximum_width [11:46] Saviq, I start really disliking qml btw :p there is so much hackish stuff to do/things the toolkit doesn't do for you [11:46] seb128, and you minimize the number of columns having that condition in mind [11:46] it's fun for nice demos [11:46] but as soon as you need things to behave in a solid way it's piling of hacks [11:46] seb128, lol [11:47] seb128, sure it's not complete (hence our own SDK) [11:47] seb128, did you see 5.1 layouts, though? [11:47] seb128, it's just not complete yet :) [11:47] Saviq, thanks for the hint, I'm going to have a look to ResponsiveGridView [11:47] Saviq, yeah, I saw that, I wish we would be on 5.1 already :p [11:49] Saviq, sorry for the ranting, I just had a very frustrating day yesterday trying to parse simple json to display items in a listview [11:49] Saviq, it's like you need to go to cpp, do manual parsing, do abstract model ... it's all crazyness and too hard for a simple usecase [11:50] where XmlListModel is great, it just doesn't exist for json :/ [11:51] seb128, did you write a JsonListModel, then? ;) [11:51] seb128, http://qt-project.org/wiki/JSONListModel [11:52] Saviq, there is one in https://github.com/kromain/qml-utils/tree/master/JSONListModel I pondered just copying the qml insource [11:52] Saviq, but then I've hundred of lines of code copied from somewhere and virtual unmaintained [11:53] seb128, right [11:54] Saviq, I ended up doing a List and turn that to a QVariant, which works but doesn't give me easy sorting of the model or dynamic update ... Laney is going to turn that into a QAbstractListModel that should do the job, it's just a non trivial api and I tried to go for the easy stuff at first :p [11:55] Saviq, https://code.launchpad.net/~seb128/ubuntu-system-settings/storage-backend-list/+merge/184967 btw if you are curious/ have comments ;-) [11:55] seb128, QAbstractListModel is only scary at first [11:56] seb128, but for general use it's not *that* big of a deal [11:56] Saviq, well, google let me land on http://doc.qt.digia.com/4.7/qdeclarativemodels.html#c-data-models [11:56] Saviq, which recommends the QList before the qabstractmodel, saying to use that one only if the easy case doesn't work [11:57] Saviq, I feel like I got misleaded to spend time on the wrong solution :p [11:57] Saviq, that's part of learning the toolkit though, so no big deal [11:57] seb128, indeed [11:57] Saviq, it just that people try to sell you qt/qml as an easy way to do stuff, but at this end it's as hard with any other toolkit === alan_g is now known as alan_g|lunch [11:57] seb128, sure, the backends need to be there [11:58] seb128, and it obviously depends on the UI you need === MacSlow|lunch is now known as MacSlow [11:58] seb128, in your case there's just more work on the backend than the UI [11:58] right [11:58] seb128, so in that sense it's just as any other indeed [11:58] though my backend need at not crazy ones [11:58] I just need to display a list of items from a json model [11:58] at->are [11:59] anyway, moving on [11:59] seb128, yeah, it's not Python (yet) ;) [11:59] Saviq, thanks for listening to my semi-ranting and still providing constructive hints ;-) [11:59] where there's barely anything you're the first one doing [11:59] Saviq, right, it has potential, as said the xmlmodel magic is awesome [12:00] with python someone somewhere did what you need already in 99% of the cases, with QML we're the ones ploughing through [12:01] seb128, and yeah, well... as soon as you have the second place where you need to parse json... maybe looking at the Json model is not that bad... [12:01] yeah, I was somewhat hopping that more of the heavy lifting would have been done by the other people who have been using it before us [12:01] we might even try to push it into Qt or our SDK at least [12:01] seb128, that's the problem - there really isn't that much use of QML out there still [12:01] seb128, with unity-2d we were one of the biggest projects with it at that time [12:01] right [12:02] maybe not so much nowadays with Blackberrys and such [12:02] which is why I though more would be done [12:02] I though that with the BB and Jolia out there we would have a bit more of the "standard usecase" covered [12:03] but they didn't use it for that long either [12:03] it's going to get there, eventually ;-) [12:03] Saviq, https://bugreports.qt-project.org/browse/QTBUG-12117 btw [12:04] doesn't seem to be actively worked on atm though [12:05] Saviq: just saw this stop by in the debug output: file:///usr/share/gallery-app/rc/qml/Utility/UbuntuApplicationWrapper.qml:19:1: module "Ubuntu.Application" is not installed [12:06] I guess we have a problem :/ [12:06] mzanetti: yep, saw it too. It's on my list [12:06] mzanetti, we renamed to Unity.Application? [12:06] dang [12:07] let's push to fix bug #1186556 then [12:07] bug 1186556 in qtubuntu "Browser does not respond to Qt.openUrlExternally(link)" [Critical,In progress] https://launchpad.net/bugs/1186556 [12:07] so that we can get rid of those completely [12:08] greyback: another issue (not high priority tho) is that the Mocked ApplicationManager doesn't use icon path's but only the appId [12:08] greyback: so right now, running on the desktop breaks icons in the launcher [12:08] mzanetti: ack. Could you log a quick bug for me please? [12:08] ok [12:12] tnx === _salem is now known as salem_ [12:19] mzanetti, you up for a review of https://code.launchpad.net/~saviq/ubuntu/saucy/qtdeclarative-opensource-src/add-qtquick-delegate-range/+merge/184774 ? [12:20] mzanetti, obviously the .patch file does not need a review, as it's applied to the code already === hikiko is now known as hikiko|lunch [12:30] Saviq: I hold off on this, to encourage gallery folks to use Qt.openUrlExternally: https://code.launchpad.net/~gerboland/gallery-app/gallery-app-fix-appman/+merge/185030 [12:31] greyback, thing is... it's not ready yet [12:31] greyback, https://code.launchpad.net/~aacid/platform-api/papi.rules.typo/+merge/182354 [12:31] https://code.launchpad.net/~aacid/qtubuntu/qtubunturl/+merge/181752 [12:31] greyback, and with tvoss away, ricmm on a sprint [12:32] Saviq: ah, I thought it was. Ok [12:32] greyback, won't get done before next week, so let's just fix it [12:32] Saviq: ack [12:32] greyback, thanks [12:35] Saviq: I hoped not having to review this :D === alan_g|lunch is now known as alan_g [12:42] mzanetti, ;D [12:43] mzanetti, why? it's actually pretty small [12:43] mzanetti, but if you refuse, I'll find someone else ;) [12:43] * mzanetti never refuses [12:43] * Saviq notes that down [12:43] haha [12:44] Saviq: ok... I'll try to get that done soonish. [12:44] mzanetti, thanks [13:03] mzanetti: hey how are you doing? [13:03] veebers: dude... isn't it like 3am for you? [13:03] mzanetti: heh, I'm in Boston on a sprint ^_^ [13:04] ah... you're at the sprint [13:04] right [13:04] yeah... doing good now... didn't do so well in our hangout this morning. luckily noone showed up :D [13:05] mzanetti: oh the sync meeting? I thought that I deleted the ones for this week? [13:05] veebers: yes you did... [13:05] veebers: obviously I noticed that after getting up and ready for the hangout :D [13:05] coding till 1:30 am and hangouts at 8:30 am don't go well together [13:05] mzanetti: oh I see now :-P Sorry I should have emailed when I did it] [13:06] veebers: no... really not your fault [13:06] anyways... how is Otto? [13:06] mzanetti: it's annoying me because I almost did send an email but didn't :-P Also, I've deleted the next one on Monday as I get back that day and will probably be in bed [13:07] ack [13:08] mzanetti: ah right so I'll ping fginther about that today (now with the qa/ci split) I talked to him about it yesterday [13:10] greyback: hey...so, i am assuming the pending image has unity-mir landed in it ? [13:11] at least from the scrollback on #ubuntu-touch [13:11] i got on late...but misses asac [13:11] i assume there is a script to switch to mir ? from sf... [13:11] or i should ask...how does one switch ? [13:12] kgunn: I've only landed the last piece there under an hour ago. The next pending image will have it in, for sure. I need to find out when it is generated [13:13] greyback: ah..dang [13:21] greyback, we can always ask to trigger one [13:21] greyback, as there's only going to be one later today [13:22] Saviq: Good to know. When we're ready, we'll have one spun up then [13:23] Saviq: curious...why only one later today ? === hikiko|lunch is now known as hikiko [13:24] kgunn, there's only two images daily [13:24] kgunn, we daily release 4 times a day [13:25] kgunn, but only build an image twice [13:26] Saviq: consider me educated :)....i didn't realize that...thot release lead to image [13:26] realizing now image means release plus load of tests [13:26] and duh...i've only ever seen 2 images a day [13:27] veebers: fyi. we have the biweekly shell hangout now. if you wanna join [13:28] bregma: hello! [13:28] sil2100, howdy!! [13:29] mzanetti: I'm keen, just in a meeting. Can you link me and I'll try pop in [13:29] ack [13:29] bregma: sorry to ping again with bad news, but it seems unity FTBFS for amd64 and i386 because of failing unit tests [13:29] bregma: https://launchpadlibrarian.net/149963225/buildlog_ubuntu-saucy-amd64.unity_7.1.0%2B13.10.20130911.2-0ubuntu1_FAILEDTOBUILD.txt.gz [13:30] sil2100, https://bugs.launchpad.net/unity/+bug/1223561 [13:30] Launchpad bug 1223561 in Unity "Some TestLauncherEntryRemote unit tests are failing with new libdbusmenu changes" [Undecided,Confirmed] [13:30] Right! How can we get this fixed? [13:31] we have to figure out a way to rewrite the tests so it works with the new libdbusmenu [13:31] it's always a problem when folks justthrow their changes over the fence and run [13:32] heh, right [13:32] uh oh [13:33] I broke hangout :D [13:33] mzanetti, can you drop out and back in, otherwise it won't let me in :D [13:33] lol [13:33] "You can't join this hangout because you blocked one of the users. You can make a new one instead." [13:33] d'oh [13:54] mzanetti, well, it's a change to how the right edge behaves [13:54] mzanetti, as now you just pull a single app in in one gesture [13:55] Saviq: in that prototype I can't see any difference to that really [13:55] mzanetti, the first one was broken [13:55] Saviq: might be because mouse handling is somewhat broken tho [13:55] mzanetti, lp:~willow-team/willow/RightEdgeNavigation [13:55] ah. was the second link any different? [13:55] yes, no "Phone" [13:55] ah... [13:56] wow [13:56] looks amazing [13:56] no clue how usable it will be... but it looks good :D === dandrader is now known as dandrader|afk [14:16] mzanetti: do you know: what listens for a bottom edge swipe to show the application toolbar? [14:16] mzanetti: I thought it used to be the bottomBarVisibilityCommunicatorShell [14:16] greyback: it's the toolbar itself [14:16] greyback: wait [14:16] greyback: you talking about apps? or the black one in the shell? [14:17] mzanetti: I open a web browser, the toolbar hides. I want to show that toolbar again [14:17] greyback: yeah... it's the Panel itself... it creates a 2 gu area at the bottom [14:18] greyback: timp might be able to provide details === dandrader|afk is now known as dandrader === alan_g is now known as alan_g|tea === 3JTAAEL6B is now known as tvoss === jono is now known as Guest91193 [14:54] hey tedg [14:54] Howdy Cimi [15:00] mzanetti, Saviq: you have a moment? I'm having issues running a test script using qmlscene when unity8 is using mocks. [15:00] sure [15:01] I have a desktop file and I'm using the desktop_file_hint. It works when I run the command [1] under a `start unity8` session, but when I export the mock paths etc. (i.e. what the autopilot tests do) I don't see the application pop up [15:01] does that sounds weird to you? === alan_g|tea is now known as alan_g [15:01] veebers, on the device? [15:02] Saviq: yes [15:02] veebers, or regardless - yeah, we're still using mocked applications [15:02] veebers, i.e. placeholder images [15:02] Saviq: oh right, does that mean that I can't run an actual application while under those conditions? [15:02] veebers, obviously we need to move away from that [15:03] veebers, yes, if unity8 is using the Unity.Application mock [15:03] well... we need to keep that in the mock [15:03] but autopilot is NOT supposed to use the mock [15:03] yeah, ultimately it should not [15:03] but we just never got around to switching to the real backend for it [15:04] mzanetti: oh, so are the autopilot tests doing something wrong then? (with the exports for QML2_import_path and ld_library_path) [15:04] yes [15:04] mzanetti: rats, right so I need to figure out what it should actually be doing [15:04] veebers: well... for the lightdm stuff we don't have the real thing in place yet. so that's why we introduce the mocks to be able to start writing tests [15:04] veebers: but the mocks are supposed to be used for unit tests (qmltestrunner) [15:05] veebers: autopilot supposed to do integration tests => test the real thing [15:05] tedg, hay, was wondering if there was some update on the wifi plugin [15:05] mzanetti: aye, correct. I guess stuff was pulled over with the revamp of the autopilot suite [15:05] mzanetti: http://pastebin.ubuntu.com/6092858/ [15:06] yep [15:06] Cimi, Uhm, nothing really news worthy. Working on it right now infact :-) [15:06] that is in effect what we're doing [15:06] mzanetti: so is any of that needed? [15:06] veebers: so in the mid-term that should go away for autopilot [15:06] tedg, good [15:06] Cimi, Connecting models to delegates to factories to.... and wondering when this gets easy :-) [15:06] tedg, second question, dednick as well… I did some work on system components, to become indicators. It's missing backends [15:06] mzanetti: alright, so no env exports needed then? or do we still need the lightDM stuff? [15:07] veebers: the qml2_import_path should not be there... for the others you'd need ask mterry on the current state and plans [15:07] (date time, users, media player etc etc...) [15:07] what do we do for them? [15:07] mzanetti: awesome will do. Thanks [15:07] Cimi, ? I'm confused. You did the QML widgets? [15:07] veebers: I'm not entirely sure how to autopilot the real thing with lightdm... [15:07] veebers: so that might stay an exception (altough I'd prefer not) [15:07] Cimi, My guess would be that you need to put them in dednick's MenuItemFactory class to instantiate them. [15:08] tedg, https://code.launchpad.net/ubuntu-settings-components [15:08] mzanetti, veebers: I think I 'm missing something in the scrollback due to disconnects. What's up? [15:08] mzanetti: ack. thanks [15:08] mterry: the fact that our autopilot tests use mocks is bad [15:08] mterry: and we should steer away from it instead of using more of them [15:08] Cimi, Yeah, so they need to get used by dednick's code in Unity8, no? [15:09] mterry: so the question is what the plans are in regard to autopilot the real thing with lightdm [15:09] Cimi, By backend you mean plugged into Unity8 [15:09] mterry: which I agree can be somewhere between extremely tricky and impossible [15:09] mzanetti, I always figured lightdm was a reasonable thing to mock, because we don't want to set up machines with real accounts that we'd need, eh? [15:09] mterry: actually we should... in theory [15:10] tedg, yep I think [15:10] mzanetti, is our QA machinery even remotely able to? [15:10] Cimi: components for indicators? [15:10] veebers: ^ [15:10] dednick, yes [15:10] they need to go in the Indicators.MenuItemFactory to be instantiated by the backends [15:11] Cimi: it has a string to component mapping [15:11] mterry: there's not muck point of integration tests when mocking the integrational parts :) when just testing the greeter code itsel, qmltests would be way better [15:11] mterry: that's the main thing behind the discussion [15:11] mzanetti, mterry thats a good question [15:11] dednick, are you planning to come to the office in next days? would be better to chat live [15:11] mzanetti, well... you can still test other bits :) [15:11] dednick, Is it possible we could put that factory in the library as well? I've copied it for system settings, but it seems like it'd be better to include. [15:11] Cimi: didnt have any plans to [15:12] mzanetti, I think we tend towards qmltests for the greeter itself [15:12] but as I said... I have no clue yet how to autopilot something with logging out the user [15:12] mzanetti, mterry are we able to setup the accounts stuff programatically? [15:12] mzanetti, we need a robot arm driving the machine :) [15:12] ^_^ [15:12] don't we have students? [15:12] tedg: mmm. it's very unitymenumodel speficific in the factory. [15:12] veebers, uh, I mean, I could probably write a script to do so... I just don't know if we have capabilities to run such things sensibly with our QA setup [15:13] dednick, Sure, but do we expect anyone to use System Components without Unity Menu Model? [15:14] tedg: not all the setttings have indicator backends [15:15] dednick, The good ones do ;-) [15:15] dednick, But what I'm saying is that they're still going to be pulling in that lib, they'd just not use the factory in that case. [15:15] tedg: ;) i guess the plugins for settings which use indicators will use the same thing [15:15] dednick, So we're not adding a dependency or anything they don't already have. [15:15] tedg: yeah i guess so [15:16] Cimi: i was working on getting the ubuntu-settings-components package into a workable form so I could put all the indicator items in there. [15:16] dednick, great, can I help? [15:17] mterry: well we can incorporate it into the autopilot tests itself. What specific capabilities are you concerned about? [15:17] i.e. what capabilities are there (that I'm not aware of) [15:18] Cimi: i've been pulled onto something else in the intrim, and it's not really in a fully working form yet. Are you wanting to do this immediately? [15:18] mzanetti, veebers but the fact that we *are* using the application mock is on purpose [15:18] mzanetti, veebers as no one looked yet at moving away from it [15:18] dednick, it was one of my tasks so I am happy to help [15:18] i.e. making sure that no apps are left running when you exit etc. [15:19] as AFAIK there's no way for autopilot on touch to handle that [15:19] Cimi: ok, well i'll try get it into shape quickly and you can take over my branch maybe? [15:19] Saviq: understood. Perhaps for the specific tests I'm looking at I can do something different with the mocks (or perhaps this isn't the best place for the tests) [15:19] dednick, yes [15:20] Saviq: if you launch the app through autopilot it ensures that apps are killed at test end, but not if you 'click' on an application to launch it [15:20] Cimi: ok, give me 30 minutes or so. [15:20] dednick, no problem [15:20] veebers, I believe the blocker for us to move away from the application mock is autopilot's ability to kill the processes on touch [15:20] veebers, yeah, exactly [15:20] veebers, AFAIK there was some work towards that, but not completed yet [15:20] or waiting for the new app manager under Mir, at least [15:21] I *think* [15:21] veebers, but obviously thomi knows more [15:22] Saviq: ack, right I'll touch base with him and see further. At this point I might see about changing the mocks for this test specifically. Thanks [15:22] veebers, yeah, that might work, too [15:32] Saviq: greyback: https://code.launchpad.net/~mzanetti/unity-api/launcher-and-appmanager/+merge/185085 [15:33] mzanetti, 107 + /// @cond [15:33] 108 + void applicationManagerChanged(); [15:33] 109 + /// @cond [15:33] mzanetti, should be @endcond? [15:33] Saviq: yes [15:34] mzanetti, hmm, didn't we establish this morning that this won't work? [15:34] mzanetti, i.e. we need a common library with ApplicationManagerInterface for this to work? [15:34] Saviq: it works for the mock in this case [15:35] Saviq: as it doesn't really load the real appmanager plugin [15:35] but compiles the application mock itself [15:35] mzanetti, yeah [15:35] Saviq: won't register this in the real launcherplugin ofc [15:35] mzanetti, yeah, but that essentially means that we need the common library *now* [15:36] mzanetti, for Unity.Application and Unity.Launcher to work together [15:36] mzanetti, as we need to pass the ApplicationManager from Unity.Application to Unity.Launcher [15:36] Saviq: no... we don't really *need* it now. but it would be cleaner, yes [15:36] yeah it would be cleaner [15:36] Saviq: it works for now if the application plugin registers stuff [15:37] mzanetti, even if both plugins compile their own copy of ApplicationManagerInterface? [15:37] pstolowski, pls https://code.launchpad.net/~mhr3/unity-scope-home/fix-1223940/+merge/185088 [15:37] interesting... [15:37] eh, wrong channel [15:37] Saviq: yes... seems to do [15:37] Saviq: that's why I was a bit surprised that it didn't work when registering the type in main.cpp [15:38] I would have expected that to work [15:38] mzanetti, btw, I asked thostr to invite you to a dash preview-related mtg tomorrow, I'll try to be there, but if not, you have my "power and trust" as thostr called it [15:38] ack [15:38]