[07:20] <justCarakas> shouldn't there be a ubuntu app aswel for https://ninjablocks.com/#/ ?
[11:20] <kalikiana> t1mp: zsombi so which one of you will take https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/orientationManual/+merge/254753
[11:21] <zsombi> kalikiana: me
[11:21] <kalikiana> thanks!
[11:22] <davidcalle> stephwilson, hello, just a quick irc bug report : images on https://design.ubuntu.com/apps/getting-started/ui-model are pulled from https://design.canonicalwebteam.com, which makes them invisible for most people
[11:22] <zsombi> kalikiana: don't forget to update teh card :)
[11:24] <stephwilson> davidcalle: Ah I see! I will get someone from the web team to have a look, think it might have to do with the http tag. Thanks for spotting it
[11:24] <davidcalle> stephwilson, np
[11:29] <kalikiana> zsombi: well, it's not done before it's reviewed
[11:29] <zsombi> kalikiana: well, it's in Needs review, right? so update the card :)
[11:30] <stephwilson> davidcalle: Ah I saw the problem, can you check if it is ok now?
[11:31] <davidcalle> stephwilson, yep, fixed!
[11:33] <stephwilson> Horray!
[11:43] <nik90> ogra_: hey, in your g+ app, you added a progress bar just below the header. Can you link me to that code? I want to create a custom progress bar.
[11:49] <kunal> charles, hi
[11:57] <ogra_> nik90, i stole it from webbrowser-app ... https://code.launchpad.net/~ogra/junk/google-plus-app
[11:59] <ogra_> http://bazaar.launchpad.net/~ogra/junk/google-plus-app/view/head:/qml/ThinProgressBar.qml ... called by line 7 and 97-104 in http://bazaar.launchpad.net/~ogra/junk/google-plus-app/view/head:/qml/Main.qml
[12:00] <nik90> ogra_: yeah I found it, thnx
[12:01] <nik90> ogra_: I wanted to created a custom progress bar to hide the percentage value shown. But turns out there is already a property called showProgressPercentage that does this...but it isnt document :/
[12:01] <ogra_> oh, yeah
[12:19] <popey> t1mp: do you know if we have a toolkit bug tracking the fact that a focussed field (in a big list of fields) is offscreen/obscured by osk?
[12:19] <dpm> hey ahayzen, how did the membership meeting go?
[12:19] <popey> dpm: 22:00 UTC tonight
[12:20] <dpm> ah, cool, better than a meeting on April 1st ;)
[12:20] <popey> heh
[12:28] <popey> pmcgowan: do you know if we plan to address https://bugs.launchpad.net/ubuntu/+source/click/+bug/1358294 soon?
[12:28] <popey> ah, there's a merge, missed that.
[12:35] <pmcgowan> popey, wow thats a controversial bug
[12:35] <mihir> popey: ping !!
[12:35] <pmcgowan> was unaware of it
[12:35] <popey> pmcgowan: yeah :S
[12:35] <popey> mihir: heya!
[12:35] <mihir> popey: could you confirm this ,it works fine on my side , https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1438946
[12:36] <popey> mihir: bet I know what this is.
[12:37] <popey> mihir: it's the fact that the all day event indication in the app points to the middle of the screen - we have a bug for that already
[12:37] <popey> mihir: so people think it was scheduled on wednesday because that's in the middle of the screen
[12:38]  * popey comments on it
[12:38] <mihir> popey: so the thing is it stores details on correct time zone right ?
[12:38] <popey> mihir: the data is stored correctly is my theory
[12:38] <popey> mihir: but the popup points to the middle of the screen, which is where wednesday is
[12:39] <mihir> okay gotcha
[12:39]  * popey marks incomplete
[12:39] <mihir> popey: thanks :)
[12:39] <popey> np
[12:40] <popey> mihir: unless it's related to https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437305
[12:40] <mihir> popey: we don't have functionality of imporing multiple calendar right?
[12:40] <popey> not yet
[12:41] <mihir> popey: should I mark it Wishlist?
[12:41] <popey> yes
[12:41] <popey> thanks
[12:42] <popey> pmcgowan: looks like mvo intended to land it, but it didn't yet.
[12:44] <t1mp> popey: I don't know
[12:44] <t1mp> zsombi: any idea?
 t1mp: do you know if we have a toolkit bug tracking the fact that a focussed field (in a big list of fields) is offscreen/obscured by osk?
