=== JanC_ is now known as JanC === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:26] does anyone know how to use the Window API from QtQuick.Window 2.2. When I use it, I cannot see any window created in the app. thanks [11:09] dpm: hello there, I'd like to add a new tutorial page to the d-u-c, can I do it myself? [11:11] dpm: do I simply go to d-u-c QML tutorials, and add a new sub-page? [11:27] zsombi, sorry, I was on the phone. Exactly, davidcalle can help you with getting set up [11:28] dpm: davidcalle: ok, I navigated to the Tutorials page, then created a sub-page... still editing [11:28] ok, great [12:22] dpm: davidcalle: guys, I have a small issue in this page https://developer.ubuntu.com/en/ubuntu-ui-toolkit-palette/ [12:23] in the first table, the last column's cell background color should be set to the proper color [12:23] I tried with but that doesn't seem to work... [12:24] davidcalle, I think the web guidelines don't support that and a regular html table with the raw html plugin should be used? ^ [12:25] dpm: davidcalle: basically that's the only issue which is left from me publishing it... [12:30] faenil: I think I made it :) [12:32] faenil: ah, sorry, not you, I meant dpm :) === _salem is now known as salem_ [12:36] dpm: seems davidcalle is not around... interestingly, even if I created the tutorial page as subpage while I was in https://developer.ubuntu.com/en/apps/qml/tutorials, the URL I got is by far from being relative to that location... is that intended? [12:48] dpm: ok, managed to get it out, so th epalette tutorial is available for the audience! https://plus.google.com/+ZsomborEgriCanonical/posts/5qQ8uKmh4ah [12:59] zsombi, sorry, just got back from lunch. Great to hear you figured it out! === chihchun is now known as chihchun_afk [13:13] dpm: we still seem to have issues.... we got reported that from the three images in the tutorial, only two can be seen... I've insetred these last two ones as a PNG file, published teh changes, but the tutorial still has the reference to the Googlke docs... [13:19] zsombi, I'm on a call, and I believe davidcalle too, but I will look at it in ~45 mins. Did you use the image plugin to upload the images to the site? [13:19] ok, sorted out this one as well [13:20] zsombi, you're too quick for us! :) [13:20] dpm: yes, I did it, and the images were still not updated, despite I published teh changes... [13:20] I did it again... and then they were out... [13:20] weird tool is this CMS... [13:22] zsombi: I'm in a call in 40 min, not right now :) So, there has been an upgrade of everything on the site last night, except the blog engine unfortunately, still stuck in the middle ages, what was the issue exactly? Did the image upload looked like it failed? [13:23] zsombi: oh, it's NOT the blog engine on your page, hmm [13:23] davidcalle: we are good with it seems... you can check the d-u-c QML -> Tutorials -> The Palette link, if everything is fine with it... [13:25] zsombi: what's not fine is the path of the page https://developer.ubuntu.com/en/ubuntu-ui-toolkit-palette/ (should be en/apps/qml/tutorials/) [13:26] zsombi: I'm going to make it a redirect to the right path [13:27] davidcalle: well... it's utmost weird that by creating a sub-page, while I'm in a page, it creates me the sub-page in a totally different place... [13:29] zsombi: yup. I'll see if I can reproduce it. [13:29] dpm: and one more post :) https://plus.google.com/+ZsomborEgriCanonical/posts/fiG2NVpA5e8 [13:35] zsombi: everything looks fine on this page? https://developer.ubuntu.com/en/apps/qml/tutorials/ubuntu-ui-toolkit-palette/ [13:36] As soon as you type "yes", your former URL will redirect to the correct one. [13:37] (We should have a "yes" bot that triggers actions) [13:39] davidcalle: "yes" :) [13:40] zsombi :) [13:55] zsombi: nice blog post [14:13] zsombi: we should spread the link of the palette post also on G+/mailing list/... [14:15] oh it is on G+ already :) [17:10] Good work zsombi! [17:25] kalikiana, nik90: I commented on https://bugs.launchpad.net/ubuntu-ux/+bug/1393485 [17:25] Launchpad bug 1393485 in ubuntu-ui-toolkit (Ubuntu) "[SDK] Need a standard way to make an Icon look disabled" [Medium,In progress] [17:29] timp, is that also the case for header actions now? IIRC we had to make then invisible rather than disabled now [17:30] ahayzen: they should be invisible, correct [17:30] ahayzen: the action has a visible property [17:30] before we did enabled=false [17:30] let me verify that [17:30] and after the UITK changes that broke so we had todo visible=false [17:30] but then the actions are less discoverable :-/ [17:31] ahayzen: right, I think the visible property should be used [17:31] ok :-/ [17:31] ahayzen: you have a point. Let's ask some designers [17:31] more context aware hidden items :-( [17:32] ahayzen: it might be eod for them already [17:32] hehe ok :-) [17:32] ahayzen: can you add a comment about it to the bug? [17:32] timp, ok will do :-) [17:33] thanks [17:37] kalikiana: so, icons in a button in a listitem? [17:37] kalikiana: so we need to decide in which of the three the opacity is changed? [17:37] timp: As the bug itself says [17:37] I guess at least the button would be 'greyed out', so that would put it in the button [17:37] or in the listitem [17:38] timp: "use an Icon inside a ListItem.Empty or any other AbstractButton derived class, and disable the item" [17:38] ok [17:39] so then the abstractbutton derived class should take care of it [17:39] timp: another question: why do you need to make the icon button translucent if the icon is already translucent? wouldn't it look the same? [17:39] kalikiana: a button can have an icon and text [17:40] kalikiana: if the text stays the same, and the icon becomes semi-transparent, it looks wrong to me [17:40] timp: so in other words we have the same problem with Label [17:40] timp: note that Label should rely on the palette, not opacity [17:41] kalikiana: right. And I just checked the icon buttons in the header, they rely on the palette, and the palette sets the colors for disabled to 0.3 opacity [17:41] timp, commented on that bug :-) [17:41] kalikiana: so in the header it is already fixed with the new palette [17:41] timp: and having the Icon change opacity would be what you want [17:42] kalikiana: setting the icon opacity to 0.3 as well when disabled will give icons in the header an opacity of 0.09, so I have to override the icon opacity there [17:42] kalikiana: the header foreground color gets 0.3 opacity when disabled. And the icon too. Those values are multiplied [17:43] timp: So the icon also uses the palette color? Presumably that will break with a custom color then. [17:43] color: UbuntuColors.green -> fail [17:43] kalikiana: no, the icon button in the header uses palette color [17:44] timp: Yes or no? [17:44] kalikiana: the icon does not use the palette color. But in the header button we use an icon and set its color to the palette color [17:44] timp: so yes [17:44] kalikiana: no, the icon doesn't use the palette [17:44] timp: it does in this case :-) [17:44] please don't give ambiguous answers [17:45] timp: so that means it will break if a custom color is used in a naive way [17:45] kalikiana: the Icon component does not use the palette [17:45] kalikiana: the header does use the palette [17:45] timp: which is exactly my point [17:45] timp: the Icon is assigned a color from the palette and the icon button relies on that, which will break with a custom color [17:46] kalikiana: in the header you have an ActionBar, which takes a list of Actions as input. Actions don't have a color [17:47] timp: unless you use a delegate [17:47] which can have a color [17:47] yes [17:47] if you explicity set a delegate that uses color: red, then it will be red. [17:48] and if the color does not check for "enabled", then it won't change its looks when it is disabled [17:48] s/color/delegate [17:49] timp: so if Button for example did change opacity, the result is wrong depending on whether you use the palette [17:49] same if Icon handled opacity [17:50] if the button takes colors from the palette it should not set the opacity, because the palette colors incorporate opacities already [17:50] I think either we need a smarter solution or leave it up to developers completely [17:51] timp: if Button is changing opacity automatically it cannot know what kind of color is being used [17:52] kalikiana: true. What's your point [17:52] if button uses the current palette correctly, the result will be wrong if it also sets the opacity [17:52] timp: My point is, regardless of anything else, the original idea of doing it in Icon, and doing it in other components, cannot work [17:53] kalikiana: so, we keep it as it is and only deal with it in the palette [17:53] I think the bug was reported with the old palette [17:54] timp: Right. The best answer might be to use the appropriate palette value depending on the state. Which we don't have a complete solution for yet. [17:54] (Complete as in, no one-line expression) [17:54] right [17:54] zsombi will fix it ;) [17:55] Should we nickname him snappy from now on? ;-) [18:58] kalikiana: so I will mark this bug as fixed: https://bugs.launchpad.net/ubuntu-ux/+bug/1393485 [18:58] Launchpad bug 1393485 in ubuntu-ui-toolkit (Ubuntu) "[SDK] Need a standard way to make an Icon look disabled" [Medium,In progress] [18:58] because the new palette solves it === chihchun_afk is now known as chihchun [19:00] kalikiana: I rejected https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/icon-disabled/+merge/289308 [19:01] ahayzen: for your issue with visible vs enabled, we'll need to discuss with the designers. But I think that won't be a bug in UITK since you can choose to use either visible or enabled. === daker_ is now known as daker === tedg_ is now known as tedg [19:58] hi everyone [19:59] found my misstake alone xD [20:20] Im trying to install ubuntu-sdk and get ready to learn a bit about creating scopes. But when I execute apt install unity-js-scopes-dev in the terminal it can't localize the package. Does anyone know what to do? === salem_ is now known as _salem [21:28] lasse, hi, which version of Ubuntu are you using?