[00:52] <aquarius> mhall119, I haven't proposed any appdev sessions because I don't know of anything which I want to happen which isn't already on someone's list.
[00:53] <aquarius> mhall119, and because I can't commit to any time to building these things, partially for job reasons and partially because I want to be an app developer, not an OS developer.
[00:53] <aquarius> mhall119, do you have sessions in mind that you think I should propose?
[00:53] <aquarius> I will of course try and be present for UDS sessions!
[00:53] <popey> yay
[01:19] <aquarius> popey, I admit that this is not really much help.
[10:03] <JamesTait> Good morning all; and though I hesitate to say it, happy Men Make Dinner Day! :-D
[10:03] <popey> Good morning JamesTait
[10:04] <JamesTait> It is!
[10:15] <t1mp> JamesTait: pfew. You almost scared me there, but I see you left out the "National" part of the special day. It is only valid in USA ;)
[10:16] <JamesTait> t1mp, feel free to play along anyway, just for fun. ;)
[10:16] <t1mp> :)
[10:16]  * JamesTait alerts the fire service.
[10:17] <aquarius> Do I *have* to have a MainView? Think of, for example, a full-screen game, where I don't want the header. What happens if I don't have a MainView? Does a bunch of stuff not work, then? Or is the best thing to do to have a MainView and somehow not include the header?
[10:17] <t1mp> aquarius: if you set the title of your active page to "" the header will be hidden
[10:18] <aquarius> t1mp, aha. So I should still have a mainview and just hide the header
[10:18] <aquarius> I suspected that might be the case
[10:18] <aquarius> might be worth poking the documentation for that case
[10:18] <aquarius> or maybe even adding a makeMyThingFullscreen bool property to mainview, which will help people realise how to do it?
[10:19] <t1mp> aquarius: wait a second, maybe I am lying :( I don't see in the code now that it'll hide when title is ""
[10:20] <aquarius> t1mp, it works, though
[10:20] <aquarius> so I think we're good :)
[10:20] <t1mp> ok, great
[10:20] <aquarius> except that this is wholly undocumented, as noted ;)
[10:21] <t1mp> aquarius: can you report a bug for that lack of documentation?
[10:25] <aquarius> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1248898 filed
[10:25] <ubot2> Launchpad bug 1248898 in Ubuntu UI Toolkit "No documentation for how to hide MainView's header" [Undecided,New]
[10:26] <t1mp> aquarius: thanksk.
[14:00] <t1mp> oSoMoN: I replied on https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/ap-toolbar-open/+merge/194122
[14:01] <oSoMoN> t1mp, replied there
[14:03] <t1mp> oSoMoN: yes, the toolbar always closes after 5s of inactivity
[14:03] <t1mp> oSoMoN: or when the user interacts with the app
[14:03] <t1mp> oSoMoN: and there is a request to hide it also when the user interacts with the app header
[14:04] <t1mp> oSoMoN: I think in most cases my solution is fine because toolbars only have buttons usually
[14:04] <t1mp> oSoMoN: but I realize that the webbrowser (and perhaps other apps) are special cases
[14:04] <daker> tmoenicke: ping
[14:06] <t1mp> oSoMoN: hmm.. maybe somehow the timer should stop when the user touches anywhere on the toolbar and restart when releasing
[14:06] <t1mp> oSoMoN: would that help? I guess for interacting with the address bar that would avoid hiding while doing stuff there
[14:06] <t1mp> oSoMoN: so then it is not strictly a test issue, but some toolbar behavior I need to fix
[14:10] <t1mp> oSoMoN: ok I commented on https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/ap-toolbar-open/+merge/194122
[14:10] <t1mp> oSoMoN: did you run into the issue on the browser that the toolbar can close while entering a url?
[14:10] <oSoMoN> t1mp, no, I’m not having issues with the browser, as I’m not using the default toolbar, I’m using a custom one
[14:12] <oSoMoN> t1mp, so in fact the only reliable solution for tests is to first ensure the toolbar is hidden by interacting with the app’s contents, then reveal it and then interact with it
[14:12] <oSoMoN> t1mp, otherwise we’ll always run into race conditions where the toolbar hides while moving the cursor to interact with it
[14:15] <t1mp> oSoMoN: well click_button() now checks that the toolbar wasn't closed (or closing) already and opens it again if needed
[14:16] <oSoMoN> t1mp, yeah, in that case I guess that’s an acceptable solution
[14:18] <t1mp> oSoMoN: ok, I'll go with that then. And I will report a bug for pausing of the timer for interaction with other components (textfield / slider) in the toolbar
[14:19] <t1mp> oSoMoN: but I don't think any apps do that (yet) so it is not urgent
[14:19] <oSoMoN> t1mp, yeah, probably not high priority
[14:20] <oSoMoN> t1mp, it might make sense to update the emulators’ documentation (if there is any) to explain the default behaviour of the toolbar, and that click_button() will ensure it’s shown before actually clicking
[14:22] <t1mp> oSoMoN: sure, I will add that.
[14:22] <t1mp> thanks
[14:24] <blaroche> bzoltan: ping
[15:32] <oSoMoN> dpm, hey, is there a design meeting for calendar-app today?
[15:32] <dpm> oSoMoN, not that I know of, I shall cancel it for this week. At UDS we'll be discussing the roadmap and how we resume the meetings for next cycle
[15:33] <dpm> popey, makes sense? ^
[15:33] <oSoMoN> dpm, makes sense to me, thanks for confirming
[15:33] <dpm> k
[15:33] <popey> No, we cancelled all the hangouts.
[15:54] <aquarius> dpm, do you think it's worth having a uds session about fat packages? I mean, I think bzoltan1 and team know about the need for it, and for the app runner to handle them?
[15:56] <dpm> aquarius, I think it might be, but I'd also check with cjwatson first, as he's got the best overview on the click packages roadmap
[15:59] <aquarius> dpm, as I understand it, click itself is now quite capable of creating fat packages, but the app runner doesn't know how to run them properly because that bit hasn't been decided :)
[15:59] <dpm> aha
[15:59] <dpm> aquarius, when you say app runner, you mean upstart?
[15:59] <dpm> or qmlscene?
[16:00] <aquarius> dpm, upstart
[16:01] <aquarius> dpm, something needs to do the moral equivalent of "QML2_IMPORT_PATHS=/opt/click.ubuntu.com/com.mypackage/current/lib/qml/arm qmlscene /opt/click.ubuntu.com/com.mypackage/current/MyApp.qml"
[16:01] <aquarius> and the same for ld_library_path for C libs
[16:01] <aquarius> and possibly $PATH for binaries
[16:02] <aquarius> that's upstart: it happens before you start qmlscene. The thing which runs packages needs to recognise that that package *is* a fat package which contains arch-specific stuff, and then make sure that the arch-specific stuff which is appropriate for the arch we are on is the stuff that gets loaded :)
[16:02] <aquarius> presumably we need some way of declaring that the Exec= line actually points to an arch-specific binary, too
[16:03] <aquarius> unless that's just handled by the path stuff as well
[16:05] <dpm> yeah, but I guess that last bit would be if the binaries actually need to be executed to start the app (e.g. a pure C++ app). So far we've just been loading QML frontends that consume binary components
[16:07] <dpm> I've pinged tedg, he might be able to help better than I can in this area
[16:07] <tedg> Howdy
[16:07] <dpm> ah, speaking of the devil...
[16:07] <dpm> hi tedg :)
[16:08] <tedg> So I'm a bit confused.  Are we installing all the binaries on disk?
[16:08] <dpm> tedg, we were wondering if you could shed some light on this discussion: http://pastebin.ubuntu.com/6377041/
[16:09] <tedg> I figured we'd just delete the unused ones.
[16:09] <dpm> I'm not familiar with how the actual fat packages will deal with the binaries
[16:09] <dpm> aquarius?
[16:10] <tedg> This probably isn't a good channel... cjwatson isn't here either :-)
[16:10] <aquarius> I don't know how any of this is supposed to work
[16:11] <dpm> In that case, I think we might just want to jump into #ubuntu-devel and ask cjwatson
[16:11] <aquarius> happy to
[16:12] <aquarius> I'm not sure cjwatson is driving it though
[16:12] <aquarius> he's doing "make click be able to create these packages", whcih I believe it already does
[16:12] <aquarius> making the app runner care about them -- he said he'd spoken to the sdk team, i think
[19:06] <balloons> nik90, I see your trying to land your swip branch now
[19:06] <balloons> let me know if you need anything
[19:21] <tmoenicke> daker: pong
[19:21] <nik90> balloons: hi
[19:22] <nik90> balloons: I looked at the test failures and figured it could do a fix or two. I fixed everything on my end now. Just waiting for the swipe delete emulator fix from elopio.
[19:22] <nik90> balloons: I have also created another branch where I added 3 more autopilot tests
[19:22] <balloons> oO :-)
[19:23]  * nik90 knew balloons would be glad :P
[19:23] <tmoenicke> daker: just seeing your comment on the language MR, thank you
[20:31] <daker> tmoenicke: yw :)
[20:32] <daker> tmoenicke: i hope that the long list will not create UI issues :)
[20:32] <tmoenicke> daker: not sure
[20:32] <tmoenicke> daker: could it be shorter somehow?
[20:34] <daker> tmoenicke: no, all those countries have arabic as their official language
[20:34] <tmoenicke> daker: ok
[20:34] <daker> tmoenicke: https://en.wikipedia.org/wiki/Arab_world
[22:04] <mhall119> Looky there, HTML5 UI API docs are now available! http://developer.ubuntu.com/api/html5/sdk-1.0/UbuntuUI/