[06:35] <dholbach> good morning
[07:44] <dpm> hi Mirv, I've just sent you an e-mail with an issue the calendar devs are having with the qtjsondb package. Let me know if that gives you enough info or if you'd need me to put you in touch with the guy who reported the issue
[07:47] <Mirv> dpm: I think I understand the problem, the raring version of qtjsondb was built in a PPA where it didn't pick up the 5.0.2. rebuilding in qt5-proper.
[07:47] <Mirv> and I assume the guy has raring
[07:48] <dpm> Mirv, yeah, I think most of the core app devs are running raring
[07:48] <dpm> Mirv, is there a way to get the package to work for raring?
[07:50] <Mirv> dpm: yep, just a rebuild, should be fixed in about half an hour in qt5-proper
[07:51]  * dpm hugs Mirv
[07:51] <dpm> cool, thanks!
[07:53] <Mirv> no problem
[08:20] <JamesTait> Good morning all, happy Friday! :-D
[08:46] <oSoMoN> gusch: hey, would you have some time for reviewing https://code.launchpad.net/~osomon/webbrowser-app/disable-webview-when-activityview-visible/+merge/173156 ?
[08:47] <gusch> oSoMoN: ok
[08:54] <gusch> oSoMoN: approved
[08:55] <oSoMoN> gusch: thx
[09:21] <rafaelement> Hi guys! I need help with this snippet. i have a state change with a transition, but its animation doesn't work. can someone please tell me what i am doing wrong? http://pastebin.com/SxgZerE9
[09:23] <dpm> I'm not very familiar with animations, timp or kalikiana, perhaps you might be able to help rafaelement ^^ ?
[09:26] <rafaelement> :)
[09:49] <timp> rafaelement: I'm quite busy now, but I can have a look in an hour or so
[09:50] <timp> rafaelement: can you try to simplify your code? to have a small test program with the animations only?
[09:52] <rafaelement> i will do that
[09:52] <rafaelement> just a second
[09:57] <rafaelement> i reuploaded the simplified version to the previous link! thanks for your help.
[10:15] <Laney> how do I refer to an enumeration type in a property?
[10:15] <Laney> e.g. property ??? fillMode : Image.PreserveAspectCrop
[10:17] <Laney> https://qt-project.org/doc/qt-5.0/qtqml/qml-enumeration.html says it's not possible but is there some trick? I got a review comment asking me to make my types more specific.
[10:41] <timp> Laney: ask the reviewer :)
[10:41] <Laney> timp: Rather avoid pinging people if possible. :P
[10:43] <timp> I don't think you can tell qml that a variable is of "enumeration" type
[10:44] <timp> rafaelement: what is the url of your updated code? http://pastebin.com/SxgZerE9 is still not that basic; It needs includes, and I think in your case a very basic program with only two states and a transition between the two would be helpful
[10:45] <Laney> I'll just bounce it back on the review
[10:46] <Laney> I also got asked to link to Image's documentation for properties which are the same - is there a qmldoc way to do that or does it mean to link to the webpage?
[10:48] <rafaelement> timp: i left it that way because i think i may have nested the elements in the wrong way
[10:53] <rafaelement> timp: http://pastebin.com/f4ehyhUR simpler...
[10:53] <Laney> ah \l
[10:54] <timp> rafaelement: that qml just gives me a blank window with only a header
[10:55] <rafaelement> it uses ubuntu buttons... do you use them? for me it displays a window with a centered button. on click, it displays an overlay with a centered close button
[10:56] <timp> rafaelement: you shouldn not anchors.centerIn parent if the parent is a column
[10:56] <rafaelement> timp: what can i use then?
[10:58] <timp> maybe my local installation of the ui toolkit is broken..
[10:59] <rafaelement> timp: does it give errors?
[10:59] <timp> rafaelement: you can use left/right anchors or align horizontally, and also set the height
[10:59] <timp> rafaelement: sorry, I have a meeting now
[11:00] <oSoMoN_> gusch: remember yesterday how you asked me whether increasing the page load time for one given autopilot test to 10 seconds wouldn’t time out? well it turns out you were right… my bad, here is a MR that should fix it: https://code.launchpad.net/~osomon/webbrowser-app/increase-test-timeout/+merge/173183
[11:00] <gusch> oSoMoN_: ok - I think I can approve it right away :)
[11:01] <oSoMoN_> gusch: yes, I think it’s safe :)
[11:01] <rafaelement> timp: fine, i will try to be patient and ask again sometime or find  a solution
[11:31]  * oSoMoN gets out for lunch
[11:45] <gusch> om26er: for camera seems to have some random failing tests :( https://code.launchpad.net/~schwann/camera-app/camera-update-today-user-metric/+merge/173135
[11:46] <om26er> gusch, hey! looking
[11:46] <gusch> om26er: there was/is a config problem (fixed by mzanetti), but still I have random failing tests from time to time
[11:47] <gusch> om26er: ... on jenkins
[13:21] <oSoMoN> Kaleo_: ping
[13:22] <Kaleo_> oSoMoN: pong
[13:22] <Kaleo_> oSoMoN: was waiting for you to reappear :)
[13:22] <oSoMoN> Kaleo_: have you seen my MR that fixes the notes-app ? https://code.launchpad.net/~osomon/notes-app/new_theming_fixed/+merge/173139
[13:23] <Kaleo_> oSoMoN: yes, I don't get it
[13:23] <Kaleo_> oSoMoN: I don't see the type property used anywhere
[13:23] <Kaleo_> oSoMoN: only the type role in the model
[13:23] <oSoMoN> Kaleo_: in MixedEdit.setCurrentTextItem()
[13:24] <oSoMoN> Kaleo_: at the very end of the function, if (item.item.type [13:24] <Kaleo_> oSoMoN: well done
[13:24] <Kaleo_> oSoMoN: ok, happroved
[13:24] <oSoMoN> Kaleo_: :)
[13:24] <oSoMoN> Kaleo_: the thing I really don’t get is how the tests were passing before, as this is clearly a bug that was already there in the code
[13:25] <Kaleo_> oSoMoN: indeed
[13:25] <Kaleo_> oSoMoN: puzzling
[13:25] <Kaleo_> oSoMoN: this week was breakage week unfortunately.
[13:26] <oSoMoN> Kaleo_: but I can’t be bothered spending more time to investigate, as long as the app works again
[13:26] <Kaleo_> oSoMoN: indeed
[13:26] <oSoMoN> got other priorities
[13:28] <seb128> Kaleo_, hey ... "The default height of Button has changed as per design.", is there anyone specifically in design I should ping with screenshots/to ask opinion if I find the design changes to look weird?
[13:31] <oSoMoN> Kaleo_: with the new simplified theming infrastructure, can I style a ListItem.Header ?
[13:31] <Kaleo_> seb128: ask Rosie
[13:31] <Kaleo_> oSoMoN: no
[13:31] <seb128> Kaleo_, thanks
[13:31] <Kaleo_> oSoMoN: ListItems are still not themable
[13:31] <Kaleo_> oSoMoN: what's your need?
[13:32] <oSoMoN> Kaleo_: the latest visual design for the browser’s timeline view has the list headers with a different background color, but I think I know how to achieve that easily
[13:34] <oSoMoN> confirmed, making the item a rectangle and putting the Header inside it works
[13:34] <Kaleo_> oSoMoN: can you show me the mockup?
[13:37] <oSoMoN> Kaleo_: forwarded to you the visuals by e-mail
[13:38] <Kaleo_> oSoMoN: thx
[13:39] <Kaleo_> timp: I replied to your comments
[13:42] <timp> Kaleo_: I saw. The MR is not done yet, right?
[13:42] <Kaleo_> timp: there is only one remaining fix; the background color
[13:42] <timp> Kaleo_: PaletteValues is not documented yet
[13:42] <Kaleo_> timp: and that
[13:42] <Kaleo_> timp: indeed
[13:42] <Kaleo_> timp: how is the rest?
[13:43] <timp> Kaleo_: looks good. only the property names in PaletteValues are not intuitive for me. Documenting them may help there, or relating the colors to the colors used in http://people.canonical.com/~kaleo/themes.png
[13:44] <om26er> wow whats' wrong with jenkins, the change has already been merged in trunk but it also seem the merge proposal is still there
[13:45] <Kaleo_> timp: yes, I'm thinking that 1) we add textual doc to the properties
[13:45] <timp> Kaleo_: now each Palette has 20 colors, I'm not sure we need that many
[13:45] <Kaleo_> timp: 2) once design has a design guidelines page ready, we link to it
[13:45] <Kaleo_> timp: hmm, do youo see many redundancies?
[13:47] <timp> Kaleo_: I count only around 5 colors per theme, plus gradients but I didn't check for different opacities with the same color
[13:51] <Kaleo_> timp: http://pastebin.ubuntu.com/5846810/
[13:51] <Kaleo_> timp: your counting is odd
[13:51] <Kaleo_> timp: that's 8 colors
[13:53] <Kaleo_> oSoMoN: it might well be that should be the default design for list item header
[13:53] <Kaleo_> oSoMoN:  need to ask Rosie
[13:55] <oSoMoN> Kaleo_: ok, in the meantime I’ll go for a custom header component that embeds the default one, will be easy enough to replace with the default one in the future if needed
[13:58] <timp> Kaleo_: I missed the background and overlay colors. I don't see them listed in Themes.png
[13:59] <timp> Kaleo_: I was counting from that image
[14:02] <Kaleo_> oSoMoN: that's not cool
[14:02] <Kaleo_> oSoMoN: let's ask Rosie
[14:02] <Kaleo_> oSoMoN: and that way you don't have to do anything
[14:03] <Kaleo_> oSoMoN: aside from asking her
[14:18] <Kaleo_> timp: so what's your conclusion?
[14:22] <Laney> Halp - the toolkit started failing to build like this: http://paste.ubuntu.com/5846911/
[14:27] <timp> Kaleo_: I get the same. And Totals: 61 passed, 0 failed, 0 skipped
[14:27] <timp> 61 passed for trunk
[14:27] <Kaleo_> timp: ok, fixing
[14:27] <Kaleo_> timp: by removing, I think it's silly to check the colors
[14:28] <timp> ok
[14:29] <Kaleo_> timp: jenkins does not fail probably because it's that special folder for X11 tests that it probably does not run for lack of X11 (tests/unit_x11)
[14:29] <Kaleo_> timp: pushed
[14:29] <timp> Kaleo_: I see that this test is the only place where that property is checked to be part of the API
[14:30] <Kaleo_> timp: I guess that the only remaining thing is the documentation
[14:30] <Kaleo_> timp: no, components.api does that automatically
[14:30] <timp> ah but we have an API check now
[14:30] <timp> yes :)
[14:30] <Kaleo_> timp: thanks for your good review
[14:31] <Kaleo_> timp: ckpringle is writing up the colors docstrings as we speak
[14:32] <timp> Kaleo_: you have this still FIXME: 'background' does not come from design, do you plan to remove that in this MR?
[14:33] <Kaleo_> timp: nope
[14:33] <Kaleo_> timp: later
[14:33] <timp> ok
[14:34] <Kaleo_> timp: and if you want to have fun, check out https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/dark_gradient_themes
[14:35] <timp> Kaleo_: one last thing, did you test it with some apps on device? I have some custom versions of packages installed on my device so it is a bit of a hassle to test it
[14:35] <Kaleo_> timp: not really, only on desktop, but colors have not really changed much
[14:39] <Kaleo_> Laney: working now?
[14:39] <Laney> nope
[14:39] <Laney> reverting commits until I get to the one which caused it
[14:42] <seb128> Kaleo_, hum, the new toolkit daily broke button, they show as void space ...
[14:42] <seb128> Kaleo_, is that a known issue?
[14:43] <seb128> Kaleo_, unping :p
[14:43] <Kaleo_> seb128: reported, fixed, fix merged
[14:43] <Kaleo_> :)
[14:44] <seb128> Kaleo_, we just need it in saucy then ;-)
[14:44] <Kaleo_> yes
[14:44] <seb128> Kaleo_, did we get a test with the fix to make sure next time landing fails in such cases? ;-)
[14:46] <timp> Kaleo_: qmlscene -I works fine for trunk, I wonder what is causing the problem with the color_palette
[14:46] <Laney> hrm, it's my r576: https://bazaar.launchpad.net/~laney/ubuntu-ui-toolkit/crossfadeimage/revision/576
[14:48] <Kaleo_> timp: thinking
[14:48] <Kaleo_> Laney: :)
[14:48] <Laney> can you see anything wrong?
[14:49] <Laney> I can't see errors in the build log
[14:54] <oSoMoN> renato__, boiko: would one of you have time to have a quick look at https://code.launchpad.net/~osomon/webbrowser-app/update-tabsview-label/+merge/172972 and approve it? Günther was reviewing it, and it was pending input from Jouni, and I got the answer to the question, but it looks like Günter has left already…
[14:55] <boiko> oSoMoN: is it fine if I review it in a couple hours?
[14:57] <Kaleo_> oSoMoN: you should use UbuntuColors.orange
[14:57] <Kaleo_> oSoMoN: though it might break at some point..
[14:58] <oSoMoN> Kaleo_: true, but I’ll do the transition to UbuntuColors in one go over the whole code base, if you don’t mind
[14:59] <Kaleo_> oSoMoN: sure
[14:59] <Kaleo_> oSoMoN: I hope jouni thought about what it means for the color palette
[15:00] <Kaleo_> oSoMoN: ie. what color in the palette that should correspond to
[15:00] <renato__> timp, Kaleo_ , any plans for a combobox widget in the SDK?
[15:00] <oSoMoN> Kaleo_: I’m sure he did
[15:00] <Kaleo_> renato__: yes, well it depends what you mean exactly
[15:00] <timp> renato__: no but we have the ValueSelector
[15:00] <Kaleo_> renato__: do you have a screenshot?
[15:00] <Kaleo_> renato__: mockup..
[15:00] <timp> haha :) opposite answers
[15:01] <renato__> Kaleo_, yes give me a minute I will share it with you
[15:01] <renato__> Kaleo_, timp this is different from value selector
[15:01] <renato__> Kaleo_, I just sent a e-mail to you
[15:02] <renato__> Kaleo_, take a look on  "Ubuntu_Contacts_Profile_Edit_01.jpg"
[15:02] <oSoMoN> boiko: sure, there’s absolutely no rush, I just want to make sure it doesn’t bitrot while Günter is away
[15:02] <boiko> oSoMoN: ok, I'll handle it today still then
[15:03] <oSoMoN> thanks!
[15:04] <Kaleo_> timp: http://people.canonical.com/~kaleo/Ubuntu_Contacts_Profile_Edit_01.jpg
[15:04] <Kaleo_> renato__: so the thing lwon the left?
[15:05] <Kaleo_> renato__: where you can select the type?
[15:05] <renato__> Kaleo_, yes and in the bottom, where you can select the Ring tone and Text tone
[15:07] <timp> those in the bottom might be new visuals for the current valueselector
[15:07] <timp> but the other ones on the left cannot be done with what we have now
[15:08] <timp> did rosie/calumn approve these designs? they are the pattern police
[15:08] <timp> ;)
[15:09] <Kaleo_> renato__: I believe that nic is working on that
[15:10] <Kaleo_> renato__: confirming now
[15:10] <Kaleo_> renato__: who is your visual designer?
[15:10] <renato__> Kaleo_, christina
[15:10] <Kaleo_> renato__: I did not know Christina did visual design
[15:10] <Kaleo_> renato__: interaction design for sure
[15:11] <Kaleo_> renato__: but actually that's even better
[15:11] <Kaleo_> renato__: I really meant interaction designer :)
[15:11] <Kaleo_> nic-doffay: thanks!
[15:11] <Kaleo_> renato__: nic-doffay confirms
[15:12] <renato__> Kaleo_, nic-doffay , whe this will be ready to use?
[15:12] <renato__> *when
[15:12] <nic-doffay> renato__, as soon as the themes and one or two additional features are implemented, not to mention the documentation being done.
[15:13] <Kaleo_> renato__: and about the fact that the app is using the dark theme; you won't have to do much; you can develop with the light theme and next week the dark theme will land with for you the option to make it the theme the phone app uses
[15:13] <renato__> Kaleo_, great
[15:15] <Kaleo_> renato__: also for widgets that are not in the toolkit (custom widgets) you should use the theme color palette when possible so that your widget will respond appropriately to changes in the theme
[15:15] <Kaleo_> renato__: it's going to land in a couple of hours (the color palette)
[15:16] <Kaleo_> renato__: and I'll make an email next week
[15:16] <renato__> Kaleo_, ok thanks
[15:18] <timp> renato__, Kaleo_ the selectors at the bottom for ringtone and texttone are the the new style for optionselector (now named valueselector)
[15:18] <timp> so that needs no new component
[15:19] <timp> the other, "small" selectors on the left seem odd to me to have on a phone. what would it look like expanded?
[15:22] <renato__> timp, if nic-doffay  is already creating a new component I do not see the point of use the valueselector since
[15:22] <renato__> the components looks the same with different sizes
[15:24] <timp> I mean it IS a valueselector, just the naming changed in the design documents
[15:24] <timp> Option selector in this doc: https://docs.google.com/a/canonical.com/document/d/1cg9ruHiEpRynEr_Ipf39Z0MQINEWoChIN-d111yx-Qw/edit#
[15:24] <timp> and the visuals need to be updated in the UITK
[15:27] <renato__> timp, something that I notice on the valueselector (I do not is is already fixed) is that it does not scroll, for example if you the options is bigger than the screen is not possible to select a option that is not visible on the screen
[15:27] <nic-doffay> renato__, that's the first thing I'm implementing after the themes
[15:27] <nic-doffay> for the option selector
[15:28] <timp> Kaleo_: I built and installed color_palette UITK on tablet, and the unselected titles in the tabs header now have white text
[15:28] <timp> which is wrong
[15:31] <renato__> Kaleo_, something that I will need, ( I need to check with christina) is the file choose dialog , for change the contact avatar. What do you have in mind for that?
[15:33] <renato__> Kaleo_, forget about it, this probably will use the content picker
[15:34] <Kaleo_> timp: in what app?
[15:34] <timp> phone-app and gallery-app
[15:36] <timp> Kaleo_: and calendar-app; probably all
[15:38] <Kaleo_> timp: odd, I don't reproduce on the desktop
[15:38] <Kaleo_> timp: let me see
[15:40] <Laney> finally building again
[15:40] <Laney> hope it still works
[15:43] <renato__> Kaleo_, matt steven is the visual designer for the contact-app
[15:44] <Kaleo_> renato__: cool; don't know him
[15:49] <timp> Kaleo_: I tried with gallery-app on desktop, and it does not have the white titles
[15:49] <timp> Kaleo_: but in the tabs header, the chevron used to be the color of the unselected titles when the tabs header is active, that is no longer the case
[15:49] <timp> very subtle difference
[15:51] <Kaleo_> timp: right, so I'm testing on the device
[15:56] <Kaleo_> timp: for the subtle difference you noticed, I think we can live with it and I will fix it when I get to updating the visual design of the tabsz
[15:56] <Kaleo_> -z
[15:59] <oSoMoN> boiko: Günther approved my MR, no need for a review anymore
[16:00] <timp> Kaleo_: ok. I didn't know we would get new visuals for tabs
[16:00] <Kaleo_> timp: slight updates for everything
[16:01] <Kaleo_> timp:  i see the white tabs
[16:01] <Kaleo_> timp: on the phone
[16:01] <Kaleo_> timp: but I don't see any error message on the console!
[16:05] <odra> Kaleo_: What do you have against white tabs???
[16:07] <Kaleo_> odra: :)
[16:09] <Kaleo_> timp: I'm 99% sure I know
[16:10] <Kaleo_> timp: https://bugreports.qt-project.org/browse/QTBUG-32238
[16:12] <timp> ohh
[16:13] <timp> Kaleo_: in which file is headerTextColor defined now?
[16:13] <Kaleo_> timp: actually it's not that bug
[16:13] <Kaleo_> timp: in NewTabBar.qml
[16:13] <Kaleo_> timp: or it is...
[16:14] <timp> it used to be in the qmltheme
[16:14] <timp> yes, the property is defined there, but its value?
[16:16] <Kaleo_> timp: in TabsStyle.qml
[16:16] <timp> ok, found it in TabsStyle
[16:16] <odra> I feel isolated because everyone here seems to code for phone.
[16:21] <Kaleo_> timp: I'm lost: if I assing to the Label.color property in NewTabBar the value from the theme directly #81888888
[16:22] <Kaleo_> timp: then it's still broken & white
[16:22] <odra> #81888888?
[16:23] <odra> Isn't there two digits too many?
[16:23] <Kaleo_> odra: no
[16:23] <Kaleo_> odra: it's the alpha channel
[16:24] <odra> Which is?
[16:24] <timp> odra: the opacity
[16:24] <odra> I mean which digits :p
[16:26] <Kaleo_> odra: the firsts 2
[16:26] <Kaleo_> -s
[16:31] <Kaleo_> timp: alright, found the bug
[16:31] <Kaleo_> timp: http://pastebin.ubuntu.com/5847291/
[16:35] <timp> :s
[16:35] <timp> how come we never noticed that before?
[16:36] <timp> well in the tabs we had a separate opacity property, but in other places
[16:37] <Kaleo_> timp: maybe it works with Qt.rgba()
[16:38] <timp> Kaleo_: nope
[16:38] <Kaleo_> timp: nope
[16:38] <Kaleo_> timp: darn
[16:39] <Kaleo_> timp: the issue with qmlscene tests/resources/tabs/Tabs.qml
[16:39] <Kaleo_> timp: I think it's also in trunk
[16:39] <Kaleo_> timp: I pushed the docstrings for the propertiez
[16:39] <Kaleo_> +s
[16:39] <Kaleo_> timp: now digging in Qt's bug tracker for that color bug
[16:40] <timp> Kaleo_: color: "#81888888"
[16:40] <timp> ^ only fails for text
[16:40] <Kaleo_> timp:  ah ah
[16:40] <timp> for Rectangle it works fine
[16:41] <Kaleo_> https://bugreports.qt-project.org/browse/QTBUG-30246
[16:41] <Kaleo_> timp: but only on some platforms/architecture
[16:46] <Kaleo_> timp: so to summarize; there are only 2 issues left with the MR: this Qt bug we need to fix & this strange import path issue
[16:46] <Kaleo_> timp: right?
[16:46] <timp> yes
[16:47] <Kaleo_> timp: ok, so Monday then
[16:47] <timp> ok
[16:47] <Kaleo_> timp: oh hang on
[16:47] <Kaleo_> idea for a wrk around
[16:47] <Kaleo_> in Label.qml
[16:47] <Kaleo_> opacity: color.a
[16:49] <Kaleo_> timp: of course that's not enough
[16:49] <Kaleo_> timp: the color if cooked
[16:50] <Kaleo_> timp: ok, Monday
[16:50] <Kaleo_> timp: thanks for you help
[16:51] <timp> yw
[17:13] <surgemcgee> Does the tools toolbar iconSource use a units.gu() like resize method?
[17:34] <AskUbuntu> Ubuntu touch apps don't open on Desktop 13.04 | http://askubuntu.com/q/316760
[22:26] <AskUbuntu> Programmatically Present Windows (Invoke Window Picker) in Compiz | http://askubuntu.com/q/316857
[23:42] <AskUbuntu> Possible to download packaged deb file before final publishing on myapps portal? | http://askubuntu.com/q/316890