[00:34] anybody else missing their message indicator? === duflu_ is now known as duflu === tvoss_ is now known as tvos === tvos is now known as tvoss [06:48] mhall119, yeah, not here for me either === tvoss is now known as tvoss_test === tvoss_test is now known as tvoss [08:21] mzanetti, hey, so there's one more possibility of going about the "I need to call a method on the object" - which is proxying the call through the model - I wonder if that would be cleaner [08:22] mzanetti, i.e. Class::myMethod() would be proxied through ClassModel::myMethod(int index) [08:22] mzanetti, but then there's proxies [08:23] mzanetti, so as soon as you proxy a model, fail unless you expose the object in the model itself [08:24] Saviq: yeah. that's what I do with the Launcher [08:24] Saviq: that's only an option for a limited amount of methods [08:24] Saviq: and also not an option for the "passing items outside the scope of the model roles" thing [08:24] mzanetti, right [08:25] mzanetti, ok, so let's see if Q_DECLARE_TYPE helps, in which case I'm opting for exposing the objects through the model [08:26] Saviq: setting up an example now [08:26] mzanetti, thanks [08:37] Saviq, any more thoughts as to why the label changes in your comments on the option selector review? [08:38] nic-doffay, If I'd have to guess, it's because the divider is enabled/disabled [08:38] nic-doffay, when you expand / collapse [08:45] Saviq: hmpf... can't reproduce the issue :D [08:45] mzanetti, lol :P [08:46] Saviq: do you know of a place where we had it? [08:47] Saviq: here's the example code... lp:~mzanetti/+junk/model-get-test [08:52] Saviq: ok... if I use qmlRegisterType on the Item and import the uri for that, everything seems to work. If I don't do that, I get this kind of messages: TypeError: Object QVariant(FooItem*) has no method 'value' [08:52] Saviq: but I can't believe this was the issue. I'm sure we did the qmlRegisterType [08:52] mzanetti, no, I never saw that issue ;) [08:53] mzanetti, our issue was that moc didn't know namespaces [08:53] mzanetti, in the Launcher API [08:53] mzanetti, so you had to make the return type explicit [08:53] hm... that was another issue. Don't think its related to this. but I can try [08:54] mzanetti, I don't remember having the "QVariant clash" issue [08:55] Saviq: I remember that MacSlow ran into it with the notifications [08:56] Saviq, mzanetti: can't recall the solution/workaround atm [08:57] MacSlow: well, we know the solution. We're just not able to reproduce the issue :D [08:57] ;) [08:57] mzanetti, Saviq: it could be worse :) [08:58] one would think so, yes [08:58] not entirely sure about it in this particular case [09:02] MacSlow: where can I find the code for the notifications backend? [09:02] mzanetti, bzr branch lp:unity-notifications [09:11] Saviq: pushed some more code to that junk repo. should be able to rest every use case with that. However, I really can't recall any more what exactly was the usecase where returning the pointer wrapped in a QVariant didn't do. [09:11] but I'm 100% positive that there is an issue somewhere [09:12] mzanetti, thanks [09:20] dednick: did you get started on the action stuff yesterday? [09:20] larsu: yeah, but hit a snag with the ext attributes [09:22] dednick: hm? Those are on the menu items, not the action... [09:23] larsu: yeah. kind of tangented onto another problem. let me get you the action shizzle quick. [09:27] larsu: http://pastebin.ubuntu.com/5928350/ [09:27] larsu: it includes the action state parser stuff as well. [09:28] dednick: I already merged that :) [09:28] dednick: but don't worry, I'll sort it out [09:29] larsu: hang on. it's missing a few bits i think [09:29] forgot to bzr add [09:39] mzanetti, so, do we agree get(int index) is unnecessary in the end? [09:39] mzanetti, and exposing the object through data() is ok? [09:39] Saviq: not sure yet [09:39] mzanetti, still trying to find the issue? [09:40] Saviq: no... gave up for now. but I can't believe I introduced the get() methods for no reason. There is something fishy in there. [09:40] mzanetti, maybe it's simply a bug that was fixed since? [09:41] Saviq: that could indeed be [09:48] mzanetti, so, since we can't find issues, do we agree we're fine with exposing objects through models? [09:48] tsdgeos, maybe you want a deciding vote ↑? [09:49] tsdgeos, for context read last paragraph in https://docs.google.com/a/canonical.com/document/d/1gd87Wo_CSB0DpFWLpTKIIXQfdmFncrq0PHSr9H2PTnk/edit [09:49] Saviq: I'd say yes... in case I just missed it in my tests now and it's still present its most likely anyways one of us 2 that runs into it at first [09:49] tsdgeos, the commented entry about wrapping QObject*s in QVariant [09:50] * tsdgeos reads [09:50] larsu: http://pastebin.ubuntu.com/5928409/ [09:51] larsu: merged with latest. [09:52] Saviq: do you know if it's possible to get the model back from the modelData in a listview delegate? [09:52] Saviq: yeah, don't see why data() should not work, i mean we do it in several places already [09:53] dednick, you need to expose it as a role [09:53] Saviq: thanks :( [09:54] dednick, why :( [09:54] Saviq: fwiw i have touch in shell and apps in gerry's demo shell [09:54] now having a look at the real shell :D [09:54] tsdgeos, awesome [09:54] tsdgeos, if we get it for tomorrow, would be awesome (we're doing demos for Jane) [09:54] demo shell == http://bazaar.launchpad.net/~gerboland/+junk/qml-demo-shell/ [09:54] Saviq: meh. that sounds a bit silly. [09:54] dednick, a Model doesn't know what it's backed with, there needn't even ba a model back there [09:55] Saviq: you mean the data does know? [09:55] doesnt [09:56] dednick, I mean that a ListModel doesn't even have to be backed by anything [09:56] dednick, it can be built on the fly [09:57] Saviq: but it has to be backed by something to have items. [09:57] dednick, not really, it can be a random number generator ;) [09:57] dednick, and building a QMap out of all the roles through data() is a bad thing to do [09:57] dednick, we just added the last paragraph to https://docs.google.com/a/canonical.com/document/d/1gd87Wo_CSB0DpFWLpTKIIXQfdmFncrq0PHSr9H2PTnk/edit btw [09:58] dednick, that talks some about what you're asking [10:18] dednick: thanks! [10:19] dednick: ooh, this is quite signal happy... why are you emitting stateChanged() on rowsInserted/Removed? [10:20] larsu: yeah, signals everywhere. i guess it's been created that means the row is there. [10:20] larsu: in which case you can remove. [10:20] dednick: right [10:21] dednick: dataChanged() can happen when something other than the state changes, too [10:21] but I guess that's a premature optimization [10:21] larsu: yeah, i was going to streamline the roles later. [10:22] larsu: we have the index and the role we need, so can streamline it fairly well i think. [10:22] dednick: yep. But this is good enough for now (and I don't really have time to work on it today), so I'll just commit it for now. Thanks for the patch! [10:22] larsu: it was a bit of a crude impl. just needed it to work for now. [10:23] larsu: thanks. [10:23] yep, understood [10:24] larsu: what is the reasoning for loadExtendedAttributes? [10:25] larsu: can we not just fill ext with all the data the backend gives? [10:25] dednick: catching mismatches between what the ui requires and what the service provides early [10:25] larsu: i c. [10:25] larsu: its causing me much pain ;) [10:25] larsu: but no matter. i think i have a solution. [10:26] dednick: the other reason is that you can specify the type and it qmlifies it for you (only in the case of icons for now) [10:26] so you already get uris if you specify "icon" [10:26] dednick: is there anything I can change to make it easier? [10:26] larsu: ah yeah, i saw that... good stuff [10:27] dednick: pushed your patch [10:29] larsu: thanks. note for future. when we do the updateState, can we push a schema with that as well? i think qvariant rounds floats to ints if on an integer boundary. and we need it to convert correctly to gvariant. [10:29] larsu: at least something does that. not sure what. [10:30] larsu: it's causing type mismatch somewhere. [10:31] dednick: oh wow. Yeah, we could simply store the GVariant type information [10:31] mzanetti: but the guy that wnts qt4 won't do much with it, no? [10:32] tsdgeos: ? [10:33] mzanetti: don't think qt4 can put anything on screen in the phones since the qpa is not there [10:33] and the phone doesn't have X [10:33] tsdgeos: oh... did he want to do something on the phone for it? [10:33] tsdgeos: I just read it as. using Qt5 for phone stuff and need Qt4 for something else [10:33] well it was the ubuntu-phone ml [10:34] ah [10:34] you're probably right [10:49] mzanetti, dammit I pushed on the trunk :-\ https://code.launchpad.net/~cimi/ubuntu-settings-components/calendar-newmodel/+merge/172598 [10:50] Cimi: yeah, I've seen that. was wondering a bit... [10:50] thought maybe there is no autolanding set up for the settings-components yet [10:51] no === MacSlow is now known as MacSlow|lunch [11:17] Saviq, ping [11:23] nic-doffay: Saviq is busy at the IOM meeting, anything we can help with? [11:31] tsdgeos, need to know who is handling design work for the sdk now that Calum's gone. [11:41] if someone has some time for a review: https://code.launchpad.net/~mzanetti/unity8/new-lockscreen-design/+merge/177555 [11:48] * tsdgeos hates long lambdas [11:49] inside long functions [11:49] my eyes are not trained to see them :D [11:49] http://paste.ubuntu.com/5928714/ [12:12] nic-doffay, you're asking about the option selector? [12:12] Saviq, busy chatting about it now. [12:12] nic-doffay, ok === MacSlow|lunch is now known as MacSlow [12:14] larsu: how do i tell if a menu item is "activatable"? === alan_g is now known as alan_g|lunch [12:15] larsu: eg the mute control doesnt have a type, but is togglable [12:15] dednick: if it is sensitive, it is activatable [12:16] larsu: everything is sensitive. even separators [12:17] dednick: if is sensitive and not a separator, it is activatable [12:17] :P [12:17] * larsu wonders if separators should not be sensible [12:17] in any case, gotta run. bbiab [12:17] larsu: lol. ok [12:22] mhr3: ping [12:37] sil2100, pong === dednick is now known as dednick|lunch === hikiko is now known as hikiko|lunch [12:41] mhr3: about lucrene++, what do we need it for in main? [12:42] sil2100, getting it first in universe would be enough for me :) [12:42] mhr3: what will use it? ;) [12:42] sil2100, but then the music and video scopes will [12:43] the phone ones at least [12:43] mhr3: ACK, then I'm on it [12:43] Since I see the needs-packaging bug is abandoned ;/ [12:45] jamesh, could you point sil2100 to the latest branches ^? [12:45] there were some fixes so it compiles with saucy libs [12:45] mhr3, jamesh: isin't it https://github.com/luceneplusplus/LucenePlusPlus ? [12:45] Ah [12:45] not sure where those are [12:46] hm, so we need some upstream changes for it to work with us? [12:46] mhr3, jamesh: did you guys try getting those into upstream? === _salem is now known as salem_ [12:47] sil2100, but maybe i'm wrong, lucene++ isn't the only component, maybe the fixes are specific to the other bits [12:48] I will take care of it with pleasure, as I need karma for becoming a core dev ;p [12:49] mhr3, jamesh: keep me informed, I'll start on the packaging now and we'll deal with the additional fixes later [12:49] sil2100, thank you [12:50] Better doing it ASAP before the FF [12:50] indeed [12:50] that's why i'm pinging about it :) [12:55] mzanetti, ping [12:56] hi dandrader, wassup? [12:56] hi [12:56] sil2100, and having arm builds of it would be awesome [12:56] mzanetti, do you know why I didn't hear back from jenkins after my latest update to https://code.launchpad.net/~dandrader/unity8/runningApps_lp1193419/+merge/175955 [12:56] ? [12:56] dandrader: I have noticed that the Dash tests sometimes hang and get killed only after an hour [12:58] dandrader: hmm... there isn't a job running tho... [12:58] mzanetti, in this merge proposal I'm poking at the tst_Shell qmluitest. it's acting very weird in jenkins. seems like it start calling the test functions *before* the scene is fully loaded [12:58] e.g.: some components are not found by findChild() [12:58] mzanetti, https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-saucy/1446/? [12:59] when the components are loaded you get a lot of warnings output to the console [12:59] so you normally see this output during the initTestCase (or something like that) function [12:59] dandrader: are they loaded with a loader? [12:59] Saviq: what about this? [12:59] mzanetti, those seem to be real failures [12:59] but in jenkins you get that init output only on the first or second real test function [13:00] that + the fact that some findChild() calls are failing point to my theory that jenkins is executing tests before the scene is fully loaded [13:00] hence the latest workarounds I put in this MP === alan_g|lunch is now known as alan_g [13:02] mzanetti, let me check.... [13:04] mzanetti, yes. DashHome -> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/832/testReport/junit/%28root%29/qmltestrunner/Shell__initTestCase/ [13:04] dandrader: so you might want to add tryCompare(loader, "progress", 1) in initTestcase() ? [13:05] Saviq: do you know which upstream build it was? [13:05] mzanetti, good idea. === hikiko|lunch is now known as hikiko [13:09] mzanetti, ah sorry - your "new lockscreen" branch [13:10] mzanetti, forgot there's no mention of that in mediumtests runner [13:12] Saviq: hmpf... they pass locally [13:14] oh no... they dont [13:14] * mzanetti fixes [13:14] mzanetti, ;) [13:17] Saviq: fixed. thanks for letting me know. I would have missed it [13:17] mzanetti, cheers [13:17] asac, unity8 is green today [13:18] Saviq: rock on! :) [13:18] lets hope for crash report support [13:19] asac, indeed, since manta is showing *a* crash still - it might actually be the same I reported before [13:20] * sil2100 published unity8 in the morning [13:25] mhr3: lucene++ sucks in this way that even though the git repo has CMake config files, the release tarballs don't [13:25] It's like, a big WTF [13:25] No new releases since 3 years ago [13:29] sil2100, simple, package git snapshot :) [13:45] mterry: hey [13:45] mterry: did you test the ofono stuff already somehow? [13:45] mterry: I mean manually, not writing automated tests for it [13:47] mterry: my code should work in theory, but I'm having a hard time testing it on the phone [13:48] mzanetti, no. I assumed libofono worked, and my plugin was such a thin wrapper, it didn't seem anything could go wrong [13:48] mterry: yeah... not saying your code wouldn't work... the thing is, apparently our ofono does not (yet) notice if you put in a sim card during runtime [13:49] mterry: and to test the startup scenario I need to install my branch into the system [13:49] thats why I ask - if you have some hints for triggering ofono or whatever... [13:49] but I'll figure it out [13:50] mterry: ah btw... you forgot to install the qmldir file. I fixed that in your branch. unfortunately I messed up the history :/ [13:50] sorry about that [13:50] mzanetti, oh right, that's a separate CMake command now [13:51] mzanetti, it doesn't notice if you put a card in? hmm... awe made it sound like that stuff worked... let me poke him [13:52] mterry: I'll push my stuff... might be buggy at some places because I couldn't fully test yet. but in theory it should support entering the pin at startup and also on the fly [13:52] mterry: pushed. [13:53] mzanetti, how does it handle on the fly? Like, does it pop up a dialog? [13:53] mzanetti, that looks like a valid failure as well for "new lockscreen" https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-saucy/840/? [13:53] mzanetti, mterry: do you guys have a custom made dialpad in your greeter? [13:54] seb128, yeah [13:54] I saw something looking like it in a merge request [13:54] mterry, do you know if there is any plan to have a proper shared widget for that? we need that in system settings as well [13:54] I'm pondering copying your meanwhile :p [13:56] seb128, ah interesting [13:56] seb128, it's a Qml file sitting on the disk... Probably could be easily reused... [13:57] I don't know how hacky it is in the Qml universe to just point QML2_IMPORT_PATH at the unity dir and pull it in [13:58] Saviq, ^ how hackish is that? [13:58] mterry, I think I might just cp it, feels safer [13:58] especially if you guys don't promise stability for the behaviour/properties [13:59] * tsdgeos confused [13:59] error: format ‘%p’ expects argument of type ‘void*’, but argument 2 has type ‘mir::input::android::InputTargetEnumerator*’ [13:59] ? [13:59] seb128: I guess if we want a shared component we need to do it. the phone one will look slightly different. [14:00] tsdgeos, ouch [14:01] seb128: the phone one will have a mailbox icon below the 1 and the letters below the other numbers etc. We don't need/want that for the PIN entry for example. but if you have the same requirements as I do, I'm open for reusing code [14:01] Saviq: i added a nice (void*) cast to my printf :D [14:01] mzanetti, seb128, mterry there's ubuntu-system-components that might be a possible place for it [14:01] mzanetti, is your design somewhere? [14:01] mzanetti, seb128, mterry, or maybe it should actually be a theme delegate? [14:02] seb128: lp:amanzi-team/design [14:02] (caveat: I don't know what I'm talking about) [14:02] Saviq, what is a theme delegate? [14:02] mzanetti, the ones we need are https://wiki.ubuntu.com/PhoneApp?action=AttachFile&do=get&target=phone-settings-call-diversion-number.png and https://wiki.ubuntu.com/Bluetooth?action=AttachFile&do=get&target=phone-bluetooth-pair.png [14:02] he doesn't know [14:02] Saviq, the theme says "draw a pin here" and the theme engine provides it? [14:02] seb128: this rather looks like a OSK plugin to me [14:02] seb128: a number-only OSK layout [14:03] mzanetti, is your different? [14:03] seb128: lemme upload a pic [14:03] seb128, mterry, mzanetti +1 - it should be OSK [14:03] hum [14:03] seb128: this is ours: http://wstaw.org/m/2013/07/30/plasma-desktopkO1139.png [14:04] can the OSK be "embedded" in the app? [14:04] or do you mean it's like splitting screen in half [14:04] seb128, why do you want it embedded? [14:04] where the bottom part is the osk? [14:04] seb128: I don't think so, but you can pop it up an lock it to open I think [14:04] the user won't see the difference [14:04] seb128, see http://qt-project.org/doc/qt-5.0/qtqml/qml-qt.html#inputMethod-prop btw [14:04] seb128, which is exposing the keyboard state and geometry to your app [14:05] Saviq, thanks [14:05] mzanetti, Saviq: right, I'm used to test on my desktop and not fully think "phone/full screen" [14:05] Saviq, mzanetti: thanks for the advices! [14:05] seb128, on desktop nothing should happen, then, you just type it with your keyboard :) [14:06] well, I was shooting for having an UI with the pad displayed in the dialog and mouse clickable [14:06] but yeah, keyboard is good enough [14:24] mhr3: dude, what the heck is wrong with this lucene package, it's building like 20 minutes already [14:24] It's like a kernel god dammit [14:24] sil2100, pfff, you'll be happy if it finishes in an hour :P [14:24] Daaamn ;p [14:25] I suppose this package cleans, does the laundry and walks the dogs for its user? [14:25] sil2100, and makes sandwiches! [14:25] but you need sudo for that [14:26] ;) === alan_g is now known as alan_g|tea [14:34] * tsdgeos needs someone from mir [14:34] is there a #ubuntu-mir ? [14:35] yes there is === alan_g|tea is now known as alan_g [14:53] hi, could anyone look up https://bugs.launchpad.net/indicator-session/+bug/1206231 [14:53] Launchpad bug 1206231 in Session Menu "clicking on lock screen does not lock the screen on saucy" [Undecided,New] [15:01] Saviq: ping [15:01] tsdgeos, pong [15:02] Saviq: i can give you a shell in which you can interact with the app you launched, but you can't go back :D [15:02] which atm you can't go back anyway [15:02] so it's a bit of an improvement [15:02] not sure if enough :D [15:02] it's basically a hack [15:06] tsdgeos, can't go back meaning? if I open an app, I can't go back to shell any more? [15:06] brb, need to reboot [15:06] Saviq: yep, that [15:16] tsdgeos, I'll wait for a better result ;) [15:16] ok [15:16] mzanetti, have you tried that trick of checking a Loader's progress before? from the documentation it seems it's about downloading the file from the network and not about instantiating components by parsing the file... [15:17] Saviq: not sure i'll be able to produce that today [15:17] dandrader: i used it before, yes. might have been Loader.status == Loader.Ready [15:17] dandrader: or Loader.item !== undefined [15:18] dandrader: but there is a way to figure when its done [15:18] "Note that if the source is a local file, the status will initially be Ready (or Error). While there will be no onStatusChanged signal in that case, the onLoaded will still be invoked." [15:19] mzanetti, "Loader.item !== undefined" sounds solid [15:19] dandrader: a waitForRendering(someItemContainingTheLoader) might do to [15:19] dandrader: if the file is always a local file [15:19] dandrader: but I guess in most cases that's safe to assume [15:20] mzanetti, where this waitForRendering comes from? [15:20] dandrader: I think from TestCase... tsdgeos digged it out at some point [15:21] yep [15:21] hmm [15:21] dandrader: anyways, check the lockscreen tests. there is a Loader which loads either the PIN or Passphrase lockscreen [15:21] dandrader: and the tests seem to work fine when using waitForRendering [15:21] mzanetti, ok [15:28] dandrader: you did the DDA thingie, right? [15:29] tsdgeos, it depends. is there a problem with it? [15:29] dandrader: no [15:29] tsdgeos, ok, then yes, I did it :) [15:30] dandrader: i just want to know if they define a width i can use to punch holes when using unity-mir [15:30] i.e. the DDA of the bottombar for example [15:30] has a height of a few pixels i can use? [15:30] tsdgeos, didn't really get your question... [15:31] tsdgeos, but the size of the DirectionDragArea is the area where touch events will be caught [15:31] dandrader: ok, that's what i wanted to know [15:31] tx [15:32] dandrader: so basically we are "stealing" the DDA's sizes from the apps at the moment, right? [15:32] s/sizes/areas [15:32] tsdgeos, yes [15:33] okidoki [15:33] tsdgeos, although that "stealing" is done by another component [15:34] by who? [15:35] tsdgeos, because the DirectionalDragArea is just another component, like Flickable. It doesn't have those cross-app stealing powers [15:35] ah [15:35] sure [15:35] well [15:35] * dandrader checks [15:35] it does have for me [15:35] since i'm unity-mir [15:35] i'm all powerful [15:35] tsdgeos, InputFilterArea is the one [15:36] guess who just successfully entered the SIM pin through the UI [15:36] tsdgeos, but that "stealing" scheme is going away once we have a proper gesture canceling or accept/reject [15:36] by gesture I mean simply a group of touch events from a given touch point) [15:37] sure [15:37] i'm just trying to get the unity-mir stuff to kind of work [15:37] i'll let the smart stuff for when gerry is back :D [15:37] mzanetti, congrats [15:37] dandrader: thanks :) [15:37] * mzanetti needs to clean up the room because that *might* get him into the Kyle Gass project [15:46] mzanetti, what's the name of that suspect component again (the memory leak thing) [15:46] in the ubuntu toolkit [15:47] mzanetti, UbuntuShape? [15:49] dandrader: yeah, UbuntuShape had lots of bugs with leaking memory [15:49] dandrader, mzanetti there's a rewrite in the works, btw [15:49] Saviq: yeah, still useful to know if its indeed that [15:49] dandrader, try loicm to see if he has something you could use to investigate [15:49] mzanetti, of course [15:59] Saviq: ok so with lp:~aacid/unity-mir/improve_input_area_handling lp:~aacid/mir/hidden_surface_no_contains and lp:~aacid/unity8/unity8-integrate-mir-input-areas you should have a shell that is kind of usable, can launch apps, use them, switch them back with the left swipe (not sure if right swipe) works [16:00] i know building 3 branches kind of sucks :D [16:00] tsdgeos, you can push to unity-mir directly [16:00] tsdgeos, and to unity8-integrate-mir [16:01] tsdgeos, only the mir one needs to go through MR [16:01] i know [16:01] tsdgeos, and I'll trigger builds into https://launchpad.net/~phablet-team/+archive/mir/ [16:01] the unity-mir change should be ok, but still with gerry we said we would do MRs [16:01] unity8-integrate-mir is a bit of a hack [16:01] i mean it works better than now [16:02] but may want gerry to give an "architecture" overview [16:02] but if you want i can just push them [16:02] and then when gerry is back we have a look [16:02] tsdgeos, it's probably fine [16:02] tsdgeos, let's talk tomorrow, have your afternoon [16:02] Saviq: well, you need to show it tomorrow, no? [16:02] tsdgeos, I'll try and try it out in the mean time [16:02] what time? [16:02] tsdgeos, tomorrow afternoon [16:02] ok [16:02] tsdgeos, 0200UTC [16:03] pm [16:03] so 1400UTC ;) [16:03] sorry [16:03] you probably don't need lp:~aacid/mir/hidden_surface_no_contains unless you want to use more than 1 app at the same time [16:03] tsdgeos, yeah, let's see where we get tomorrow [16:04] tsdgeos, I'll try and get the mir guys to review that in the mean time [16:04] they seem to be on it [16:04] ok cool [16:04] at least alan_g gave a +1 [16:04] not sure if that measn it'll be merged or not :D [16:05] tsdgeos, they'll probably wait for another +1 [16:06] tsdgeos: If no-one top-approves before my start of day tomorrow. I'll do it. (But other timezones ought to get a say.) [16:06] sure [16:06] no hurry :-) [16:09] * tsdgeos logs off for the day [16:30] dednick: hi [16:30] pete-woods: howdy [16:31] dednick: I'm just looking at unitymenumodel/qmenumodel - should I be able to export a menumodel using Qt with that? [16:31] or is it just for connecting to already exported gmenumodels? [16:32] pete-woods: it's for the frontend. needs an exported model. [16:32] dednick: so the only way to export a model at the moment is through the gmenumodel API? [16:32] mzanetti, Saviq without UbuntuShape and memory still growing as usual [16:33] FYI ^ [16:33] dandrader, thanks [16:33] pete-woods: as far as i know. larsu is gmenumodel qt king. [16:34] although i'm sure he wont appreciate me causing him more pings :) [16:35]