[12:44] <t1mp> zsombi: ^
[12:45] <zsombi> t1mp:  ?
[12:45] <pmcgowan> popey, yeah thats not ready to land
[12:46] <zsombi> t1mp: I think we have, and the fix is not trivial
[12:46] <zsombi> t1mp: I think OrientationHelper has support for that, but nothing else...
[12:48] <popey> DanChapman: ^
[12:48] <DanChapman> bah so no autofocusing textfields anytime soon then
[12:48] <popey> zsombi: t1mp it hurts us with apps like dekko which have a manual settings screen which is a big list of fields to fill in
[12:48] <popey> so you have to manually pull the screen around to get to the next one
[12:49] <zsombi> popey: I do get that, but in order to fix this it is not enough that toolkit provides something, apps must at some extent rewrite teir views
[12:51] <zsombi> popey: but we can prioritize and work on it, but it may need a huge change all over
[12:51] <t1mp> zsombi: do we have documentation that describes what needs to be done to make it work?
[12:54] <zsombi> t1mp: I don't think so, because noone had enough time to investigate that. All we agreed is that pages must be implemented with a scrollable view, even if they don't need to scroll, otherwise OSK cannot push teh content upwards
[12:55] <zsombi> t1mp: in any other case, offsetting the content may be painful, and may cause UI hickups, especially if someone uses Flow or whatever
[12:56] <zsombi> t1mp: and OSK cannot detect anything, it's the UI which is showing teh content can do the job
[12:56] <zsombi> t1mp: and therefore this would work only if people use a given component as content holder, like Page, or whatever
[12:57] <t1mp> zsombi: and the Page must have a flickable inside it?
[12:57] <zsombi> t1mp: yes
[12:57] <t1mp> zsombi: I think most apps are using Pages
[12:57] <t1mp> but it doesn't have a flickable in it by default
[12:58] <zsombi> t1mp: or moreprecisely a component which connects to OSK
[12:58] <zsombi> t1mp: and it is flickable
[12:59] <zsombi> t1mp: however, the scrolling depends on the focus component, and it must be a text input...
[12:59] <t1mp> it is not just textfields right? basically we want any component that gets focus to automatically go into the view
[13:00] <zsombi> t1mp: in a sense yes, if we think of component navigation, yes, any component should stay in the view, but text inputs should be pulled upwards when OSK appears, and that's a different use case
[13:03] <t1mp> zsombi: we should write down the steps needed to get this done so we can include that in the next sprint planning discussion
[13:03] <zsombi> t1mp: good idea, go for it :)
[13:03] <zsombi> t1mp: make a card and a gdoc
[13:04] <zsombi> t1mp: actually we have a bug at least for it as well, so you can even link to it
[13:04] <t1mp> which bug is it?
[13:06] <zsombi> t1mp: dunno by heard, it is about the OSK and text input
[13:06]  * zsombi goes offline
[13:09] <t1mp> popey: we have this bug https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1200371
[13:09] <t1mp> zsombi: I happroved https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/01-multiple-theme-engines/+merge/251942
[14:11] <mhall119> Mirv: ping
[14:14] <dobey> yay, docs page isn't loading because code.jquery.com is apparently borked :-/
[15:06] <mcphail> Will the Ubuntu-SDK get included in the base distribution any time soon? It seems stupid to have it in a PPA, thereby making updates tricky and breaking the repository model.
[15:07] <ogra_> no, it is clever to have it in a PPA
[15:07] <mcphail> ogra_: for update frequency?
[15:07] <ogra_> else you have to lock it down at some point and it cant move forward anymore
[15:07] <ogra_> you would have to make SRUs for every change ... lots of paperwork, very slow
[15:08] <ogra_> a PPA can just keep rolling
[15:09] <mcphail> ogra_: I'm not sure rolling is such a good thing. A stable platform with stable target (+ next devel target) would seem sensible
[15:09] <ogra_> how would you get "next devel target" in ..., how would you get it stabilized for "next ..."
[15:10] <mcphail> ogra_: there was discussion about frameworks yesterday. I accept the current model wouldn't work well, but if the framework for "next" was finalised further in advance it could become a stable target
[15:12] <mcphail> ogra_: I know you guys are comfortable with development on the bleeding edge, but for amateurs like me it is quite hard to keep up with the next fresh thing
[15:13] <mcphail> ogra_: when vivid releases, I'd like to be able to say "I can now get an app ready for release on vivid+1. Here is the SDK. Here are the design guidelines for that release. I'll have it looking good for vivid+1 when vivis+1 is released"
[15:14]  * mcphail is a bit conservative
[15:34] <mcphail> Can anyone point me to an open source repo for an app/game using SDL2 on ubuntu-touch?
[15:34] <popey> mcphail: sturmflut-work made a simple one I think
[15:36] <mcphail> popey: thanks
[15:36] <popey> https://github.com/Sturmflut/sdi-ss12
[15:39] <mcphail> popey: don't think that is the right one :)
[15:40] <popey> yeah
[15:40] <popey> somewhere round there
[15:40] <mcphail> aah - I see his ubuntu-touch-sdl-template. Sounds perfect
[15:43] <popey> thats the one
[15:43] <mcphail> cmake is beyond me so a template is great
[15:44] <ogra_> mcphail, sorrym had to drop off into a meeting ... wrt your last sentence, how would you get the vivid+1 framework into vivid ?
[15:44] <ogra_> it doesnt exist by release day
[15:46] <mcphail> ogra_: yes - that's why I was saying the current model wouldn't fit with my suggestion. I think it would be good to have the stable SDK and design guidelines for the next release in advance. But, as I said, I'm rather conservative
[15:47] <ogra_> the prob is that people would use LTS ... for the next two years you couldnt really move forward with the frameworks
[15:47] <ogra_> until the next lts
[15:47] <ogra_> thats a way to low frequency for the phones
[15:47] <ogra_> (which are on a rolling release)
[15:48] <mcphail> ogra_: I see your point
[15:48] <ogra_> the right solution is to simply lift *everything* to rolling releases ;)
[15:49]  * mcphail hears the Ubuntu devs having a collective myocardial infarction
[15:50] <ogra_> well, that will eventualyl happen :)
[15:50] <ogra_> snappy brings us rolling releases
[15:50] <mcphail> I'll charge the defibrillator
[15:50] <ogra_> and snappy is the future of ubuntu
[15:51] <mcphail> snappy does look very nice
[15:51] <ogra_> yep, over time it will become the base for everyhting
[15:51] <ogra_> from phone to server
[15:52] <mcphail> and would let me package things without the ubuntu SDK, which would be nice. I don't understand click and cmake well enough
[15:52] <ogra_> i never used the SDK ... and i have plenty of click packages ;)
[15:52]  * ogra_ does everyhing in vi 
[15:52] <mcphail> ogra_: yes - I prefer vim and autotools for builds
[15:53] <mcphail> ogra_: or vim and ant for android
[15:53]  * ogra_ prefers vim and interpreter languages ... silly compiling ... 
[15:54] <mcphail> ogra_: it would be great if you could point me to a HOWTO for command-line builds for Ubuntu
[15:55] <ogra_> i think there is one in the examples on developer.ubuntu.com
[15:55] <mcphail> I'm trying to cheat and avoid learning about click. I can't wait for snappy
[15:55] <ogra_> snap and click are not to far apart ...
[15:56] <ogra_> snap adds just extra stuff on top (like service files and systemd integration)
[15:56] <mcphail> maybe I can backport what I've learned...
[16:24] <bzoltan> ogra_: thanks for the promotion dude :) good job
[16:24] <ogra_> haha
[16:27] <nik90> ogra_: You don't use the SDK.!!!.how dare you :P
[16:28] <ogra_> lol
[16:29] <bzoltan> nik90:  specially that ogra_ knows very well my irc highlight settings :D
[16:30] <ogra_> nik90, i'm even worse ... i usually create a click package with only a Main.qml file in it ... install that on the phone and do all my development in /opt/click.ubuntu.com/ :)
[16:31] <nik90> ogra_: stop talking..you are killing me....Next you might say you do all your development in VIM and admit to never using the super awesome Qtcreator
[16:31] <nik90> bzoltan: rofl
[16:32] <ogra_> nik90, yeah, havent found a way to get QTCreator working inside a ssh session on the phone yet :P
[16:33] <nik90> ogra_: I don't know...I can't live without the autocompletion that qtc offers..its just too good to give up :D
[16:33] <ogra_> i cant live without vim shortcuts and macros :)
[16:35] <nik90> ha..I guess that's where we hit our blockade :) .. LOTR: YOU SHALL NOT PASS!
[16:35] <ogra_> heh
[16:36] <ogra_> when i write office docs i always have to delete the ":wq" everywhere in them :)
[16:39] <mcphail> that's been my biggest problem using the IDE. But I think you can turn on vi keybindings somewhere...?
[16:39] <ogra_> probabyl
[16:40] <mcphail> I was stuck in vim.tiny on the phone yesterday: couldn't work out how to send <Esc>
[16:40] <ogra_> ctrl-c
[16:41] <ogra_> works the same
[16:41] <mcphail> yes - someone gave me that tip!
[16:44] <ogra_> there is also a vim keyboard profile for the terminal
[16:44] <ogra_> i think that adds an esc key
[16:46] <mcphail> aah - that profile button is neat. I hadn't noticed it
[17:15] <bzoltan> ogra_: I had the on device development feature in the QtC :) i was explicitly asked to remove it :)
[17:16] <ogra_> bzoltan, yeah, so the cool kids can show off with it now :)
[17:16] <bzoltan> ogra_:  if they find it :)
[17:16] <ogra_> heh
[17:17] <bzoltan> ogra_:  actually I am more into vi too... and yes I do type :wq even in google docs sometimes
[17:17] <ogra_> haha, yeah
[17:17] <ogra_> happens to me all the time
[17:19] <bzoltan> ogra_:  actually teaching QtC to do real on device development and to use the tools on the device and edit the code on the device would not be a big deal. but I am afraid that our device is not so hackable by default.
[17:23] <AlanBell> https://github.com/GNOME/file-roller/pull/1 given that is pull request #1 I am fairly confident that this isn't the way to fix gnome stuff
[17:23] <AlanBell> ooh, wrong channel
[18:14] <mihir> popey: if you get time to test small patch , https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/1438910/+merge/255123
[18:17] <popey> mihir: will do
[18:18] <mihir> popey: thanks :)
[18:19] <popey> mihir: i dont see the option...
[18:19] <mihir> of ?
[18:19] <popey> mihir: http://imgur.com/OPLlBBK
[18:20] <popey> should I not see monthly/yearly there?
[18:20] <mihir> popey: scroll down :D
[18:20] <popey> haha, thats totally not obvious!
[18:20] <popey> :)
[18:20] <mihir> i meant scroll the dropdown :| i can make that change if that is required too :d
[18:20] <mihir> yes i got that too :D
[18:20] <popey> I _never_ knew that was scrollable
[18:20] <mihir> or we should show some scroll over there
[18:20] <popey> we need to make that bgger i think
[18:20] <popey> *bigger
[18:20] <popey> as it's a separate screen, not a popover
[18:21] <mihir> hm okay i'll do that in separate    MR
[18:21] <popey> ok
[18:21] <popey> thanks mihir
[18:21]  * popey leaves for the weekend
[18:21] <popey> o/
[18:28] <mihir> popey: enjoy happy easter :P
[19:15] <renato___> popey, could you test the silo 30, it should fix the bug: #1438662
[19:53] <blocage> hello, I want to create a new window belong the main window within nux and draw something inside, someone can help ?
[19:54] <blocage> I also want to use this new window as dropdown menu :)
[23:46] <popey> renato___: will do.
[23:49] <ahoneybun> 525 downloads popey
[23:49] <popey> :)