[05:45] <zsombi> good morning everyone!
[09:28] <nerochiaro> oSoMoN: can you please take this MR, it's been pending for a couple weeks now: https://code.launchpad.net/~amanzi-team/notes-app/notes-app-click-collapse/+merge/164926 or someone else
[09:31] <oSoMoN> nerochiaro: sure, if you take https://code.launchpad.net/~osomon/webbrowser-app/focus-fix-suggestions-list/+merge/166862 :)
[09:31] <nerochiaro> oSoMoN: if i can test on desktop. i just realized i had forgotten my phone at home (at the makerspace now)
[09:32] <oSoMoN> nerochiaro: yep, there’s a bug report associated to the MR, and it’s fully reproducible on desktop
[09:32] <nerochiaro> oSoMoN: i'm on it
[09:32] <oSoMoN> thx
[09:32] <oSoMoN> I’ll be on yours in a moment
[09:45] <nerochiaro> oSoMoN: a couple tests failed for me on desktop after merging your MR. haven't tried before but i suspect it's not your MR fault. trying again
[09:45] <oSoMoN> nerochiaro: ok, thanks
[09:45] <oSoMoN> nerochiaro: note that CI tests passed in jenkins
[09:45] <nerochiaro> oSoMoN: yeah, that's probably more reliable
[09:46] <nerochiaro> oSoMoN: i also need to upgrade packages, i might be out of date on webkit or some other library
[09:56] <nerochiaro> oSoMoN: it looks like the failing tests is the built in web server failing to respond for some reason
[09:57] <oSoMoN> nerochiaro: that’s weird
[09:58] <oSoMoN> nerochiaro: when you run those failing tests individually, do they fail as well?
[10:03] <nerochiaro> oSoMoN: trying
[10:04] <oSoMoN> nerochiaro: I’m still seeing some random failures from time to time in the browser’s autopilot tests, I need to improve their robustness, it’s a general background task that’s been on my list for quite some time
[10:07] <dpm> bzoltan, zsombi, Kaleo_, could one of you provide some guidance on implementing the new visual theme for the clock app to nik90? We just got the visuals from design (https://code.launchpad.net/~jounihelminen/ubuntu-clock-app/designs), and while he's read the Theming API docs, he wasn't too clear on where to start.
[10:08] <nerochiaro> oSoMoN: the funny thing is that now i ran them again, some random ones gave you exceptions like this http://pastebin.ubuntu.com/5728884/ but the overall result of the test run was "OK"
[10:08] <nerochiaro> oSoMoN: these exceptions seem  to be totally random
[10:11] <oSoMoN> nerochiaro: those exceptions are harmless
[10:22] <nerochiaro> oSoMoN: ok, then i think i'll just approve your MR, all seems good. what about mine ?
[10:22] <oSoMoN> nerochiaro: it’s the connection between the server and the client dropping for some unknown reason (maybe a bug in the server side part in python), but the connection is resumed
[10:22] <oSoMoN> nerochiaro: reviewing it now
[10:26] <oSoMoN> nerochiaro: this needs to be tested on the device, right?
[10:26] <nerochiaro> oSoMoN: yes, it's a touch issue
[10:27] <oSoMoN> nerochiaro: so why was there this "pressedAtY" property in the first place, was it addressing a specific issue?
[10:29] <nerochiaro> oSoMoN: it was put there because intercepting the onclicked was conflicting with a flickable IIRC, so i had to capture the press and release events instead. but now the other flickable is gone so i can just use click
[10:29] <oSoMoN> nerochiaro: ok, makes sense
[10:29] <oSoMoN> nerochiaro: the code looks good, I’ll test on the device
[11:00] <Kaleo_> dpm: don't use themeing
[11:00] <Kaleo_> dpm: it's not meant to be used by app developers
[11:01] <Kaleo_> dpm: let's see what it looks like
[11:08] <dpm> Kaleo_, thanks. Here are the visual designs: lp~jounihelminen/ubuntu-clock-app/designs even just a few bullet points on how to implement them would help nik90 and the clock team enourmosly
[11:09] <oSoMoN> nerochiaro: approved your MR
[11:10] <Kaleo_> dpm: checking
[11:14] <nerochiaro> oSoMoN: if there's an app that has a qml plugin (e.g. for componentizing the browser) do you know if the .mo files (for i18n) have to be installed by the qml plugin or by the app ?
[11:17] <Kaleo_> timp: can you be my reviewer for https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/smaller_xlarge_font/+merge/167020 please?
[11:18] <Kaleo_> dpm: ok, it's going to require a bit of work in the toolkit
[11:19] <nik90> Kaleo_: will those work be done by the sdk dev or do the core app devs?
[11:19] <dpm> Kaleo_, is this work already tracked in a blueprint, or could we track it somewhere (e.g. bugs)?
[11:19] <oSoMoN> nerochiaro: well if some of the components in the plugin have translatable strings, then the mo files should be installed by the plugin
[11:20] <nerochiaro> oSoMoN: looks like both the main app and the plugin have them, so i guess we need to build a separate set of .mo and install from both
[11:20] <nerochiaro> oSoMoN: also i'm unsure about the .qmltheme file. because it should belong to the plugin but it's loaded by the main
[11:21] <Kaleo_> dpm: hang on :)
[11:21] <Kaleo_> dpm: just started thinking
[11:22] <Kaleo_> nik90: sdk dev
[11:22] <Kaleo_> nik90: it should be very simple for app devs
[11:51] <dpm> Kaleo_, how is that thinking going? ;)
[11:55] <oSoMoN> nerochiaro: the qmltheme file will go away very soon, so don’t worry about it
[11:56] <nerochiaro> oSoMoN: ok great
[12:14] <Kaleo_> dpm: interrupted by a meeting :)
[12:15] <Kaleo_> dpm: still ironing some things with jouni
[12:15] <Kaleo_> dpm: I'm pretty sure it will end up being something like: app dev needs to pass 2 colors and the rest is done for him
[12:15] <nik90> Kaleo_: that is nice to know
[12:16] <oSoMoN> Kaleo_: hey, could you please confirm bug #1186968 ?
[12:16] <ubot2> Launchpad bug 1186968 in Ubuntu UI Toolkit "Need a way to expose and access common colors for a theme" [Undecided,New] https://launchpad.net/bugs/1186968
[12:16] <nik90> Kaleo_: I was told by Jouni to talk to you about UbuntuShape.
[12:16] <nik90> Since the new UbuntuShape allows to create a circle
[12:16] <nik90> However I cannot find this in the docs at developer.ubuntu.com
[12:17] <Kaleo_> dpm: added there though: https://blueprints.launchpad.net/ubuntu/+spec/sdk-new-widgets
[12:18] <Kaleo_> nik90: it's not ready yet
[12:18] <Kaleo_> nik90: what kind of circle do you need though?
[12:18] <Kaleo_> nik90: do you have a mockup?
[12:18] <dpm> Kaleo_, excellent, and thanks for milestoning it
[12:18] <Kaleo_> oSoMoN: done
[12:19] <nik90> Kaleo_: its for drawing the clock face as shown in the mockups shared by david
[12:20] <nik90> Kaleo_: https://www.dropbox.com/sh/uzkr674j7zuglbn/jAEZkfnAAo
[12:20] <Kaleo_> nik90: ok, let's show that to loicm see if the new ubuntushape will do that
[12:20] <Kaleo_> nik90: but expect another couple of weeks before it's ready anyway
[12:20] <nik90> Kaleo_: oh ok.
[12:46] <GuidoPallemans> fuck me that looks good
[12:47] <GuidoPallemans> will these also be used as time pickers?
[12:47] <Kaleo_> nerochiaro: how do you run the notes app on your laptop?
[12:47] <nerochiaro> Kaleo_: "notes-app"
[12:50] <Kaleo_> nerochiaro: very funny
[12:50] <Kaleo_> nerochiaro: you install it system wide??
[12:52] <nerochiaro> Kaleo_: well, i do both. whe i want to run locally i run it as "qmlscene -I src NotesApp.qml"
[12:52] <Kaleo_> nerochiaro: thanks
[12:52] <Kaleo_> nerochiaro: that's what I needed
[13:23] <timp> Kaleo_: ok, I'll review
[13:23] <timp> Kaleo_: jenkins failed on https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/smaller_xlarge_font/+merge/167020
[13:29] <Kaleo_> timp: thanks, I pushed a fix
[13:31] <timp> Kaleo_: ok, I'll wait for jenkins to approve
[13:32] <kalikiana> dpm, ping
[13:32] <dpm> hi kalikiana
[13:33] <kalikiana> dpm, can you check out my last comment https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/navi/+merge/165617/comments/368434
[13:33] <dpm> sure
[13:34] <kalikiana> if you have a minute I'd like to quickly discuss what to do at this point
[13:34] <kalikiana> this is blocking on non-trivial qdoc bugs now…
[13:35] <kalikiana> or we can try to "avoid" them by changing our expectations
[13:46] <dpm> kalikiana, answered
[13:47] <dpm> let me know what you think. I'm about to enter a few hours of calls now, but we can discuss tomorrow morning or over the merge proposal
[13:53] <oSoMoN> zsombi: hey, when you have a moment could you please have a quick look at https://code.launchpad.net/~osomon/ubuntu-ui-toolkit/clear-button-0width-when-not-visible/+merge/167042, it’s a trivial one-liner MR to fix bug #1186247
[13:53] <ubot2> Launchpad bug 1186247 in Ubuntu UI Toolkit "[TextField] When unfocused, text should not be anchored to the left of the area of the clear button" [Medium,In progress] https://launchpad.net/bugs/1186247
[13:55] <zsombi> oSoMoNÉ checking...
[13:55] <loicm> nik90: looking at the mockup, I guess you'd like to use the UbuntuShape so that you can have nice looking inner and outer shadows, so yes you'll be able to use it in order to get nice shadows on top of a circle (ie shape radius of size width/2)
[13:55] <loicm> nik90: actually you'll need 2 shapes (looking at the mockups)
[13:56] <loicm> nik90: but that's perfectly fine
[13:57] <dpm> loicm, is this already possible with trunk?
[13:59] <loicm> dpm: nope, I'm currently working on a completely procedural ubuntu shape
[14:00] <nik90> loicm: yes I need UbuntuShape mainly for shadow and styling
[14:00] <nik90> loicm: when can we expect it to be ready?
[14:02] <loicm> nik90: I'm going to propose a demo for the end of the week, then we'll need to agree on the new API and on the integration, so you might be able to test a beta version in a week, but I'm not sure it will land exactly
[14:02] <loicm> +when
[14:04] <nik90> loicm: I am not sure if you saw the video, but in the video it also shows an animation where the radius increases and then decreases. Will this also be provided by UbuntuShape?
[14:05] <dpm> there: https://www.dropbox.com/s/zczjswik815ylxa/Clock_Motion_01.mp4
[14:07] <loicm> nik90, dpm: yes it will be supported
[14:08] <nik90> loicm: that's pretty cool
[14:09] <nik90> loicm: At the end of the day, it seems like the sdk devs are doing all the heavy lifting while app dev can use them in a much easy way for their apps.
[14:10] <loicm> nik90: that's our job ;)
[14:11] <nik90> loicm: :-) thnx
[14:14] <timp> Kaleo_: font-size MR approved
[14:18] <Kaleo_> timp: cheers
[14:19] <zsombi> oSoMoNÉ approved
[14:19] <zsombi> oSoMoN: ^ typo :)
[14:23] <oSoMoN> zsombi: I guess you meant "approuvÉ" :) thanks!
[14:24] <zsombi> oSoMoN: almost :) I had HUN layout active :)
[14:24] <gusch> nerochiaro oSoMoN renato_ up for a review? https://code.launchpad.net/~schwann/gallery-app/gallery-database-move/+merge/167036
[14:33] <gusch> renato_: I updated this MR https://code.launchpad.net/~schwann/gallery-app/gallery-modularity/+merge/166054
[14:35] <oSoMoN> gusch: I can put it in my list, but I can’t promise I’ll review it today
[14:35] <renato_> gusch, approved
[14:36] <gusch> oSoMoN: nerochiaro renato_ would be good to have this done rather early, as my next work will depend on it
[14:36] <gusch> renato_: thx
[14:37] <oSoMoN> man, that was fast
[14:37] <oSoMoN> ah, ok, not that one
[14:37] <renato_> oSoMoN, I approved the older one :D, not the new one
[14:42] <nerochiaro> Kaleo_: can we have a quick meeting today to talk about where to put these components for browser and media player ?
[14:43] <nerochiaro> Kaleo_: should've been a couple weeks ago but stuff got in the way ;)
[14:52] <Kaleo_> nerochiaro: how about tomorrow?
[14:52] <nerochiaro> Kaleo_: bill wants it done this week, and given my schedule the sooner i know the better
[14:53] <oSoMoN> timp, zsombi: how can I display a Tabs component with the usual header without having it inside a MainView?
[14:54] <timp> oSoMoN: the header is part of the mainview, so you cannot
[14:54] <zsombi> oSoMoN: No way if I'm not mistaken - as timp said
[14:54] <oSoMoN> bleh :/
[14:54] <oSoMoN> this is too restrictive
[14:54] <Kaleo_> nerochiaro: good, tomorrow
[14:54] <zsombi> oSoMoN: you don't like MainView?
[14:55] <Kaleo_> nerochiaro: unless you are willing to do it at midnight
[14:55] <oSoMoN> zsombi: afaik, MainView doesn’t allow me to have a custom toolbar, like I do for the browser
[14:55] <nerochiaro> Kaleo_: probably not, i don't have internet at my place yet or it would be ok
[14:56] <zsombi> oSoMoN: how custom you need there?
[14:56] <timp> zsombi: address bar, which we don't support yet
[14:56] <Kaleo_> nerochiaro: first thing tomorrow, send an invite for my 9am :)
[14:56] <timp> we don't support that in the standard toolbar I mean
[14:57] <zsombi> timp: so that cannot be done with th eaction hint?
[14:57] <nerochiaro> Kaleo_: ok busy man
[14:57] <oSoMoN> zsombi, timp: is the header delegate available for me to reuse, somehow?
[14:58] <timp> zsombi: itemHint could work, but currently the positioning is fixed
[14:58] <timp> oSoMoN: actually, the Header is not marked as internal in the qmldir file.. so you could use it
[14:58] <timp> not sure if that is a mistake
[14:59] <nerochiaro> Kaleo_: you should have an invite now, please confirm
[15:00] <oSoMoN> timp: cool, I’ll use it and then as it’s used by a core app you’ll have no choice but to leave it public. <insert evil laugh>
[15:02] <Kaleo_> nerochiaro: cheers
[15:04] <om26er> tmoenicke, Hey! which package to report bug for the OSK ?
[15:06] <timp> oSoMoN: uhm.. yeah. that would work for you :)
[15:07] <zsombi> timp: are you sure it's a good idea? I mean do we want to make it public?
[15:08] <timp> zsombi: no I'm not sure.
[15:08] <timp> oSoMoN: probably with that approach you will have to replicate some of the MainView functionality.
[15:09] <timp> zsombi: do you have a different solution that will work for the browser right now?
[15:09] <zsombi> timp: no, but I have the feeling that we do hacks just for someone's eyes instead of fixing the problem...
[15:09] <oSoMoN> zsombi, timp: I’m fine with not using it, provided you guys can provide me an alternative solution
[15:10] <tmoenicke> om26er: touch-preview-images
[15:10] <zsombi> timp: cannot the toolbar be made so it takes into account the itemHint's width/height?
[15:11] <timp> zsombi: I think it does. It just uses the whole item that's put in the itemhint
[15:12] <zsombi> timp: I don't get it then: browser has 3 components, 2 buttons and a TextInput...
[15:12] <timp> zsombi: it may be possible to use the itemHint for the textinput, but I haven't tried how to do it.
[15:12] <timp> zsombi: we could add a contents property to Toolbar, just like we did with Header, to allow custom contents instead of the one-button-per-action
[15:13] <oSoMoN> timp, zsombi: there’s some additional complexity: depending on the state, some of the buttons may be shown/hidden
[15:13] <timp> oSoMoN: the automatic buttons are created from the actions of the Page, and each Action has a visible property that you can use for that.
[15:13] <oSoMoN> timp, zsombi: also, I’d need the header to never be visible when browsing
[15:14] <oSoMoN> timp: ok, good to know
[15:15] <timp> oSoMoN: there is a bug right now https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1177123 that messes up the automatic placing of the buttons when some are invisible, but that will be fixed
[15:15] <ubot2> Ubuntu bug 1177123 in Ubuntu UI Toolkit "Toolbar actions buttons are not placed dynamically" [High,New]
[15:24] <timp> zsombi: there is a proposal to not have itemHint in the new Action APIs (since itemHint cannot be passed over dbus)
[15:24] <timp> zsombi: in case you are interested, here is the doc https://docs.google.com/a/canonical.com/document/d/1GVw0jQfvdhG-xkL6HAb7EJdpQlb32Q2-JlBLy2slsF4/edit?disco=AAAAAF1brgI and we have a meeting in 35m
[15:25] <oSoMoN> timp, zsombi: so I managed to use the Header component directly with Tabs: http://pastebin.ubuntu.com/5729625/, but how do I enable tab switching through the header?
[15:27] <timp> oSoMoN: assign Tabs.__headerContents to Header.contents
[15:27] <timp> some stuff that relies on MainView (such as propagation of toolbar property) will break.
[15:27] <timp> well you don't use the toolbar, so maybe you are lucky
[15:29] <zsombi> timp: sorry, was on hangout
[15:30] <zsombi> timp: but do we have to pass every property of Action through dbus?
[15:30] <oSoMoN> timp: works nicely, thanks!
[15:31] <timp> zsombi: the suggestion was to allow to add the component directly in the list of actions instead
[15:32] <timp> zsombi: so tools: ToolbarActions { Action { }; Button { action: Action { } }; }
[15:32] <timp> for example
[15:32] <zsombi> uhh...
[15:33] <timp> I gotta go now, back in 30m for Action meeting.
[15:33] <timp> zsombi: I can discuss it with you when I'm back if you are still around, otherwise tomorrow?
[15:33] <zsombi> timp: maybe tomorrow...
[15:33] <timp> ok
[15:34] <timp> zsombi: I am not convinced of that change yet, so I may not be the best person to convince you ;)
[15:34]  * timp bbl.
[15:57] <mhall119> FYI, anybody interested in beta-testing Discourse, we now have an application-development category for topics: http://test.ubuntu-discourse.org/category/application-development
[15:57] <mhall119> dpm: ^^
[15:57] <dpm> nice mhall119 :)
[16:05] <GuidoPallemans> bug: http://test.ubuntu-discourse.org/t/getting-started-with-app-development/174 contains a typing error
[16:14] <GuidoPallemans> oh, that's not actually part of discourse
[17:05] <demonoid_me> hi to all guys!
[17:05] <demonoid_me> i have samsung galaxy ace 2
[17:05] <demonoid_me> it is possible to install ubuntu on this device?
[17:08] <demonoid_me> becouse i develope apps for android phones
[17:09] <nerochiaro> timp: Kaleo_ : zsombi: do you guys know how to do i18n for libraries ?
[17:09] <nerochiaro> oSoMoN: ^
[17:09] <nerochiaro> timp: Kaleo_ : zsombi: oSoMoN: i have found examples for apps, but not for libs yet
[17:12] <Kaleo_> nerochiaro: what's youro use case?
[17:12] <nerochiaro> Kaleo_: browser component
[17:12] <Kaleo_> nerochiaro: and I guess you mean doing it in instead of  QML
[17:12] <Kaleo_> nerochiaro: strike that last sentence
[17:12] <nerochiaro> Kaleo_: ok
[17:12] <Kaleo_> nerochiaro: ask timp torroow
[17:12] <Kaleo_> omorrow
[17:12] <Kaleo_> :)
[17:12] <nerochiaro> Kaleo_: ok
[17:14] <timp> nerochiaro: or now :)
[17:14] <Kaleo_> timp: yay
[17:14] <nerochiaro> timp: how do i do i18n for a qml library ?
[17:15] <timp> I don't fufully understand the question
[17:15] <timp> *fully
[17:15] <timp> sucky internet..
[17:15] <Kaleo_> nerochiaro: (you mean how to generate the translation file and how to load it?)
[17:16] <timp> nerochiaro: for cpp it is standard gettext
[17:18] <Kaleo_> timp: and don't do cpp if you can avoid it
[17:18] <Kaleo_> (which you can :))
[17:18] <timp> if you can avoid the cpp, then I don't understand the question
[17:19] <Kaleo_> timp: :)
[17:20] <timp> nerochiaro: I had a doc once https://docs.google.com/a/canonical.com/document/d/1rLQLvWLuUJxV8LMv5s4vX3cwnWzpnM_fnkdeFSVU4JE/edit#heading=h.tiwophvmzjhk but it is outdated
[17:20] <timp> dpm: ^ do you have newer documentation ready?
[17:21]  * dpm looks at doc
[17:21] <timp> it is old. and there are better tools than my script :)
[17:22] <timp> still it is not fully clear what nerochiaro wants
[17:23] <dpm> timp, nerochiaro, I created this for how the workflow should be, but Qt Creator still works a bit differently: https://docs.google.com/a/canonical.com/document/d/12fEDKGVlNAkeXQyNXUM8JcekYwfvN7brRG5m5a0a4Dk/edit#heading=h.vbkzlk3ri2wg
[17:23] <dpm> I need to run, will be back later
[17:23] <timp> dpm: great, thanks
[17:35] <nerochiaro> timp: i have a QML library (plugin) that has some strings in it. These strings need to be i18n'd
[17:35] <nerochiaro> timp: so that they can be translated. more clear ?
[17:36] <nerochiaro> timp: dpm: all documents you sent to me cover only applications, not libraries (plugins)
[17:40] <dpm> nerochiaro, ah, gotcha, so this is about internationalizing a C++ plugin, right? In that case, you'll need to use gettext, as the i18n.tr() functions cannot be used from C++. See bug 1182577 and the example app link in there
[17:40] <ubot2> Launchpad bug 1182577 in Ubuntu UI Toolkit "[i18n] Cannot use the i18n plugin in C++" [Wishlist,Confirmed] https://launchpad.net/bugs/1182577
[17:42] <nerochiaro> dpm: it's a QML plugin
[17:42] <nerochiaro> dpm: no c++
[17:42] <dpm> nerochiaro, in that case, that makes things easier:
[17:43] <dpm> - use the i18n.tr() function as you would do with an app
[17:43] <dpm> - set the i18n.domain explicitly
[17:43] <nerochiaro> dpm: and where do i install the gmo files ?
[17:43] <dpm> - Generally i18n.domain is the name of the app (or plugin, in this case)
[17:44] <nerochiaro> dpm: sorry, .mo files
[17:44] <dpm> nerochiaro, the same as with an app: /usr/share/locale/$LANG/LC_MESSAGES/$DOMAIN.mo
[17:45] <nerochiaro> dpm: ah, sounds simple enough .i'll give it a shot and let you know (prob tomorrow). thanks
[17:46] <dpm> nerochiaro, the only thing to bear in mind is to ensure that the library loads those files. That works for apps and should work for plugins, but the later has not yet been tested afaik
[17:46] <dpm> so you've got a nice opportunity for pioneering ;)
[17:46] <nerochiaro> dpm: any hints on how can i test it ?
[17:46] <timp> nerochiaro: as dpm says, the process is the same as with an app. You also set the domain, and in the app when you want to use the dictionary of the library, use i18n.dtr() to pass the domain
[17:47] <timp> app = app that uses your qml lib
[17:47] <nerochiaro> timp: i don't get it, why do i need to call i18n.dtr() and where do i need to call it ?
[17:48] <timp> hmm. maybe you don't need in most cases.
[17:48] <timp> but in your app, if you get a string from your lib, you need to use dtr.
[17:48] <dpm> timp, I think the i18n.dtr calls in the app using the plugin should not be needed
[17:49] <timp> dpm: yeah I just start wondering now, if the lib already returns the translated strings you don't need
[17:49] <dpm> timp, ah, yes, in those cases perhaps
[17:49] <timp> I was thinking userString = dtr(lib.getString(), libDomainName)
[17:49] <timp> for error messages
[17:50] <timp> but if lib returns the translated string you don't need it. so when do you ever need dtr()?
[17:50] <dpm> timp, when an app has several domains, for example, which is not usual
[17:52] <timp> nerochiaro: ok so forget everything I said about dtr() ;)
[18:25] <nerochiaro> timp: ok, done. forgotten. gotta go anyway
[18:25] <nerochiaro> timp: dpm: thanks for the help
[18:52] <odraencode> Hello :D