[16:03] <Saviq> hmm is there a video for anyone?
[16:04] <Saviq> ah now it's here
[16:05] <nuclearbob> is anybody else getting a 502 error on the video?
[16:06] <christina> saviq nuclearbob is it ok now
[16:06] <vthompson> nuclearbob: I did but refresh fixed it
[16:06] <Saviq> 502 :/
[16:06] <t1mp> video works for me now
[16:06] <nuclearbob> christina vthompson: I'll keep refreshing, no luck so far
[16:07] <christina> ok let me look into it
[16:07] <christina> how about now
[16:07] <christina> ive updated the link
[16:09] <vthompson> I think the 502 issue is a Youtube/Google issue in general. I'm getting the same error on some of the bottom edge YouTube videos
[16:09] <t1mp> I don't see the video on http://summit.ubuntu.com/uds-1403/meeting/22224/bottom-edge-update/ now
[16:09] <christina> https://plus.google.com/hangouts/_/hoaevent/AP36tYfzOSVlWyGfh6Csw3u0i5-J8oPyS--IzDO-nQCkpso9MT6cRw?authuser=0&hl=en-GB
[16:10] <christina> join us then :)
[16:10] <t1mp> :)
[16:10] <t1mp> even better
[16:10] <Saviq> we broke google, yay
[16:10] <t1mp> you can ask questions live. Or disable your video and audio if you like to
[16:13] <Saviq> actually now there seems to be an issue with summit, the frame where the video is supposed to be is empty
[16:13] <Saviq> christina, ↑ maybe something misfired with updating the link?
[16:13] <t1mp> same for me. Video is not on the summit page anymore
[16:13] <vthompson> QUESTION: Do you envision the user being able to "stop" at any of the 3 phases by releasing while at say the first phase?
[16:14] <t1mp> vthompson: thanks. We'll let Dani finish his story and then go through the questions
[16:14] <t1mp> more questions are welcomed :) just prefix your question with QUESTION
[16:16] <Cimi> QUESTION: How will apps run on the desktop, where a mouse is not really designed for swipes?
[16:19] <Cimi> QUESTION: How do we help developers in assigning the bottom edge for doing the right thing? I can see it easily becoming confusing for the user, in case every app might use it for different purposes
[16:24] <vthompson> QUESTION: As an easy way for apps to implement this, could one option be to allow developers to have more control over the HUD? I'm torn between deciding to implement this from scratch for the music-app because I've wanted to do this for a LONG time... If it might be done via the HUD most of that work will be for naught
[16:25] <t1mp> one edge to rule them all ;)
[16:26] <vthompson> But there are 4 edges. ;) The next device that should be created should be a pentagon shaped phone
[16:30] <vthompson> That answers my question.
[16:31] <vthompson> t1mp: will this be a component in the SDK? In other words, should I expect to use a "BottomEdge" component and customize it?
[16:32] <t1mp> vthompson: I'll answer in the video
[16:34] <vthompson> excellent
[16:38] <vthompson> t1mp: does the Panel component currently allow a header?
[16:39] <t1mp> vthompson: basically it is an Item that detects bottom edge swipes and tracks a position
[16:39] <t1mp> vthompson: so every visual that needs to be in it, you have to put yourself
[16:39] <t1mp> vthompson: but you make a good point. Currently it does not allow a header
[16:39] <t1mp> vthompson: we'll need to add a more advanced header component for that. I will create a bug for it.
[16:39] <vthompson> It does have a "hintSize" though... what's in the hint?
[16:40] <vthompson> I take it that's for swiping up though, I guess
[16:40] <t1mp> vthompson: the hintsize is how much the panel will pop up from the bottom edge when you just touch the dge
[16:40] <t1mp> *the edge
[16:40] <t1mp> so without swiping
[16:40] <vthompson> ah, ok
[16:41] <t1mp> vthompson: you can see that with the current toolbar, when you just touch near the bottom edge, you can see it pop out for 1 grid unit
[16:42] <t1mp> vthompson: I don't know how to implement it yet. We have to give it some thought. But here is the bug https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1291477
[16:42] <udsbotu> Launchpad bug 1291477 in Ubuntu UI Toolkit "new component: Panel with contents and header" [High,New] - Assigned to Tim Peeters (tpeeters)
[16:42] <vthompson> t1mp: the music app implemented a lot of this from scratch for our custom toolbar. we'll want to rewrite for the Panel component and from there I'm sure we'll put together the full screen queue view
[16:43] <vthompson> This is all very good to know though
[16:43] <t1mp> vthompson: the Panel is very basic for now. More features will be added, but it will take some time. Moving the current toolbar features to the header has priority now
[16:44] <vthompson> Since it's just an item with position control, I believe we have everything we need
[16:45] <t1mp> vthompson: ok, cool
[16:45] <t1mp> vthompson: the current toolbar may be in the way of the panel, but as soon as we land Qt 5.2, I have a merge proposal ready that adds a boolean property to the MainView that can be used to disable the toolbar
[16:47] <t1mp> vthompson: if there are issues with anything Panel-related, just ping me on irc (and/or report a bug on https://bugs.launchpad.net/ubuntu-ui-toolkit )
[16:47] <vthompson> t1mp: is a bool really something thats needed when you can simply set the ToolbarItems to locked and not opened?
[16:47] <vthompson> will do, thanks!
[16:48] <t1mp> vthompson: yes, you can do that also
[16:48] <t1mp> vthompson: for now the bool only disables the toolbar, but when I add more features to the header it will be used to enable those also
[16:48] <vthompson> oh right
[16:49] <t1mp> vthompson: eventually, the bool will be used by the app developers to switch from the current toolbar with the tools in it, to putting all the tools (automatically) in the header
[16:49] <t1mp> so app developers will be able to test their app with the new header before deciding to switch to using the header instead of toolbar for their app
[16:52] <t1mp> thanks everybody for watching the session :)