12:03 <popey> #startmeeting Dekko meeting
12:03 <meetingology> 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 <meetingology> 
12:03 <meetingology> Available commands: action commands idea info link nick
12:03 <popey> 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 <JMulholland> haha, no problem popey
12:03 <popey> How we doing chaps?
12:04 <DanChapman> Doing good thanks :-)
12:05 <popey> What do we have to discuss this week?
12:05 <DanChapman> JMulholland: is https://bugs.launchpad.net/dekko/+bug/1393779 still correct to go fullscreen in landscape?
12:07 <popey> that would fail on nexus 7 with kb attached in windowed mode I imagine?
12:07 <popey> 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 <JMulholland> Hm, I think the ‘supress indicators in landscape’ idea may have gone away?
12:09 <popey> well, some things like games can go full screen
12:09 <popey> that makes sense
12:09 <JMulholland> I can’t find any examples of it in our apps that support landscale at the moment...
12:09 <JMulholland> for games, yes. But then wouldn’t they suppress/hide the indicators in portrait too if that were the case
12:10 <popey> they would, yes
12:10 <popey> I'm just not convinced (non-game) apps should be hiding the indicators
12:11 <popey> even for fully immersive composition (email) or consumtion (reading) tasks?
12:11 <DanChapman> Yeah i agre, I think it only really works with games
12:12 <DanChapman> So if that's no longer valid then I can just mark that as released as shell-rotation is now enabled
12:12 <popey> the problem comes as jamie identifies, with low res screens, bq e4.5 is only 540 pixels wide/high
12:13 <JMulholland> 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 <JMulholland> *FROM
12:15 <JMulholland> Just looking at notes on a BQ now...
12:16 <JMulholland> (which has landscape) and yes, with the OSK in view there is very little room to show the text being entered…
12:16 <JMulholland> The indicators are obscuring 20-25% of the available space to view the entered text
12:17 <JMulholland> Although notes has a special toolbar it keep in view ‘stacked’ ontop of the OSK
12:17 <popey> yeah, this is a problem for all platforms
12:17 <DanChapman> 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 <popey> on ios you can't see the conversation in messaging app when landscape
12:18 <JMulholland> And iOS hide their indicators, as far as I recall
12:19 <JMulholland> 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 <JMulholland> So i think we Jamie is right; an additional line is a marginal improvement, but an improvement none the less
12:22 <popey> yeah
12:22 <popey> I'll leave that decision to you two then :)
12:22 <JMulholland> 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 <JMulholland> i.e. Hide the indicators in landscape at all times, not just for compossing
12:23 <DanChapman> Oh yeah that's true. I was thinking just the composer going full screen :-)
12:24 <DanChapman> Ok then i'll get that on the backlog for next milestone then
12:25 <JMulholland> 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 <DanChapman> 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 <JMulholland> 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 <DanChapman> awesome, thanks!
12:32 <popey> Ok, anything else to discuss?
12:32 <DanChapman> when can we expect uitk 1.3 to be on devices?
12:32 <popey> it already is
12:32 <DanChapman> What on stable?
12:32 * popey checks
12:32 <popey> [M#PKii  ubuntu-ui-toolkit-theme                  1.3.1549+15.04.20150710.1 armhf                     Qt Components for Ubuntu - Ubuntu Theme
12:32 <popey> thats my stable bq e4.5
12:32 <popey> so, the story is thus...
12:33 <popey> 1.3 landed on OTA-1 (AIUI)
12:33 <popey> it has been iterated on over the rest of the OTAs
12:33 <popey> 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 <popey> (framework update to add newer ones will be on OTA-7)
12:34 <popey> (and will be in rc-proposed before then)
12:34 <DanChapman> Oh I see. I wasn't aware of that. Sweet! So we can actually just target that now
12:34 <popey> I would, and we can test to make sure we don't break things
12:34 <popey> (before store upload I mean)
12:35 <DanChapman> That makes things *alot* easier
12:37 <DanChapman> I haven't got anything else to discuss today.
12:38 <popey> Super stuff.
12:38 <popey> Lets wrap for now then.
12:38 <popey> thanks DanChapman JMulholland
12:38 <popey> #endmeeting