== Meeting information == * #ubuntu-touch-meeting: Dekko meeting, 27 Aug at 12:03 — 12:38 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-08-27-12.03.log.html]] == Meeting summary == == Vote results == == Done items == * (none) == People present (lines said) == * popey (33) * JMulholland (17) * DanChapman (14) * meetingology (3) == Full Log == 12:03 #startmeeting Dekko meeting 12:03 Meeting started Thu Aug 27 12:03:32 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 12:03 12:03 Available commands: action commands idea info link nick 12:03 JMulholland: I would join you at the end of the office, but i don't think the ethernet cable I'm using will reach 12:03 haha, no problem popey 12:03 How we doing chaps? 12:04 Doing good thanks :-) 12:05 What do we have to discuss this week? 12:05 JMulholland: is https://bugs.launchpad.net/dekko/+bug/1393779 still correct to go fullscreen in landscape? 12:07 that would fail on nexus 7 with kb attached in windowed mode I imagine? 12:07 I mean, if you went automatically full screen on landscape, we'd lose the abillity to unmaximise because the window decorations would be lost? 12:08 Hm, I think the ‘supress indicators in landscape’ idea may have gone away? 12:09 well, some things like games can go full screen 12:09 that makes sense 12:09 I can’t find any examples of it in our apps that support landscale at the moment... 12:09 for games, yes. But then wouldn’t they suppress/hide the indicators in portrait too if that were the case 12:10 they would, yes 12:10 I'm just not convinced (non-game) apps should be hiding the indicators 12:11 even for fully immersive composition (email) or consumtion (reading) tasks? 12:11 Yeah i agre, I think it only really works with games 12:12 So if that's no longer valid then I can just mark that as released as shell-rotation is now enabled 12:12 the problem comes as jamie identifies, with low res screens, bq e4.5 is only 540 pixels wide/high 12:13 A fair point. And as far as I know, even when hidden the idea is that you could still swipe the relevant edge to reveal the indicators, so users arent locked out form using them…. 12:14 *FROM 12:15 Just looking at notes on a BQ now... 12:16 (which has landscape) and yes, with the OSK in view there is very little room to show the text being entered… 12:16 The indicators are obscuring 20-25% of the available space to view the entered text 12:17 Although notes has a special toolbar it keep in view ‘stacked’ ontop of the OSK 12:17 yeah, this is a problem for all platforms 12:17 Hmmm pulling up the bottom edge in landscape would mean the animation initially goes up behind the indicators it would then have to move into a fullscreen infront of it. Which IMO will look weird 12:17 on ios you can't see the conversation in messaging app when landscape 12:18 And iOS hide their indicators, as far as I recall 12:19 Even withpout notes special toolbar ontop of the OSK, we’re still losing a 6th or 7th od the viewable space with the indicators 12:19 So i think we Jamie is right; an additional line is a marginal improvement, but an improvement none the less 12:22 yeah 12:22 I'll leave that decision to you two then :) 12:22 DanChapman: One more reason ‘for’ then. If the indicators are hidden to begin with in landscape, no clash with pulling up the bottom edge :) 12:23 i.e. Hide the indicators in landscape at all times, not just for compossing 12:23 Oh yeah that's true. I was thinking just the composer going full screen :-) 12:24 Ok then i'll get that on the backlog for next milestone then 12:25 And I’ll pass on the recommendation that apps that are heavy OSK users should hide indicators in Landscape as a general rule 12:25 While were on the composer. We don't have any designs from jouni for it. Are we still going with the split view with drafts on the left, as per your wireframes? 12:26 I spoke to Jouni this morning and he assured me he’d be working on visuals for oustanding screens (including composer) now that he’s back from Holiday 12:27 awesome, thanks! 12:32 Ok, anything else to discuss? 12:32 when can we expect uitk 1.3 to be on devices? 12:32 it already is 12:32 What on stable? 12:32 * popey checks 12:32 [M#PKii ubuntu-ui-toolkit-theme 1.3.1549+15.04.20150710.1 armhf Qt Components for Ubuntu - Ubuntu Theme 12:32 thats my stable bq e4.5 12:32 so, the story is thus... 12:33 1.3 landed on OTA-1 (AIUI) 12:33 it has been iterated on over the rest of the OTAs 12:33 if there is something specific in 1.3 you need, that will break on older releases, then we need to bump the framework 12:33 (framework update to add newer ones will be on OTA-7) 12:34 (and will be in rc-proposed before then) 12:34 Oh I see. I wasn't aware of that. Sweet! So we can actually just target that now 12:34 I would, and we can test to make sure we don't break things 12:34 (before store upload I mean) 12:35 That makes things *alot* easier 12:37 I haven't got anything else to discuss today. 12:38 Super stuff. 12:38 Lets wrap for now then. 12:38 thanks DanChapman JMulholland 12:38 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)