[01:44] <jdstrand> popey: hey, I'm not sure what is going on with akari-- the upstream trunk has 0.1.3 but the store has 0.1.5. I just submitted https://code.launchpad.net/~jdstrand/akari/akari-fixes/+merge/240667 to upstream. if we are updating akari somewhere else, can we get that patch applied?
[04:09] <liuxg> does anyone know how to add some music tracks to my Nexus 4 device? Is there anyway to copy over via PC?
[08:48] <mihir> popey: ping , Morning
[08:48] <mihir> popey: i have responded on both the emails.
[09:15] <JamesTait> Good morning all; happy Stress Awareness Day! :-D
[09:22] <DanChapman> dpm, Good Morning :-) do i remember correctly, yesterady you said reminders ships it evernote account provider with the app? I'm trying to figure out what's needed to get an outlook.com provider setup, but there seems to be little documentation around this :-)
[09:49] <dpm> hey DanChapman, morning
[10:02] <dpm> DanChapman, sorry, got into another conversation. Yes, Reminders ships the Evernote account provider in the click package
[10:11] <dpm> hi penk, how are you getting on with the scope integration in Reminders? Have you had a chance to test https://code.launchpad.net/~mzanetti/reminders-app/libqtevernote/+merge/239496 ?
[10:11] <mzanetti> o/
[10:11] <dpm> hey :)
[10:13] <penk> dpm: hi, yes tested that against reminder-app, works, am working on the scope
[10:13] <penk> dpm: also lp:~reminders-app-dev/reminders-app/uriHandler works for me
[10:14] <mzanetti> penk: please add an "Approve" comment to those merge proposals then
[10:14] <mzanetti> dpm: just came across this one: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286
[10:14] <penk> mzanetti: ok
[10:14] <penk> dpm: is it possible we start our weekly meeting 15mins earlier?
[10:17] <dpm> penk, works for me. Let me ask mzanetti and rpadovani - would it work for you guys to start the reminders weekly meeting 15 mins earlier?
[10:18] <DanChapman> dpm right.. thanks :-) I'll go dig around reminders then and see how it's done
[10:19] <dpm> t1mp, I asked this question on askubuntu http://askubuntu.com/questions/545483/whats-the-difference-between-optionselector-and-itemselector - and now I noticed this comment -> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384726/comments/4 - do you have more insight on that?
[10:19] <mzanetti> dpm: worksforme
[10:21] <dpm> DanChapman, one thing to bear in mind is that the Reminders authentication plugin for Evernote is slighly more complex because it uses the Evernote API to get the account name. You can start simple and just create a plugin that uses oauth for authentication, it's just a bunch of files with little to no code at all (a Main.qml file you can get a template for from other online accounts in the system)
[10:22] <dpm> this might not give you the account name, but for starters it should easily get you going with creating the authentication plugin
[10:25] <penk> mzanetti: approved, thanks https://code.launchpad.net/~mzanetti/reminders-app/libqtevernote/+merge/239496
[10:26] <DanChapman> dpm, ahh ok great i'll take a look at the others aswell then. Thanks!! :-)
[10:26] <t1mp> dpm: I'd say it was a mistake that we have them both
[10:26] <t1mp> dpm: basically one is in Ubuntu.Components, and one in Ubuntu.Components.ListItems, and their visuals are slightly different
[10:27] <t1mp> zsombi: is anything like an itemselector planned for the new list items?
[10:28] <zsombi> t1mp: kinda yes, the ListItem.expansion is about to provide the base for that. However content must be given manually to have teh same things we have now in ItemSelector
[10:29] <zsombi> t1mp: perhaps we can provide a different ItemSelector which is based on ListItem and provides same template as the current ItemSelector... and a bit more flexible if possible ;)
[10:29] <t1mp> zsombi: okay, eventually we can ^W^W^W^W yeah what you just said :)
[10:33] <dpm> t1mp, so we should start telling app devs not to use OptionSelector and use ItemSelector instead?
[10:36] <t1mp> gventuri: good timing. There was some discussion about itemselector vs optionselector
[10:36] <t1mp> dpm: I think we will keep them both for now, until we have the new list items and then a new selector based on those, and then they will both become deprecated
[10:37] <t1mp> zsombi: ^do you agree?
[10:37] <zsombi> t1mp: I do
[10:37] <t1mp> good :)
[10:38] <dpm> hi gventuri, so to give you some more context, I asked this question to t1mp -> "I asked this question on askubuntu http://askubuntu.com/questions/545483/whats-the-difference-between-optionselector-and-itemselector - and now I noticed this comment -> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1384726/comments/4 - do you have more insight on that?"
[10:39] <zsombi> t1mp: fyi: I'm moving the panels (ListItemPanel, ListItemSelectionPanel) to the theme
[10:40] <zsombi> t1mp: in this way themes can provide different designs if needed
[10:41] <zsombi> t1mp: and subtheming will also be good with it ;)
[10:50] <rpadovani> dpm, is tomorrow, right? It's ok for me
[10:51] <dpm> cool, thanks rpadovani
[10:52] <dpm> penk, time changed to 15 mins earlier
[10:55] <t1mp> zsombi: hmm
[10:56] <t1mp> zsombi: I think we can land the basic new list items even before we review the panels
[10:56] <t1mp> zsombi: the panels are only the contents right?
[10:57] <zsombi> t1mp: no, the panels are the ones which provide the visualization o fthe actions...
[10:57] <zsombi> t1mp: so it's in teh base functionality of the list item
[10:57] <zsombi> t1mp: what you are talking about are the list item layouts
[10:58] <t1mp> ah
[10:58] <t1mp> yeah I got confused
[10:59] <t1mp> zsombi: I'd say the API to define the actions is part of the list item, and the panel itself the theme
[10:59] <zsombi> t1mp: that's what I'm after now, to move those things to teh theme
[11:07] <gventuri> dpm: Hi. Yes I confirm what I said on Launchpad ;-)
[11:15] <t1mp> gventuri: was there a conceptual difference, or do they just look different?
[11:16] <t1mp> gventuri: as zsombi and I discussed before, we will just keep both around for now. So I guess the design guidelines will just recommend the OptionSelector
[11:16] <t1mp> gventuri: as I see it, only the visuals are different now
[11:17] <zsombi> t1mp: gventuri: uhh, guys, pls decide where we go: OptionSelector always has a shape around the items, ItemSelector shouldn't have those...
[11:22] <gventuri> zsombi: t1mp: OptionSelector must go...
[11:22] <zsombi> gventuri: in or out?
[11:22] <zsombi> gventuri: or away?
[11:22] <gventuri> Going forward, we are not using the ubuntu shape to embed controls
[11:22] <gventuri> including time picker etc.
[11:23] <gventuri> away!!!
[11:23] <gventuri> zsombi: I assume ListitemSelector will have much better customisation options
[11:23] <gventuri> zsombi: as we discussed
[11:24] <zsombi> gventuri: oh, yes
[11:24] <gventuri> zsombi: cool
[11:24] <gventuri> zsombi: the optionSelector is dead for me
[11:24] <gventuri> zsombi: long live ItemSelector
[11:24] <zsombi> gventuri: thank you!
[11:25] <t1mp> gventuri: that sounds so mean
[11:25] <zsombi> gventuri: long live until further notice :D
[11:25] <gventuri> zsombi: and please let's keep the expansion in
[11:25] <zsombi> gventuri: I have it on my todo list
[11:27] <dpm> gventuri, zsombi, t1mp, does the answer to my own question look reasonable to you guys? http://askubuntu.com/q/545483/9781
[11:30] <zsombi> dpm: yes, until further notice :)
[11:32] <dpm> ok, thanks :)
[11:32] <t1mp> dpm: w.r.t. the ubuntushape, it is the opposite, in general we do NOT want to embed UbuntuShapes in the controls
[11:32] <t1mp> dpm: w.r.t. the ubuntushape, it is the opposite, in general we do NOT want to embed UbuntuShapes in the controls
[11:32] <t1mp> gventuri: ^ correct?
[11:33] <brendand> popey, when will this calculator update be available? https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1365564
[11:33] <dpm> t1mp, yeah, I meant that the plan going forward is to deprecate that. Let me rephrase it to make it clear
[11:33] <t1mp> dpm: or did you mean "deprecate (OptionSelector and embedding UbuntuShapes in controls)"
[11:33] <dpm> yep :)
[11:37] <zsombi> t1mp: oh, man, it feels so good to have the panels in teh theme ;)
[11:37] <t1mp> :)
[11:41] <zsombi> t1mp: that also means that we must move the backgroundColor/foregroundColor from ListItemActions to ListItem. The reason is that ListItem is the only styleable component so far. And it is more likely that ListItems want to visualize teh actions differently than to use a ListItemActions which has "hardcoded" visualization.
[11:44] <t1mp> zsombi: hold on..
[11:44] <t1mp> zsombi: the ListItemActions can be an API that is used for defining the actions, it doesn't have to have a hardcoded visualization
[11:45] <t1mp> zsombi: like the header's PageHeadConfiguration (page.head.config). It contains the actions, foreground color, ...
[11:45] <t1mp> but the visualization is completely separate
[11:59] <popey> brendand: let me take a look
[12:00] <popey> brendand: ah excellent, it landed...
[12:00] <popey> Mirv: could you please upload http://s-jenkins.ubuntu-ci:8080/job/calculator-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calculator_1.3.339_all.click to the store when you get a moment, thanks!
[12:02] <brendand> popey, in the meanwhile i'll just take that...
[12:02] <brendand> yoink!
[12:02] <popey> heh
[12:04] <dpm> hi akiva-thinkpad, thanks for proposing the sessions for the online summit next week. I see there you've filed a few - just to confirm, are you going to attend/drive the sessions you're proposing?
[12:05] <dpm> argh, a second too late
[12:05] <dpm> hi akiva-thinkpad, thanks for proposing the sessions for the online summit next week. I see there you've filed a few - just to confirm, are you going to attend/drive the sessions you're proposing?
[12:06] <zsombi> t1mp: yes, but right now the panel delegate is hardcoded in ListItemActions. What I'm doing I take that into ListItem, and that will take it from the theme
[12:08] <aquarius> I thought that if I had a Page containing a Column as the sole content of my MainView, then the SDK made sure that the content was scrollable for me?
[12:09] <nik90> aquarius: no, that would be a flickable or a listview
[12:09] <dpm> aquarius, I think you need to wrap it in a Flickable
[12:09] <nik90> not a column
[12:09] <aquarius> ok, I'll stick it in a flickable then
[12:09] <nik90> or what dpm said would work as well
[12:10] <akiva-thinkpad> dpm, ah yah; I'll have to double check
[12:10] <akiva-thinkpad> For go; I wanted to see if a go developer would come in and do a proposition. Its probably too late to do that now.
[12:10] <mivoligo> mzanetti: ping
[12:11] <dpm> akiva-thinkpad, I think the topics are really good, but before approving the session, we need to make sure that there is someone to run the session
[12:11] <akiva-thinkpad> yep; exactly.
[12:11] <mzanetti> mivoligo: hey
[12:11] <mivoligo> mzanetti: have a time?
[12:12] <mzanetti> mivoligo: hit me
[12:12] <mivoligo> mzanetti: I reported few bugs just now
[12:13] <mivoligo> mzanetti: also I put new UI for tower info dialog into the drive
[12:13] <mzanetti> mivoligo: nice :)
[12:14] <mivoligo> mzanetti: size of the current dialog is that you can see level pause dialog under it :)
[12:15] <mzanetti> hehe
[12:16] <mzanetti> cool, will fix those bugs and implement the design
[12:16] <mivoligo> mzanetti: :) great
[12:16] <mzanetti> mivoligo: for the adding tower I just change it how we discussed it via mail?
[12:16] <mivoligo> mzanetti: yes
[12:16] <mzanetti> if field is selected and user clicks on tower -> add the tower
[12:16] <mzanetti> if no field is selected and user clicks on tower -> open tower info dialog
[12:16] <mzanetti> ack
[12:17] <mivoligo> mzanetti: I think when the field is not selected, the cost should disappear from the tower
[12:17] <mzanetti> yep
[12:18] <mzanetti> I'll play around with it a bit and you can then tell me how to improve it :)
[12:18] <mivoligo> mzanetti: sure :)
[12:19] <mivoligo> mzanetti: can you also implement the right colours everywhere?
[12:19] <mzanetti> mivoligo: hmm... I thought I had that already
[12:19] <mzanetti> mivoligo: but wanted to talk about that:
[12:19] <mivoligo> mzanetti: hit me :D
[12:20] <mzanetti> so we have UbuntuColors. Which define some red, green, blue etc
[12:20] <mzanetti> but they are a bit different then your definitions
[12:20] <mzanetti> somehow I feel it'd be nice to go with the standard ubuntu definitions
[12:21] <mivoligo> mzanetti: can I see these colors somewhere?
[12:21] <mzanetti> mivoligo: you still on trusty or have you upgraded to utopic?
[12:21] <mivoligo> have utopic in vbox
[12:22] <mzanetti> ah, then you should be able to just create a qml file with a rectangle and set color to
[12:22] <mzanetti> UbuntuColors.green
[12:22] <mzanetti> UbuntuColors.orange
[12:22] <mzanetti> etc
[12:22] <mivoligo> mzanetti: ok
[12:22] <mivoligo> I'll do that
[12:22] <mzanetti> mivoligo: make sure to import Ubuntu.Components 1.1
[12:23] <mzanetti> mivoligo: http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.UbuntuColors/
[12:24] <mzanetti> mivoligo: apart from that, in machines-vs-machines.qml at the top, there are the color definitions for the game
[12:24] <mzanetti> I think it should be used everywhere, if it isn't please file bugs (or just tell me in IRC)
[12:25] <mivoligo> mzanetti: I have black text on the Play! button for example
[12:25] <mzanetti> hmm... I see...
[12:26] <mivoligo> mzanetti: the dots are completely black too
[12:27] <mzanetti> right... ok. need to fix some stuff then
[12:27] <davmor2> popey, ahayzen: there are a few laggy bits but I think that is mostly because images were still loading, once all the images were in I didn't find anything particularly awful with the music app
[12:28] <mivoligo> mzanetti: one more thing about the gameplay
[12:28] <Mirv> popey: calculator uploaded to the store
[12:28] <ahayzen> davmor2, thanks for testing :), is this basically what you are describing with the slow images? https://bugs.launchpad.net/music-app/+bug/1387816
[12:29] <mivoligo> mzanetti: I noticed you don't get any money when selling some towers. I don't know if it's not finished yet or you just forget :D
[12:30] <popey> thanks Mirv
[12:30] <popey> davmor2: yeah, i get that too
[12:30] <popey> once loaded it's fine
[12:31] <popey> brendand: new calc hit the store, yay for automated reviews!
[12:31] <mzanetti> mivoligo: right... tower prices are not correct yet
[12:32] <mzanetti> mivoligo: I wanted to a) implement the changed add logic and b) wait for all the level backgrounds before finishing off the level pack
[12:32] <mzanetti> mivoligo: I have a good idea how to do it now, but each change influences the gameplay and the level difficulty
[12:32] <davmor2> ahayzen: yeap, but things like scrolling feel slower while all the images are loading, once loaded it speeds up I'm assuming it is simply the level of memory and cpu being used to load the image and display them as well as moving the display etc
[12:33] <mzanetti> mivoligo: so that's why I decided to not tweak them any more right now until the rest is finished...
[12:33] <mivoligo> mzanetti: in other words: I have to do the backgrounds :D
[12:34] <mzanetti> mivoligo: well, yeah, at some point yes. don't want to put pressure on you though...
[12:35] <mivoligo> mzanetti: I know :)
[12:36] <mivoligo> mzanetti: speaking of backgrounds: can we have bridges and tunnels?
[12:36] <ahayzen> davmor2, yeah that makes sense...also i is know the 'cardview' is slow because it attempt to load *all* of the thumbnails at once...and loads them backwards just to make it worse ;) lol
[12:36] <mzanetti> mivoligo: we could, but it's not implemented
[12:37] <mzanetti> mivoligo: we can have crossings though
[12:38] <mivoligo> mzanetti: they working right now?
[12:38] <mzanetti> mivoligo: yep
[12:39] <mivoligo> mzanetti: :) good, so I'll concentrate on the backgrounds now
[12:39] <mzanetti> col
[12:40] <mzanetti> cool
[12:40] <mivoligo> coool
[12:40] <mzanetti> :D
[12:40] <mivoligo> mzanetti: oh, one more thing
[12:41] <mivoligo> mzanetti: some time ago I put sound settings icon into the drive, so you can use it
[12:41] <mzanetti> ah ok, cool.
[12:42] <mzanetti> mivoligo: yeah, haven't been very active in the last 3 weeks. there was the sprint and then last weekend my bday...
[12:42] <mzanetti> mivoligo: will ramp up again soon
[12:42] <mivoligo> mzanetti: I'm guilty too
[12:45] <mivoligo> mzanetti: anyway, I'm now thinking about these backgrounds and then we finish the UI
[12:45] <mzanetti> yep. shouldn't be too much left to do
[12:46] <mivoligo> mzanetti: ok, see you around :)
[12:47] <mzanetti> yep
[12:47] <mzanetti> o/
[13:16] <davmor2> charles, nik90: I know how much you love my bugs.  Fresh install with --revision -40 (image 102), Set timezone to New York 22:25, upgrade to the latest image alarm is now magically 04:25 :)
[13:18] <davmor2> charles, nik90: I know how much you love my bugs.  Fresh install with --revision -40 (image 102), Set timezone to New York, set an alarm at 22:25 (sorry missed some words there), upgrade to the latest image alarm is now magically 04:25 :)
[13:40] <aquarius> Can I style the popup that appears when I use a Slider component? In particular, make it appear somewhere other than above the slider?
[13:51] <mzanetti> aquarius: I don't think so
[13:51] <aquarius> bah
[13:51] <mzanetti> aquarius: well, shouldn't be too hard to implement your own one
[13:52] <aquarius> not too hard, but there are a bunch of fiddly interactions with it
[13:52] <aquarius> hence why I prefer using existing components where I can...
[13:52] <mzanetti> yeah... but I guess you'd have the same issues if you'd change/restyle the existing once
[13:52] <mzanetti> one
[13:52] <aquarius> mzanetti, you might have an idea about my larger problem, here
[13:53] <mzanetti> you might want to reconsider the reason why the default position doesn't work for you :)
[13:53] <aquarius> imagine a Page, with a header, containing a listview. If I scroll the listview, the header disappears, and comes back if I scroll up. Hooray
[13:53] <aquarius> however. I would like, at the top of the listview, a text box
[13:53] <aquarius> and I want the text box to always be on screen
[13:54] <mzanetti> meh
[13:54] <aquarius> the app is trivial -- a text box for text, and a listview of that text in all fonts.
[13:54] <mzanetti> you still want the header moving?
[13:55] <mzanetti> if you keep the header fixed, this shouldn't be too hard... but the moving header in the SDK is quite a hack actually and only working properly when the first item in there is a ListView
[13:55] <aquarius> but... I don't know how to get the magic header scrollability vanish stuff if the listview isn't the only child of a Page
[13:55] <aquarius> right. I don't want the header to stay fixed because, well, it takes up about a fifth of the screen :P
[13:55] <aquarius> (not quite that much, perhaps)
[13:55] <mzanetti> so what the header does is to set topMargin (*NOT* anchors.topMargin) on the ListView
[13:56] <mzanetti> you might be able to play around with that and increase that
[13:56] <aquarius> hm
[13:56] <mzanetti> or you could try to use the header property of the ListView
[13:56] <mzanetti> and put your textbos in there
[13:57] <aquarius> sneaky
[13:57] <aquarius> nik90 suggested the listview header thing, but I couldn't get it to do anything :)
[13:58] <mzanetti> aquarius: I think you need to use a Component for it
[13:58] <mzanetti> like described in the first reply here: http://stackoverflow.com/questions/8089522/qml-listview-header-and-footer-items
[13:58] <aquarius> do toolbar items have to be one of the actual Toolbar things, like a ToolbarBUtton? Or can I put a slider in the toolbar?
[13:59] <mzanetti> you can't
[13:59] <aquarius> the docs say "However, it is possible to include non-ToolbarButton Items inside ToolbarItems", but the only example given is a Button, which only has tap interactions, not slide interactions
[13:59] <mzanetti> oh... well, if a button works, I don't see a reason why a slider would not
[13:59] <aquarius> maybe I'll give that a try
[13:59] <mzanetti> I thought you can't put visual things in there, as Action {} is a non-visual item only holding information that the header draws itself
[14:00] <nerochiaro> artmello: hi, do you think you will have time at some point this week to see if it is possible to replace the custom header in the camera photo roll with the header+mainview from the SDK ?
[14:00] <mzanetti> my info on that might be outdated though
[14:00] <aquarius> ah
[14:01] <aquarius> now that tools appear in the header, rather than the drag-up-from-the-bottom toolbar, it seems that you can only put ToolbarButtons in it
[14:01] <aquarius> bah, again
[14:01] <aquarius> and the example on http://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Components.ToolbarItems/ is wrong, mhall119
[14:01]  * aquarius files a bug
[14:03] <artmello> nerochiaro: yes, I could take a look on that this week
[14:03] <nerochiaro> artmello: thanks. please email me the branch when you do, if you don't see me here in irc
[14:03] <aquarius> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1389711 filed.
[14:05] <artmello> nerochiaro: sure
[14:07] <nik90> davmor2: image 40? Which channel is this?
[14:07] <davmor2> nik90: -40 it goes back 40 images so the image is 102
[14:08] <nik90> davmor2: ah
[14:08] <davmor2> nik90: see not in brackets after the -40 :)
[14:08] <davmor2> s/not/note :)
[14:08] <nik90> davmor2: I think there was some change in EDS related to timezone changes ...can you reproduce it with the current image?
[14:09] <nik90> davmor2: as in, set an alarm for 10:00 and then change the timezone, does that change the alarm?
[14:09] <davmor2> nik90: I was testing ota so it would need to be triggered in an ota
[14:10] <davmor2> nik90: by going back 40 images you effectively trigger a fresh install but with data on
[14:11] <nik90> davmor2: well, after rtm, we will ota at which point this should work as expected since there wouldn't any more critical changes like that in the rtm distro?
[14:11] <nik90> between 102 and 142, a lot could have changed...but that doesn't mean a lot wil change between 142 and 182 for instance
[14:12] <davmor2> nik90: yes but between rtm and ota 2 there could still be a lot of changes and that is what we are looking for now :)  shaking the tree so to speak
[14:13] <davmor2> nik90: no but again it would be enough of a delta to trigger a full install which again might corrupt data
[14:14] <nik90> ah ok
[14:18] <nik90> zsombi: hey, I am not sure if charles brought this up with you, but there is a bug where when a single type alarm is triggered, it does not get automatically disabled or deleted by the system. And you mentioned that this is something indicator-datetime should do since it is the one which triggers the alarm.
[14:18] <nik90> zsombi: well charles fixed it by making indicator-datetime disable the alarm via the tasks.ics file. However the clock app does not update automatically to reflect the change.
[14:19] <nik90> only on restarting the clock app does it show the single type alarm as disabled.
[14:19] <nik90> this is all still in a branch and hasn't been released yet
[14:31] <balloons> nik90, so the resolution on everything I thought I would share. Nothing seemed to work out, so I did something interesting. I hid the non text areas when keyboard appears and shrunk the boxes slighlty too
[14:50] <mhall119> aquarius: what's wrong about it?
[15:14] <popey> mhall119: 14:03:50 < aquarius> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1389711 filed.
[15:15] <mhall119> I believe you could in the bottom-edge toolbars in 14.04
[15:16] <popey> yeah, he says that in the bug i think
[15:17] <mhall119> ah, it's present in the 14.10 docs too, he originally linked to 14.04 docs
[15:17] <mhall119> here in IRC
[15:18] <mhall119> so yeah, that's for the uitk developers to fix in the -doc packages
[15:19] <mhall119> I'm not sure ToolbarItems can be used at all with the header toolbar, it may only work with useDeprecatedToolbar: true
[15:19] <mhall119> in which case it might be accurate, but needs to be clarified
[15:21] <nik90> balloons: didn't the code diff I provided yesterday work out?
[15:25] <t1mp> aquarius: I commented on https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1389711
[15:26] <jdstrand> I'm having trouble with themes
[15:26] <jdstrand> I understand how to do this:
[15:26] <jdstrand> Component.onCompleted: {
[15:26] <jdstrand>   Theme.name = 'Ubuntu.Components.Themes.SuruDark'
[15:26] <jdstrand> }
[15:27] <jdstrand> that works fine (though, there are various bind loop detected errors
[15:27] <jdstrand> )
[15:27] <jdstrand> but what I'd really like to do is define my own theme
[15:28] <jdstrand> I created a qmldir, MainViewStyle.qml, Palette.qml and parent_theme in Themes/Foo
[15:28] <jdstrand> but when I do:
[15:28] <jdstrand> Component.onCompleted: {
[15:28] <jdstrand>   Theme.name = 'Themes.Foo'
[15:28] <jdstrand> }
[15:28] <balloons> nik90, no it didn't. I'd rather work on using the new header next. But othe rprojects take my attention for now
[15:28] <balloons> nik90, at least for me it didn't work so good
[15:29] <jdstrand> I get "Theme not found: " "Foo"
[15:29] <balloons> nik90, it did help me with the solution I ended up using, and I learned some tricks, so thank you much for all the help
[15:29] <jdstrand> I have a qmldir in Themes too, but don't know how to setup the import line
[15:29] <jdstrand> (I may not know a lot more than that :)
[15:31] <zsombi> nik90: still around?
[15:32] <nik90> balloons: np
[15:32] <nik90> zsombi: yeah
[15:33] <zsombi> nik90: seems EDS sends the change while the app is in background, which means that when the app is waken up, it won't get the signal anymore.
[15:33] <zsombi> nik90: have you tried the same in desktop?
[15:34] <nik90> zsombi: no I haven't tried it on the desktop. Since the branch is a wip, I haven't tested it yet
[15:34] <zsombi> nik90: yeah...
[15:35] <zsombi> nik90: the situation is as said: we need a refresh to be invoked every time the app gets foreground.
[15:36] <nik90> does an app go to background when there is a snap notification shown?
[15:36] <nik90> if that's the case, then that should be simple enough to implement in the clock app
[15:42] <t1mp> nik90: do you want to host this one? http://summit.ubuntu.com/uos-1411/meeting/22338/ubuntu-touch-component-store/
[15:43] <nik90> t1mp: I created that session, so yes
[15:43] <nik90> t1mp: although I am contemplating a little about it
[15:43] <nik90> ;)
[15:44] <t1mp> nik90: it is not a bad idea
[15:44] <t1mp> just not something we can help a lot with because we have our hands full with the official UITK
[15:45] <t1mp> nik90: shall I wait with scheduling it until you finish contemplating? :)
[15:45] <nik90> t1mp: yeah that would be best. I am working on a prototype for it. If it goes well, then it might be worth having the session.
[15:46] <t1mp> ok, cool
[15:51] <jdstrand> zsombi: istr you did the themes work for Ubuntu. how does an app developer override the/provide a theme?
[15:52] <zsombi> jdstrand: it's pretty cumbersome, you can to it in the MainView in Components.onCompleted: Theme.name = "your.theme.name"
[15:53] <jdstrand> zsombi: right, but did you see backscroll? I can't seem to be able to find "you.theme.name" if I define my own theme
[15:54] <jdstrand> I really don't know what I'm doing, but basically, I took the SuruDark theme's files, modified them a bit and then put them in a directory in my tree, sprinkling in qmldirs
[15:54] <zsombi> jdstrand: no, did not scroll back, I did not see my name there mentioned :)
[15:54] <zsombi> jdstrand: so
[15:54] <jdstrand> heh, that's fine
[15:54] <zsombi> jdstrand: in this case, your.theme.name should be stored relative to your app's folder
[15:55] <t1mp> zsombi: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1389759 :)
[15:55] <zsombi> jdstrand: like <appfolder>/your/theme/name
[15:55] <jdstrand> and what is 'name'?
[15:55] <zsombi> t1mp: yes, I know...
[15:55] <jdstrand> a directory with the MainViewStyle.qml  Palette.qml  parent_theme?
[15:55] <zsombi> jdstrand: 'name' what? Theme.name? it's a proeprty, the name of the theme to be used
[15:55] <t1mp> zsombi: but now there is a bug so we can track ideas and progress :)
[15:56] <zsombi> t1mp: no, sh...
[15:56] <zsombi> :D
[15:56] <zsombi> t1mp: first we need subtheming and then we document this
[15:56] <jdstrand> zsombi: ie, should I have <appfolder>/your/theme/name/MainViewStyle.qml, <appfolder>/your/theme/name/Palette.qml and <appfolder>/your/theme/name/parent_theme?
[15:58] <zsombi> jdstrand: no, you don't need all of them. you can do as SuruDark theme is done, so you need a :parent" file which tells what theme your are deriving from, then have only the styles you want to chane, or the Palette if that's the only thing you wanna change
[15:59] <jdstrand> zsombi: that is what I was trying to get at
[15:59] <jdstrand> zsombi: so, I create <appfolder>/your/theme/name/parent_theme
[15:59] <jdstrand> it has something like:
[15:59] <jdstrand> Ubuntu.Components.Themes.Ambiance
[16:00] <jdstrand> then if all I want to do is fiddle with colors, <appfolder>/your/theme/name/Palette.qml
[16:00] <zsombi> jdstrand: ah, and forgot that the MainViewStyle will screw your theme selection :/
[16:00] <jdstrand> so I should omit MainViewStyle?
[16:00] <zsombi> jdstrand: so you may want to rewrite that component completely :(
[16:01] <zsombi> jdstrand: you need to declare a MainViewStyle of your own
[16:01] <jdstrand> zsombi: ok, so, yeah, I had: http://paste.ubuntu.com/8837588/
[16:02] <zsombi> jdstrand: unfortunately teh default one will chose between Ambiance and SuruDark/SuruGradiemnt depending on teh backgroindCiolor/header/footerColors set
[16:02] <zsombi> jdstrand: that's not enough :(
[16:02] <jdstrand> zsombi: what else is needed?
[16:02] <jdstrand> is this the bit with the Binding stuff?
[16:03] <jdstrand> eg, http://bazaar.launchpad.net/~savilerow-team/savilerow/trunk/view/head:/src/system/custom/xdg/data/themes/Ubuntu/Custom/MainViewStyle.qml
[16:03] <zsombi> jdstrand: you can have whatever there, MainViewStyle has no public API (yet)
[16:03] <aquarius> t1mp, ah, nice, am looking at the page header stuff now. Clearly the docs should have made that reference for me, as you note :)
[16:03] <zsombi> jdstrand: so you can just have a Rectangle with your prefered color, or you can take teh color from MainView (styledItem.backgroundColor)
[16:04] <jdstrand> zsombi: oh, I think I responded to the wrong thing. is this sufficient to get me started with playing: http://paste.ubuntu.com/8837588/
[16:04] <jdstrand> zsombi: or do I need to do something more like http://bazaar.launchpad.net/~savilerow-team/savilerow/trunk/view/head:/src/system/custom/xdg/data/themes/Ubuntu/Custom/MainViewStyle.qml
[16:05] <zsombi> jdstrand: it all depends what you want :) if you want a solid fill, no need for gradients or two items, you can have a simple Rectangle {z: -1; color: styledItem.backgroundColor }
[16:06] <zsombi> jdstrand: and forgot anchors.fill: parent
[16:06] <jdstrand> zsombi: I'm not being clear. you said the default will only choose between two themes. I thought you were saying I needed to do something extra for it to recognize my theme
[16:07] <zsombi> jdstrand: yes, you need to disable the logic that recognizes the two hardcoded themes (the stuff below line 53 in the MainViewStyle)
[16:07] <zsombi> jdstrand: you can do that by writing your own MainViewStyle.qml in your app's theme
[16:08] <zsombi> jdstrand: no need to derive from Ambiance, just write your own stuff
[16:09] <zsombi> jdstrand: so, your MainViewStyle.qml could be
[16:09] <zsombi> import QtQuick 2.2
[16:09] <zsombi> Rectangle {
[16:09] <zsombi> anchors.fill: parent
[16:09] <zsombi> color: styledItem.backgroundColor
[16:09] <zsombi> z: -1
[16:09] <zsombi> }
[16:09] <zsombi> jdstrand: that's it
[16:10] <zsombi> jdstrand: the thing is that if you derive from Ambiance's MainViewStyle, that will be driving you out from your theme
[16:13] <jdstrand> zsombi: is this what you are talking about: http://paste.ubuntu.com/8837747/
[16:14] <jdstrand> I think you are saying I need to remove a few things
[16:14] <zsombi> jdstrand: uh, no, the theme.Foo/MainViewStyle.qml is wrong
[16:14]  * jdstrand really has no idea what he is doing with themes :)
[16:14] <jdstrand> can you tell?
[16:14] <zsombi> jdstrand: just did ^^^^
[16:14] <jdstrand> no, 'can you tell' was a joke on me not knowing what I'm doing
[16:15] <zsombi> jdstrand: :D
[16:15] <jdstrand> zsombi: what should theme/Foo/MainViewStyle.qml have for just a bare bones 'here is how you start with theming'?
[16:16] <zsombi> 18:09 zsombi: jdstrand: so, your MainViewStyle.qml could be
[16:16] <zsombi> 18:09 zsombi: import QtQuick 2.2
[16:16] <zsombi> 18:09 zsombi: Rectangle {
[16:16] <zsombi> 18:09 zsombi: anchors.fill: parent
[16:16] <zsombi> 18:09 zsombi: color: styledItem.backgroundColor
[16:16] <zsombi> 18:09 zsombi: z: -1
[16:16] <zsombi> 18:09 zsombi: }
[16:16] <zsombi> jdstrand: you keep deriving your MainViewStyle from Ambieance's MainViewStyle, but you don't have to
[16:18] <jdstrand> zsombi: so, having the ambiance import in the MainViewStyle.qml means I am deriving from it?
[16:18] <zsombi> jdstrand: more precisely you shouldn't derive from it at all, because if you do, the ancestor MainViewStyle will drive your theme out.
[16:18] <zsombi> jdstrand: that alone doesn't mean
[16:19] <zsombi> jdstrand: but the line 52 from http://paste.ubuntu.com/8837747/ does
[16:20] <jdstrand> ok, so I've adjusted MainViewStyle.qml to remove the ambiance import and the binding. then I'm using in my main.qml:
[16:20] <jdstrand> import "themes"
[16:20] <jdstrand> Component.onCompleted: Theme.name = 'themes.Foo'
[16:20] <jdstrand> it seems to have found it
[16:21] <zsombi> jdstrand: why don't you use the code I wrote for the MainViewStyle in the chat?
[16:21] <jdstrand> I thought I did
[16:21] <jdstrand> http://paste.ubuntu.com/8837846/
[16:21] <zsombi> jdstrand: do you want to have the same coloring as the Ambiance has? (except the automatic theme switching)
[16:22] <zsombi> jdstrand: :D
[16:22] <zsombi> jdstrand: you're doing "recursive" typing
[16:22] <zsombi> jdstrand: get rid of the topmost MainViewStyle {
[16:22] <zsombi> jdstrand: just use the Rectangle {}
[16:23] <jdstrand> what I really want is to be able to use the SuruDark palette, and then override one component OptionSelectorStyle.qml
[16:23] <jdstrand> oh
[16:23] <zsombi> jdstrand: ok, then we need a bit more complex style, lemme write U one
[16:24] <jdstrand> zsombi: sorry, use the suru dark palette, with me overriding a few things
[16:24] <jdstrand> and then override the occasional component's style
[16:25] <jdstrand> yeah, what I have now needs me to redefine a bunch of style qml files
[16:25] <jdstrand> file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/ToolbarItems.qml:139:25: QML ActionItem: Warning: Style ToolbarButtonStyle.qml not found in theme themes.Foo
[16:26] <jdstrand> file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/OptionSelector.qml:220:9: QML StyledItem: Warning: Style OptionSelectorStyle.qml not found in theme themes.Foo
[16:28]  * jdstrand thought that was what parent_theme was for...
[16:28] <zsombi> jdstrand: http://paste.ubuntu.com/8837908/
[16:29] <zsombi> jdstrand: huhh?
[16:29] <zsombi> jdstrand: parent theme should be SuruDark if you want SuruDark colors as base
[16:30] <jdstrand> zsombi: sure
[16:30] <jdstrand> I can change that
[16:30] <zsombi> jdstrand: but this failure tells me that the Theme engine doesn't find the style from your app...
[16:30] <jdstrand> and let me do that right now
[16:31] <jdstrand> ah yes
[16:31] <jdstrand> I thought it was found, but it wasn't
[16:31] <jdstrand> QQmlComponent: Component is not ready"Theme not found: " "themes.Foo"
[16:31] <jdstrand> zsombi: do the qmldirs need to be there?
[16:32] <zsombi> jdstrand: well, it has to be there only if you derive from it, which is not teh case in your app
[16:33] <jdstrand> ok, so I moved them aside
[16:33]  * zsombi checks the theming unit tests again
[16:33] <jdstrand> I'm using: Component.onCompleted: Theme.name = 'themes.Foo'
[16:33] <jdstrand> in MainView{}
[16:33] <jdstrand> do I need to do anything else with the imports?
[16:35] <zsombi> jdstrand: make sure you import the 1.1 version in teh theme so you get all the palette values
[16:35] <jdstrand> zsombi: which theme, and where?
[16:35] <zsombi> jdstrand: I mean wherever you derive
[16:36] <zsombi> jdstrand: in your OptoipnSelectorStyle.qml
[16:36] <zsombi> jdstrand: and btw, OptionSelector is deprecated, better use ItemSelector!
[16:36] <zsombi> jdstrand: which will be rewritten once we get the ListItem out
[16:36] <jdstrand> right, but ItemSelector had a number of problems. I filed a bug, but that is separate
[16:37] <zsombi> jdstrand: and in your Palette.qml as well, import Ubuntu.Components.Themes.SuruDark 1.1
[16:38] <zsombi> jdstrand: in that way your palette will be based on SuruDark, so you only have to change teh colors you want
[16:38] <jdstrand> zsombi: ok, I changed Palette.qml
[16:38] <jdstrand> zsombi: but I don't know what you mean by "I mean wherever you derive"
[16:39] <jdstrand> I don't know where I derive
[16:39] <jdstrand> parent_theme?
[16:39] <jdstrand> MainViewStyle.qml?
[16:39] <jdstrand> both?
[16:39] <zsombi> jdstrand: the Palette.qml derives from SuruDark's Palette :)
[16:39] <jdstrand> zsombi: yes, but you said 'as well' for Palette.qml
[16:39] <jdstrand> so I did that
[16:40] <jdstrand> but I didn't do the 1st thing cause I don't know what you are talking about
[16:40] <zsombi> jdstrand: you said you want to change the OptionSelectorStyle, so you need to derive from the paren't sone, right?
[16:40] <jdstrand> ok, so in OptionSelectorStyle.qml, I would have that import
[16:41] <jdstrand> got it
[16:41] <jdstrand> I am not doing that atm though
[16:41] <zsombi> jdstrand: ah, ok :)
[16:41] <jdstrand> I'm just trying to get my main.qml to find the theme
[16:41] <jdstrand> and it isn't
[16:41] <zsombi> jdstrand: ok, so you rtheme yet doesn't have anything else just parent_theme, MainViewStyle.qml and Palette.qml
[16:41] <jdstrand> that is correct
[16:42] <jdstrand> your MainViewStyle.qml, Palette.qml from SuruDark (with the added import you just gave) and parent_theme that (now) reference SuruDark
[16:42] <jdstrand> main.qml has:
[16:42] <jdstrand> import "themes"
[16:42] <jdstrand> MainView {
[16:42] <jdstrand> ...
[16:43] <jdstrand> Component.onCompleted: {
[16:43] <jdstrand>   Theme.name = 'themes.Foo'
[16:43] <jdstrand> }
[16:43] <jdstrand> ...
[16:43] <zsombi> jdstrand: you don't need to import "themes"
[16:43]  * jdstrand tries without
[16:43] <zsombi> jdstrand: it won't do much difference
[16:43] <jdstrand> "Theme not found: " "themes.Foo"
[16:43] <zsombi> jdstrand: wth??!
[16:44] <jdstrand> let me get a simple reproducer
[16:44] <zsombi> jdstrand: seems we have a BIG bug then!
[16:46] <zsombi> jdstrand: need to reboot, brb
[16:48] <zsombi> back
[16:49] <jdstrand> zsombi: http://paste.ubuntu.com/8838140/
[16:49]  * jdstrand wonders if he needs an import in main.qml
[16:49] <jdstrand> for SuruDark
[16:52] <zsombi> jdstrand: import for your theme? there shouldn't be needed, the Theme engine loads the theme as files, and creates the style components by loading them as files
[16:52] <zsombi> jdstrand: so the import "themes" shoudl not be needed
[16:53] <jdstrand> it was a wild guess. have I mentioned I don't know what I'm doing?
[16:53] <jdstrand> :)
[16:53]  * jdstrand is trying to learn
[16:53] <zsombi> jdstrand: LOL not surprized, we don't have any docs on this
[16:53] <aquarius> t1mp, can I have multiple pageheadstates? or am I only allowed two, a default one and one other?
[16:53] <zsombi> jdstrand: and we are trying to make it more robust
[16:54] <jdstrand> zsombi: could you reproduce with the paste I gave?
[16:54] <zsombi> jdstrand: and we're introducing the subtheming as well
[16:54] <zsombi> jdstrand: I'll try
[16:55] <jdstrand> oh, I left a 'import Ubuntu.Components.Themes.SuruDark 1.1' in ./themes/Foo/MainViewStyle.qml for testing. removing it doesn't help though
[16:57] <jdstrand> there was probably an uneeded extra import in Palette.qml too. removing it didn't help either
[16:58] <zsombi> jdstrand: looking
[17:00] <zsombi> jdstrand: ok, so the theme did not change after all, checking the reason
[17:00] <aquarius> do I have to do something special to make icons from the theme work? I'm using iconName: "back" in an action, and I get a black square, and output says "QML QQuickImage: Failed to get image from provider: image://theme/back". (This is running on the emulator.) /usr/share/icons/suru/actions/scalable/back.svg exists on teh device.
[17:01] <jdstrand> zsombi: thanks for the help and sorry for being a pain. as payback, once I get theme-test working, I'll give the tarball to davidcalle since I know he wants to do a theming tutorial
[17:02] <zsombi> jdstrand: :D
[17:02] <zsombi> jdstrand: thx
[17:02] <zsombi> jdstrand: a tutorial which we will have to update once the subtheming comes
[17:02] <jdstrand> well, hopefully that will only affect 15.04 frameworks, no?
[17:03] <zsombi> jdstrand: but it is better to update something we have rather to not have anything
[17:03] <jdstrand> ie, apps that use the 14.10 frameworks with this stuff would hopefully still work
[17:03]  * jdstrand nods
[17:03] <zsombi> jdstrand: yes, 15.04 is the plan for it
[17:05] <zsombi> jdstrand: the current Theme engine will stay, but we will need something more neat and not a context property, becaus ethat is a pain...
[17:05] <aquarius> man, none of this pagehead stuff works :(
[17:05] <zsombi> jdstrand: and all this will apply to 1.2 import of Ubuntu.Components
[17:05] <jdstrand> that's cool
[17:06] <jdstrand> zsombi: ah, so you were able to confirm that the theme didn't apply. ok, good. I'm not crazy (though, less good for you)
[17:06] <jdstrand> well, I'm not crazy cause of *that*
[17:06] <zsombi> jdstrand: yes, the theme is not found, but I wonder why...
[17:06] <aquarius> setting head.actions as given in the example at http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.PageHeadConfiguration/ just doesn't seem to show any actions at all, as far as I can tell?
[17:07] <dpm> t1mp, zsombi, any of you have seen what aquarius is experiencing with black squares on the emulator? ^ I've seen it in the past, but I've not seen the black squares lately
[17:07] <zsombi> jdstrand: because the "Theme not found" should come ony if teh parent theme is not found...
[17:07] <zsombi> dpm: I can see black squares everywhere :D
[17:08] <dpm> yeah, I'm starting to see lights all around me now that I'm nearing my EOD :)
[17:09] <nik90> aquarius: did you set useDeprecatedToolbars to false in your mainView?
[17:10] <nik90> aquarius: I wrote that example and it works well in my testing
[17:10] <aquarius> nik90, yep.
[17:10] <nik90> do you get any runtime errors?
[17:10] <zsombi> jdstrand: could you please file a bug for this theming problem?
[17:10] <jdstrand> sure
[17:10] <aquarius> nik90, http://paste.ubuntu.com/8838430/ is the whole source
[17:10] <zsombi> jdstrand: thx!!!
[17:11] <zsombi> jdstrand: just assign to me if you can, so I can follow it tomorrow!!!
[17:12]  * nik90 runs the example
[17:13] <aquarius> nik90, it is possible that the pageheadstate is overriding the actions. but if I put two actions in the default pageheadstate, then it screws up when selecting them, afaict ;(
[17:14] <nik90> aquarius: https://imgur.com/M6zggaf
[17:15] <aquarius> wtf?
[17:15] <mihir> popey: yay started merging MRs
[17:15] <aquarius> that doesn't happen to me
[17:15] <popey> Ooh!
[17:15] <nik90> aquarius: I had to move the 2 actions you defined inside the default state
[17:15] <popey> mihir: awesome stuff! looking forward to trying out the new stuff! :D
[17:15] <nik90> aquarius: you need to specify which actions you want to show manually in each pageheadstate
[17:16] <mihir> popey: yup , i have approved both kunal's MP , I am waiting him to review and approve my MPs and we are ready to push in store.
[17:16] <nik90> aquarius: what did you mean by " but if I put two actions in the default pageheadstate, then it screws up when selecting them, afaict ;("
[17:16] <popey> mihir: awesome.
[17:16] <mihir> popey: then I guess we have to think , what needs to be done next, shall we wait for design inputs or just move ahead with the fixing and performance issues.
[17:17] <aquarius> nik90, right, so then, two things. 1) that example doesn't work if you have pageheadstates, but it doesn't say that :) More importantly, 2) I get both the "states" on top of one another when switching to them. :( Try tapping one of the icons, then go back, then tap the other. I get both the slider *and* the text box on top of one another
[17:18] <jdstrand> zsombi: what should I file it against, ubuntu-ui-toolkit?
[17:18] <zsombi> jdstrand: yes
[17:19] <zsombi> jdstrand: and I think I have the fix for it.. or at least I can see that the app's path is not added to the theme lookup list :/
[17:19] <zsombi> jdstrand: so no wonder it doesn't find it
[17:20] <aquarius> what the hell? now I can't even deploy; "process:5138): WARNING **: database.vala:794: Manifest in /opt/click.ubuntu.com/org.kryogenix.fontbrowser/0.1/.click/info/org.kryogenix.fontbrowser.manifest is not a JSON object"
[17:20] <aquarius> I haven't touched the manifest :(
[17:20] <nik90> aquarius: hmm I get your bug where the pageheadstate contents mix with one other..that's a serious bug!
[17:20] <zsombi> jdstrand: this engine is ancient enough we thought the app's themes will be stored in ~/.local/share
[17:20] <aquarius> nik90, it is. It makes pageheadstates unusable :(
[17:21] <zsombi> jdstrand: it has not been updated for ~1 year now...
[17:21] <nik90> zsombi: can you see if you can run this code http://paste.ubuntu.com/8838577/ and reproduce the above bug. its quite serious
[17:22] <zsombi> nik90: what bug?
[17:22] <nik90> basically run the app -> press the search icon -> press the back icon -> press the webbrowser icon
[17:22] <nik90> you will notice that the contents of each pageheadstate mix with one other
[17:22] <nik90> so the whole "state" concept breaks down
[17:23] <nik90> so you will see the slider and textfield on top of one other
[17:23] <jdstrand> zsombi: bug #1389792
[17:23] <jdstrand> zsombi: ah!
[17:24] <jdstrand> zsombi: I'm guessing this is definitely something for OTA
[17:24] <jdstrand> zsombi: should I bring it up to the PM team?
[17:24] <zsombi> jdstrand: I'd say so... however apps are not really using this rigt now
[17:25] <zsombi> jdstrand: you can, however if apps are not using it, it won't be so crucial
[17:25] <jdstrand> zsombi: no, they aren't, but this is about the developer story. developer's can't change the theming, and I think that is a problem (it's been hugely frustrating for me)
[17:25] <zsombi> jdstrand: yes, I agree :(
[17:26] <zsombi> jdstrand: ok, let's see what PMs are gonna say about it
[17:26] <jdstrand> pmcgowan: fyi, bug #1389792. I was thinking 'high' and 'ota-1'. what do you think?
[17:28] <zsombi> nik90: ah, that one! that bug (or a similar one) has been already repoprted to header, t1mp?
[17:28] <nik90> zsombi: well I remember ahayzen reporting it, but that only happened when switching between different pages. This bug happens within the same page itself.
[17:29] <nik90> so essentially we are limiting the developer to using only 2 pageheadstates to avoid this bug
[17:29] <ahayzen> nik90, oh the searching bug?
[17:29] <zsombi> nik90: doesn't matter, similar problem
[17:33] <zsombi> jdstrand: one question: will the launcher set teh current dir to the path the app is launched?
[17:34] <jdstrand> zsombi: yes, a chdir to the install dir happens on launch. it is safe to use relative paths
[17:34]  * zsombi wonders how can we get the path to the app's theme 
[17:34] <zsombi> jdstrand: ok, good, so I don't have to do any magic, I can use QDir::currentPath() then, thx
[17:35] <zsombi> jdstrand: ok, seems to be a one liner :)
[17:35] <zsombi> jdstrand: or not :D
[17:36] <zsombi> I get loads of binding loops now...
[17:36] <zsombi> anyways, will continue tomorrow
[17:36] <jdstrand> note, I see binding loops when I just set the theme to SuruDark
[17:36] <jdstrand> (ie, not trying to do any of this user-defined theming)
[17:43] <zsombi> t1mp: damn, the automatic style change in MainViewStyle is giving nore and more headache!
[17:57] <t1mp> zsombi: what's up?
[17:58] <t1mp> zsombi: I thought we decided to remove it
[17:58] <akiva-thinkpad> dpm, Just waiting to hear back from a few people; I will probably be able to host one or two. For the "Why Go?", I am trying to find another developer who is familiar with Go to host it.
[17:59] <dpm> akiva-thinkpad, cool. I'm asking a Go advocate too, I think it could be a good session
[17:59] <t1mp> B18:13:27 < aquarius> nik90, it is possible that the pageheadstate is overriding the actions. but if I put two actions in the default  pageheadstate, then it screws up when selecting them, afaict ;(
[17:59] <t1mp> aquarius: yes there is something wrong with the PageHeadState
[18:00] <t1mp> aquarius: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1345775
[18:03] <akiva-thinkpad> dpm, http://www.reddit.com/r/golang/comments/2ldlpl/is_anyone_would_be_interested_in/
[18:03] <akiva-thinkpad> Seems to be upvoting
[18:08] <pmcgowan> jdstrand, sounds good
[18:15] <dpm> thanks akiva-thinkpad
[18:15] <dpm> kyleN -> http://developer.ubuntu.com/2014/11/announcing-the-ubuntu-scopes-workshops/
[18:16] <zsombi> t1mp: if we remove the auto-theming from MainViewStyle, we will break some apps...
[18:16] <dpm> ah, sorry pinged you unnecessarily again about it, I meant to post the link here to let folks know about the workshops
[18:19] <zsombi> greyback_: ping
[18:19] <greyback_> zsombi: pong
[18:20] <t1mp> zsombi: now is the best time to do that
[18:20] <zsombi> greyback_: dude, I need a field in the desktop file
[18:20] <zsombi> greyback_: to set teh theme
[18:20] <zsombi> greyback_: of the app
[18:20] <greyback_> zsombi: how is the theme set? I.e. is it an env var, to be set at app run?
[18:20] <zsombi> greyback_: is it on you, or not? I mean is the app launcher on your hands?
[18:21] <zsombi> greyback_: yes
[18:21] <t1mp> zsombi: you can add a onBackgroundColorChanged: if (lightness(backgroundColor) < 0.5) print("For a dark background color, add $some_code to use the suru dark theme");
[18:21] <greyback_> zsombi: you need tedg
[18:21] <t1mp> zsombi: or we fix the apps first
[18:21] <zsombi> greyback_: thx
[18:21] <greyback_> zsombi: as upstart-app-launch will be performing the env var set
[18:21] <zsombi> greyback_: sure
[18:22] <zsombi> t1mp: the problem is partly solved with...
[18:22] <zsombi> t1mp: the best would be if teh app would be launched with the proper theme, i.e. if the app si launched with its own theme, then we're good.
[18:22] <zsombi> t1mp but perhaps moving the theme to the StyledItem woudl also help...
[18:23] <zsombi> t1mp: must do a small proto anyway
[18:23] <t1mp> zsombi: where is the theme now
[18:23] <t1mp> ?
[18:23] <t1mp> I don't see it in MainView.qml
[18:23] <zsombi> t1mp: MainViewStyle
[18:23] <t1mp> ah yes, there..
[18:23] <zsombi> t1mp: it was there for >1 year now :)
[18:23] <t1mp> yeah
[18:23] <zsombi> :P
[18:23] <t1mp> and that is weird.
[18:23] <zsombi> I know... I always said so :D
[18:24] <t1mp> zsombi: we can move it to the MainView instead, and *never* change the theme in a style..
[18:24] <zsombi> anyways, I'll try to get a small workaround there
[18:24] <zsombi> t1mp: yes, but that doesn't help
[18:24] <t1mp> actually like that we will have the desired default behavior and the binding loops should be gone
[18:24] <zsombi> t1mp: as if the app wants a custom theme, what will we do?
[18:25] <t1mp> hmpf
[18:25] <t1mp> the MainView needs a theme property then
[18:25] <t1mp> I have to go now
[18:25] <zsombi> t1mp: we better ask launcher to read a desktop file field and set it as UBUNTU_UI_TOOLKIT_THEMES_PATH, so teh app is launched with that
[18:25] <t1mp> zsombi: we need subtheming support :)
[18:25] <zsombi> t1mp: yes
[18:26] <t1mp> zsombi: that won't be needed anymore when our StyledItems have a theme property
[18:26] <zsombi> t1mp: and we can start having that slowly
[18:26] <zsombi> right
[18:26] <t1mp> we can start with only the MainView
[18:26] <t1mp> and then extend it to the StyledItems
[18:26]  * t1mp gotta run now
[18:26] <t1mp> ttyl
[18:27] <zsombi> t1mp: cheers
[18:27]  * zsombi goes off 2
[22:39] <brendand> nik90, in your email were you referring to the ringer volume?
[22:44] <nik90> brendand: well both ringer volume and alarm volume
[22:45] <nik90> so I basically don't hear incoming calls or alarms clearly
[22:45] <nik90> since they are so low
[22:45] <brendand> nik90, right. so i just replied - basically you can't change the volume of those while media is playing
[22:45] <nik90> brendand: but I didn't have any media playing though
[22:45] <brendand> nik90, it's the same on other platforms, just they make it clearer by displaying a different icon on the volume overlay
[22:46] <nik90> brendand: either way I just want to increase the ringer/notification volume, how do I do that?
[22:47] <brendand> nik90, it works fine for me here apart from that
[22:47] <brendand> nik90, it could possibly get stuck on the media context somehow
[22:47] <brendand> nik90, have to restarted the device?
[22:47] <nik90> so If I was receiving an call and then I press the volume button, would that change the ringer volume?
[22:48] <brendand> nik90, it should
[22:48] <nik90> I have restarted the phone a couple of times due to unity8 crashing causing media hub to eat my battery
[22:48] <nik90> I have not had luck :/
[22:48] <nik90> I will try again later in the night and see If I get anywhere
[22:50] <brendand> nik90, i'm on -proposed so there's a small chance it was fixed in the meantime, but i don't think i saw any fixes matching that description coming through
[22:50] <brendand> nik90, definitely when the call is ringing and i change the volume, it changes the ringer volume, not the music volume
[22:51] <brendand> nik90, if it doesn't for you then something very curious is going on
[22:54] <nik90> true
[22:55] <nik90> brendand: strange thing was when I saw the call snap notification, press the volume buttons did not show the volume snap notification to indicate the volume is increasing
[22:55] <nik90> but yeah we definitely need a UI to change volume of different roles separately to make it more clear
[23:09] <aquarius> I suddenly can't deploy my app to the emulator: it says "database.vala:794: Manifest in /opt/click.ubuntu.com/org.kryogenix.fontbrowser/0.1/.click/info/org.kryogenix.fontbrowser.manifest is not a JSON object", and indeed that file on the device is blank. This worked and then just stopped working; what might I do to debug it?
[23:17] <daker> aquarius: the manifest file is corrupted
[23:17] <daker> aquarius: you need to uninstall the app
[23:17] <aquarius> daker, hm. How? I went looking for how to uninstall the app and couldn't work out how!
[23:18] <daker> aquarius: adb shell click unregister $PKGNAME --user=phablet
[23:19] <aquarius> I don't *know* the package name. And click says that I should use pkcon, and pkcon list-packages doesn't list my package :(
[23:20] <aquarius> hence confusion :(
[23:20] <daker> aquarius: adb shell click unregister org.kryogenix.fontbrowser --user=phablet
[23:20] <aquarius> ah, ok :)
[23:20] <daker> hope it will work :)
[23:26] <aquarius> daker, trying it now :)
[23:35] <aquarius> well, that problem is fixed
[23:35] <aquarius> now it can't connect to the mir server
[23:35] <aquarius> I think this emulator is screwed
[23:35] <aquarius> I shall try the other one
[23:37] <nik90> aquarius: you can run apps/scopes on the emulator for 15-20 times before having to restart it.
[23:38] <nik90> aquarius: this is because when you quit an app, it doesn't release the mir egl surface. As such after 15 tries, it causes it to fail
[23:38] <aquarius> ya, the newer emulator works
[23:38] <aquarius> although the dash *still* doesn't start
[23:38] <aquarius> sigh
[23:40] <aquarius> cheers, daker; at least I know that now :)
[23:41] <daker> aquarius: you can try : restart unity8-dash
[23:42]  * aquarius tries that
[23:42] <aquarius> yay, that fixed it
[23:42] <aquarius> worried that it didn't start, though
[23:42] <daker> :D
[23:42] <daker> maybe check the log
[23:43] <aquarius> which log? happy to check it
[23:43] <daker> ~/.cache/upstart/unity8-dash.log
[23:44] <aquarius> ah, I think that's just for this run of it, right?
[23:45] <daker> hm ?
[23:45] <aquarius> the dash wasn't running
[23:45] <aquarius> I restarted it
[23:46] <aquarius> and now it is running
[23:46] <aquarius> but I don't know whether tha log file has details of both
[23:46] <aquarius> or whether restarting it blanks the log file
[23:47] <daker> i don't think it blanks the log file
[23:47] <daker> you should see errors somewhere at the end of the file anyway
[23:47] <aquarius> yeah, I don't :(
[23:48] <aquarius> there are a bunch of random errors about not being able to get images, but nothing that looks like a crash
[23:48] <daker> aquarius: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1365733
[23:50] <daker> or https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362619
[23:51] <nik90> ahayzen: ping
[23:51] <ahayzen> nik90, pong
[23:51] <nik90> ahayzen: hey :), you use the ColumnFlow component in the music app remix. Did you make any modifications to the code when you imported it?
[23:52] <ahayzen> nik90, yeah lots...but we are looking to rewrite it as it doesn't quite meet our needs
[23:52] <aquarius> daker, I've commented on that bug, cheers
[23:52] <ahayzen> nik90, IIRC i put //custom next to most things i changed
[23:52] <nik90> ahayzen: ah ok..yeah when I used michael spencer's one, it resulted in https://imgur.com/esQtvMs where the order is a bit strange
[23:52] <ahayzen> woah
[23:53] <ahayzen> nik90, this is what ours looks like http://bazaar.launchpad.net/~music-app-dev/music-app/remix/view/head:/common/ColumnFlow.qml
[23:53] <nik90> ahayzen: pls do let me know when you think you got something which is generic and worth sharing.
[23:53] <ahayzen> nik90, but as i said we need to rewrite it...as it loads *everything* rather than what is just inview
[23:54] <ahayzen> nik90, which causes things to be slow
[23:54] <nik90> ah