[00:02] <ahoneybun> oh
[00:02] <ahoneybun> ahayzen_: I put them on different tabs
[00:03] <ahayzen_> ahoneybun, awesome :) you should be able to make that component generic as well
[00:04] <ahayzen_> ...if it is exactly the same on both tabs
[00:06] <ahoneybun> ahayzen_: my friend was saying that the app I am coping from iOS has a button that switch the buttons to edit the other textfield
[00:07] <ahayzen_> you could do that
[00:07] <ahoneybun> oh?
[00:08] <ahoneybun> that would be ideal
[00:08] <ahayzen_> just have a property TextField focusedField ... then set it to the one that the buttons are focussing on ... like you mean that both text fields are visible? you have a button to flip which the buttons write to?
[00:09] <ahoneybun> yea
[00:09] <ahayzen_> yeah do that ^^
[00:09] <ahoneybun> let me grab a screeni
[00:09] <ahayzen_> then have a button at the bottom to flip that has... onClicked: focussedField = focussedField == fieldA ? fieldB : fieldA
[00:10] <ahayzen_> then change when you click the number buttons to reference focussedField.text
[00:10] <ahoneybun> ahayzen_: too much at once lol
[00:11] <ahayzen_> hah
[00:11] <ahoneybun> not even to the property yet
[00:11] <ahayzen_> lol
[00:12] <ahayzen_> so like put the property somewhere where the buttons can access it...so like in the Column {}
[00:12] <ahoneybun> https://plus.google.com/+AaronHoneycutt/posts/jA63bs8DkCp?pid=6129216980386487874&oid=110525358571541799848
[00:13] <ahayzen_> so what changes the focus of the buttons?
[00:13] <ahoneybun> there is a button above the numbers
[00:14] <ahoneybun> each number
[00:14] <ahayzen_> ok i think what i said will work
[00:17] <ahoneybun> so a property
[00:17] <ahayzen_> so basically have a property storing the currently focussed textfield
[00:17] <ahoneybun> 2 buttons will switch the numbers button to effect each textfield
[00:18] <ahoneybun> yea
[00:18] <ahayzen_> then you have a button(s) that flip that value
[00:18] <ahoneybun> property TextField focusedField
[00:18] <ahoneybun> ?
[00:18] <ahayzen_> yup
[00:18] <ahoneybun> I would like a example if you could
[00:18] <ahayzen_> and maybe set it to the left one to start with
[00:18] <ahoneybun> I learn like that
[00:18] <ahayzen_> erm gimme like 15min+ i gotta collect washing :) \o/
[00:19] <ahoneybun>         property TextField focusedField = score1.text?
[00:19]  * ahayzen_ learns by example as well ;)
[00:19] <ahayzen_> property TextField focusedField = score1 ... was what i was thinking
[00:19] <ahoneybun> http://pastebin.ubuntu.com/10656622/
[00:19] <ahoneybun> k
[00:20] <ahayzen_> outside of anchors {} ;)
[00:20] <ahayzen_> i'll build something in a bit ;)
[00:20] <ahayzen_> brb
[00:21] <ahoneybun> k
[00:42] <ahayzen_> ahoneybun, something like this ? http://pastebin.ubuntu.com/10656754/
[00:43] <ahayzen_> or like you could use states if you started having more things depend on the currently focused field
[01:25] <ahoneybun> whats the add 1?
[01:25] <ahoneybun> oh
[01:26] <ahayzen_> a label lol
[01:27] <ahayzen_> ahoneybun, is that the sortof thing you were looking for?
[01:27] <ahoneybun> let me try
[01:29] <ahoneybun> from this example the buttons should not have ids
[01:30] <ahoneybun> ahayzen_: TypeError: Cannot read property 'text' of undefined
[01:30] <ahayzen_> ahoneybun, is that in mine or your code lol ?
[01:30] <ahoneybun> mine
[01:31] <ahoneybun> I replaced mine with ideas from yours
[01:31] <ahayzen_> ahoneybun, you probably haven't set an initial value for the focused field?
[01:31] <ahoneybun> ahayzen_: http://pastebin.ubuntu.com/10656994/
[01:31] <ahayzen_> ahoneybun, ah parent.focused won't work
[01:32] <ahoneybun> yea
[01:32] <ahayzen_> it would either be parent.parent.focused.text or put an id on the column and do ... columnId.focused.text
[01:32] <ahayzen_> ..or it might by inscope anyway so you can do focused.text
[01:32] <ahayzen_> one of them will work ;)
[01:33] <ahoneybun> ok parent.parent works
[01:33] <ahoneybun> now the button
[01:34] <ahoneybun> ahayzen_: it works!
[01:34] <ahayzen_> \o/
[01:34] <ahoneybun> brb bathroom and sode
[01:34] <ahoneybun> *soda
[01:34]  * ahayzen_ is likely to go to sleep
[01:37] <ahoneybun> back
[01:37] <ahoneybun> now to add a + and - buttons
[01:39] <ahayzen_> \o/
[01:40] <ahoneybun> can I have the 1 2 3 and so on buttons switch from adding to sub?
[01:41] <ahayzen_> adding to sub?
[01:41] <ahoneybun> + to -
[01:41] <ahoneybun> turn it from adding 1 to taking 1 away
[01:42] <ahayzen_> well it is appending it to a string
[01:42] <ahayzen_> but like you could take the substring of it
[01:42] <ahoneybun> oh?
[01:42] <ahayzen_> depends if you actually want them to act like push/popping from a string ... or like adding/subtracting from an integer?
[01:43] <ahoneybun> 2nd one
[01:44] <ahayzen_> you'll need todo parseInt each time you want to manipulate the value then ... or have another property that stores the actual value as an int and then the textfield just 'views' that
[01:46] <ahoneybun> way above me
[01:46] <ahayzen_> hah
[01:48] <ahoneybun> parseint?
[01:48] <ahayzen_> yeah https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt?redirectlocale=en-US&redirectslug=JavaScript%2FReference%2FGlobal_Objects%2FparseInt
[01:48] <ahayzen_> and then toString() but that could get messy
[01:48] <ahoneybun> oh
[01:49] <ahayzen_> it may be best to have a property inside the textfield with the actual value ... or to use a control that allows you to use ints rather than strings
[01:49] <ahoneybun> how would the property go?
[01:49] <ahayzen_> property int actualValue: 0
[01:49] <ahayzen_> then do text: actualValue.toString()
[01:49] <ahayzen_> ..i think...
[01:50] <ahayzen_> then you would be able to do parent.parent.focused.actualValue += 1 ... or -= 1
[01:50] <ahoneybun> would the property be below the other one?
[01:50] <ahayzen_> would need one inside each TextField
[01:50] <ahayzen_> but then the type of the other property may need to change to var rather than TextField as well lol
[01:51] <ahoneybun> oh boy/
[01:51] <ahayzen_> lol
[01:51] <ahoneybun> property inside the textfield {} ?
[01:51] <ahayzen_> yup
[01:52] <ahoneybun> { property}
[01:52] <ahayzen_> hm?
[01:52] <ahayzen_> like TextField { property int actualValue: 0 }
[01:53] <ahayzen_> and then text: actualValue.toString() as well
[01:53] <ahoneybun> k
[01:53] <ahoneybun> for the buttons?
[01:53] <ahoneybun> textfield?
[01:54] <ahayzen_> the buttons need to have their parent.parent.focused.text changed to parent.parent.focused.actualValue
[01:56] <ahoneybun> ok
[02:00] <ahoneybun> how do I switch the buttons from + to - ?
[02:00] <ahayzen_> heh
[02:01] <ahayzen_> have another var ... which you set to 1 or -1 ... then do ... actualValue += 8 * myVar ... so it would do += 8 * 1  .... or += 8 * -1
[02:02] <ahayzen_> (for the button for 8 ;) )
[02:02] <ahoneybun> ahayzen_: var?
[02:02] <ahayzen_> property
[02:02] <ahoneybun> property var
[02:02] <ahayzen_> property int
[02:02] <ahayzen_> or var would work as that can be anything
[02:03] <ahoneybun> some many "..." lol
[02:03] <ahoneybun> it makes it hard to read
[02:03] <ahayzen_> http://doc.qt.io/qt-5/qtqml-typesystem-basictypes.html
[02:03] <ahayzen_> haha
[02:03] <ahoneybun> plus I'm back at C++ or code in gerenel
[02:04] <ahoneybun> ahayzen_: can you write what the 8 button property would look like?
[02:04] <ahayzen_> ok you wan't another property at the column level. which you then set to 1 (for addition) or -1 (for subtraction)
[02:05] <ahayzen_> then your onClicked for the button, say 8, would change to be parent.parent.focused.actualValue += 8 * myProperty
[02:05] <ahayzen_> you may also want to look at the repeater ;) http://doc.qt.io/qt-5/qml-qtquick-repeater.html
[02:06] <ahoneybun> property var myProperty: 1 or -1?
[02:07] <ahayzen_> you would change its value from another set of buttons ;)
[02:07] <ahoneybun> ?
[02:08] <ahayzen_> so have a button to do addition/minus mode?
[02:08] <ahoneybun> I have a button to switch modes
[02:09] <ahayzen_> yeah which then switches the property to be either 1 or -1
[02:09] <ahoneybun> http://pastebin.ubuntu.com/10657197/
[02:09] <ahoneybun> I'm working on the 1 button
[02:10] <ahayzen_> yeah like that will by subtracting at the moment?
[02:10] <ahayzen_> so make another button which changes myProperty = 1 then it'll be adding :)
[02:11] <ahoneybun> oh ok
[02:11] <ahayzen_> ahoneybun, anyway mate i've gotta go to sleep now ;) have fun :)
[02:11] <ahoneybun> thanks ahayzen_ alot
[02:11] <ahayzen_> no problem :)
[02:11] <ahoneybun> have some good sleep
[02:11] <ahayzen_> thanks night o/
[02:46] <AskUbuntu> error in uploading click package to ubuntu app store | http://askubuntu.com/q/600107
[03:56] <mhall119> ahoneybun: I am now, if you still need help
[03:58] <ahoneybun> mhall119: ahayzen has been helping a lot with *our* new app
[03:58] <ahoneybun> a scoreboard
[03:58] <mhall119> nice, I figured when I saw ahayzen talking to you that you didn't need me anymore :)
[03:59] <ahoneybun> mhall119: I sent a email to the membership board
[03:59] <mhall119> \o/
[03:59] <ahoneybun> always need you mhall119 :)
[04:00] <mhall119> :)
[04:00] <ahoneybun> mhall119: http://imgur.com/dxXQE8x
[04:02] <ahoneybun> my app also has 290 users now!
[04:03] <mhall119> the beginners app?
[04:03] <ahoneybun> yep
[04:03] <mhall119> awesome
[04:03] <ahoneybun> yea
[04:04] <ahoneybun> it was 240 on friday
[04:04] <ahoneybun> then 271 on sat
[04:04] <ahoneybun> now 290
[04:04] <ahoneybun> is there a official facebook page
[04:04] <ahoneybun> ?
[04:05] <mhall119> for what?
[04:05] <ahoneybun> Ubuntu
[04:05] <ahoneybun> in general
[04:05] <mhall119> https://www.facebook.com/ubuntulinux
[04:06]  * ahoneybun needs to make a icon for gazeteer
[04:06] <ahoneybun> thats community managed
[04:06] <mhall119> https://www.facebook.com/ubuntuappdev for appdev
[04:06] <mhall119> that's our official page
[04:06] <ahoneybun> ok
[04:06] <ahoneybun> I did not want to put a non offical page in my app
[04:07] <ahoneybun> in case someone put some bad stuff on there and hurt the image of ubuntu
[04:14] <ahoneybun> mhall119: I think like 5 or 6 people would vote for more including you for the Board
[04:17]  * mhall119 is already on a Council
[04:19] <akiva-thinkpad> whats up everyone.
[04:19] <akiva-thinkpad> bzoltan_, or zbenjamin -- ping
[04:25] <ahoneybun> hey akiva-thinkpad
[04:25] <akiva-thinkpad> ahoneybun, o/ whats new?
[04:25] <ahoneybun> akiva-thinkpad: almost 300 users
[04:25] <akiva-thinkpad> lol triple :)
[04:25] <akiva-thinkpad> nice stuff
[04:26] <ahoneybun> yea
[04:26] <ahoneybun> making a new app with ahayzen's help
[04:30] <ahoneybun> mhall119:
[04:30] <ahoneybun> lint_maintainer_domain
[04:30] <ahoneybun>         email=aaronhoneycutt@ubuntu.com matches special domain=com.ubuntu.aaronhoneycutt.gazeteer
[04:30] <ahoneybun> ?
[04:55] <akiva-thinkpad> ahoneybun, new app?
[04:57] <ahoneybun> yea
[04:57] <ahoneybun> a score keeper
[04:59] <akiva-thinkpad> ahoneybun, for golf?
[05:01] <ahoneybun> anything really
[05:01] <ahoneybun> it was for a card game
[05:01] <akiva-thinkpad> :)
[05:01] <ahoneybun> but could be used for a lot of things
[05:02] <ahoneybun> akiva-thinkpad: I think it is pretty cool
[05:02] <ahoneybun> I could not find anything like it on the store currently
[05:03] <akiva-thinkpad> ahoneybun, if you have a use for it, then this is reason enough to have it.
[05:03] <ahoneybun> yea
[05:04] <ahoneybun> I just need to get the icon made up
[05:13] <ahoneybun> akiva-thinkpad: still around?
[05:13] <akiva-thinkpad> ahoneybun, yah
[05:14] <ahoneybun> akiva-thinkpad: I'm getting a warning from the SDK
[05:14] <akiva-thinkpad> ?
[05:15] <ahoneybun> let me get it in a pastebin
[05:15] <ahoneybun> email=aaronhoneycutt@ubuntu.com matches special domain=com.ubuntu.ahoneybun.gazeteer
[05:19] <akiva-thinkpad> sounds like something in a json file
[05:21] <ahoneybun> com.ubuntu.ahoneybun.gazeteer
[05:21] <ahoneybun> Aaron Honeycutt <aaronhoneycutt@ubuntu.com>
[05:21] <ahoneybun> name and maintainer
[05:29] <ahoneybun> The uploaded package name (com.ubuntu.aaronhoneycutt.gazeteer) does not use your namespace (aaronhoneycutt)
[05:38] <akiva-thinkpad> hmmmm
[05:38] <akiva-thinkpad> don't know;
[05:43] <ahoneybun> I can't upload it till I fix it so..
[05:44] <ahoneybun> I'll wait till more people are online
[05:44] <ahoneybun> thanks akiva-thinkpad
[07:46] <davidcalle> Morning all o/
[07:47] <seb128> lut davidcalle
[07:47] <davidcalle> Hey seb128 :)
[08:28] <mrqtros> popey hello! If you will have some free time, please, test it: https://code.launchpad.net/~mrqtros/ubuntu-rssreader-app/ubuntu-rssreader-app-startup-time/+merge/253769
[08:29] <popey> mrqtros: saw that over the weekend, will take a look, sure
[08:33] <dholbach> good morning
[08:34] <seb128> hey dholbach
[08:35] <mrqtros> Hi, dholbach
[08:37] <dholbach> hi seb128
[08:37] <dholbach> hi mrqtros
[08:37] <mrqtros> popey thanks!) Joey will review too, I hope this will be enough) If you will like it, we can update version in the store. I think that it's time to up minor version ;) After transition to C++ we can up major version to 1.0
[09:38] <akiva-thinkpad> !ping
[10:08] <bzoltan_> akiva-thinkpad: hello, what's up
[10:09] <akiva-thinkpad> bzoltan_, on the autopilot plugin; I could not find the widget in the run config to insert my widget into. Its not in the object pool, or a child of anything. I was wondering if I could make it my own mode instead; that would be easier I think.
[10:10] <akiva-thinkpad> does that make sense?
[10:11] <akiva-thinkpad> give it its own mode*
[10:11] <akiva-thinkpad> I don't know why I said "my"
[10:12] <akiva-thinkpad> I made a thread about it in qt center; I didn't get an answer http://www.qtcentre.org/threads/61656-Cant-find-object-for-quot-Mode-Projects-gt-Project-gt-Build-amp-Run-gt-Kit-gt-Run-quot-to-add-widget
[10:13] <akiva-thinkpad> My understanding is that if I wanted to add a configuration widget into the run config of a project, I would need to find the widget to insert my widget into from the object pool.
[10:22] <bzoltan_> akiva-thinkpad:  upstream does not want to overload the fancytabbar with new modes. That is only a simple point...maybe not even th emost relevant.
[10:22] <akiva-thinkpad> bzoltan_, does my problem make sense though?
[10:23] <akiva-thinkpad> bzoltan_, the only other way I can figure this, other than coupling it with a different mode,
[10:23] <bzoltan_> akiva-thinkpad:  I do not think that the widget what you need is exposed... so I doubt that you can add a new widget there
[10:23] <akiva-thinkpad> bzoltan_, so I would need to push to qtcreator, an addToObjectPool() right?
[10:23] <bzoltan_> akiva-thinkpad:  I am out of office today... and zbenjamin is off too, so it is hard to figure out much :)
[10:25] <akiva-thinkpad> bzoltan_, thats fine. I just want to tie up this loose end. Do you think i should see if qtcreator would allow me to push a patch that would expose that widget?
[10:25] <akiva-thinkpad> or should I ask you later when you are in the office?
[10:26] <bzoltan_> akiva-thinkpad: Not a bad idea to check with the upstream
[10:26] <akiva-thinkpad> bzoltan_, okay i'll try that then. enjoy your day off
[10:26] <bzoltan_> akiva-thinkpad:  thanks :)
[11:12] <dholbach> dpm, I look forward to rtm moving to vivid at some stage, so we can drop the hack for bug 1434415 :)
[11:13] <dholbach> it'll require all of us hackers to move to vivid too (it's partly not on my radar because I moved to vivid a while ago :))
[11:28] <akiva-thinkpad> dholbach, huh... I just realized there is no animal background for vivid
[11:28] <akiva-thinkpad> animal wallpaper*
[11:29] <dholbach> akiva-thinkpad, you don't want me to fix that
[11:29] <akiva-thinkpad> dholbach, lol
[11:29] <dholbach> it'd probably look a lot like http://www.goparoo.com/kids/drawings/anna-africa-monkey.gif
[12:11] <daker> ping nik90 (dekko on lxc question)
[12:41] <nik90> daker: pong
[12:42] <daker> nik90: do you know how can i run dekko on lxc ?
[12:42] <daker> dekko doesn't run on 14.04
[12:42] <nik90> daker: Have you got the ubuntu-sdk libs installed on lxc? Or do you need help with that as well?
[12:42] <daker> yes
[12:42] <daker> from A-Z
[12:43] <nik90> daker: http://nik90.com/fiddling-around-with-lxc-containers/
[12:43] <nik90> daker: ^^ should help with getting lxc up and ready from scratch on 14.04
[12:43] <balloons> So I see https://code.launchpad.net/~dholbach/help-app/1434125/+merge/253658 is still a thing dholbach :-)
[12:44] <daker> nik90: ok i'll try it
[12:44] <nik90> daker: once you get lxc up and running, you should be able to open a lxc terminal and run the cmake scripts for dekko like you always do
[12:45] <nik90> daker: the only drawback of lxc is that it doesn't allow creating chroots that one might need to run dekko on the phone. But I guess that time you can always use the host machine for that
[12:46] <dholbach> balloons, yes - didn't ahve time over the WE
[12:46] <daker> nik90: no i don't need a chroot, i only want to run dekko on desktop so i can fix/test stuff
[12:51] <mardy> bzoltan_: hi! Do you have a minute to talk about bug 1393697?
[12:52] <bzoltan_> mardy:  that issue is long fixed
[12:53] <nik90> daker: ok
[12:54] <bzoltan_> mardy: but keep in mind that it is available only for Vivid. because it needed a qtbase update what was hardly possible for Utopic.
[12:55] <ogra_> nik90, it would be nice if the handle of the circle menu could drop a slight shadow ... i'm using my webapp hack wih all my webapps locally and notice that on white pages the handle kind of vanishes visually
[12:55] <mardy> bzoltan_: right, so, do I understand correctly that this does not depend on which Ubuntu version the developer is using, but it depends only on the targetted framework?
[12:55] <mardy> bzoltan_: I'm using vivid, but my click framework is 14.10
[12:55] <bzoltan_> mardy:  Yes
[12:56] <faenil> contacts app shows blank page when tapping on "Import contacts via Google" but the phone is not connected
[12:56] <mardy> bzoltan_: not even if we pay Mirv a beer? ;-)
[12:57] <bzoltan_> mardy: we need to offer something harder to him and to a bunh of other folks :)
[12:57] <ogra_> which folks do you want to offer to Mirv ?
[12:57] <mardy> ogra_: funny one :-)
[12:58] <mardy> bzoltan_: is it only about qtbase, or would there need other packages to be updated (click, I guess)?
[12:58] <mardy> "only" :-)
[13:02] <dobey> mardy: backporting the new qtbase to 14.10/rtm is probably not something you want to have done :)
[13:05] <Mirv> qt 5.4 comes to rtm by making vivid the rtm :)
[13:06] <dobey> yeah taht
[13:06] <Mirv> so "just" fix all the vivid bugs
[13:07] <Mirv> mardy: qtbase can't be updated alone, it needs to be all 20 Qt modules plus rebuilds of various components of ours (which means backporting qt 5.4 related fixes from trunks)
[13:07] <bzoltan_> mardy: qtbase and click, that is all
[13:08] <Mirv> but speaking about backporting, if someone can pinpoint the needed feature from 5.4 code commits and it can be backported to 5.3, that would be possible and would only affect qtbase
[13:08] <bzoltan_> mardy:  for the sdk... and as Mirv sai, all other package what is built on qtbase should be rebuilt... joyride
[13:09] <Mirv> oh right now reading backlog, cross qmake package would probably be doable by just updating qtbase, unless there was something 5.4 specific in there.
[13:10] <dobey> Mirv: but that would still break the framework
[13:11] <Mirv> ok
[13:11] <dobey> Mirv: because building against qtbase 5.4 won't be runnable by people who don't have an updated image
[13:11] <Mirv> I meant adding the qmake binary package to 5.3rtm qtbase packaging
[13:12] <dobey> oh, if it doesn't need qtbase 5.4 it might be ok
[13:12] <Mirv> although getting click + qmake-cross to work involved some ugly/unpleasant apt problems when creating chroot
[13:13] <dobey> i'm just very wary of such things, because we recently ran into a problem after 5.4 landed in vivid, with the way clicks were being built in jenkins
[13:13] <dobey> as they were being built on vivid, not rtm
[13:14] <Mirv> I'm also wary, it's a rather complex path to fully enable click cross-qmake building in rtm since it wasn't a piece of cake in vivid either when it was done
[13:14] <Mirv> and introducing it had a potential to break image building (which it did) etc
[13:14] <mardy> Mirv: the description of bug 1393697 says that that binary is provided with qt 5.3
[13:16] <Mirv> mardy: in 5.3.2, in vivid, involving many other updated packages like click, ubuntu-touch-meta and even Oxide (which was then reverted later though) because it complicates the click chroot creation afaik
[13:16] <Mirv> mardy: so getting qmake-cross package in rtm 5.3.0 qtbase is not the biggest problem, but getting something functional using it is more complex
[13:17] <dobey> anyway, vivid is supposed to be "stable" soon, right? :)
[13:17] <Mirv> yes, in a "few weeks". again depending on how quickly all bugs are fixed :)
[13:18] <Mirv> it might also take a few weeks before we'd have qmake-cross working inside click chroot for rtm-14.09
[13:19] <mardy> Mirv: so, you are saying that if I isolate the patch which generates qmake-cross and apply that to 5.3.0, I still won't be able to use it?
[13:20] <Mirv> mardy: no, I didn't read the backlog at that point. the commit is there, you can recompile qtbase, but getting the qmake into automatically created click chroots might be more complicated. but I think you might even just get the 5.3.2 qmake-cross and try it out.
[13:20] <Mirv> mardy: the packaging change was http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src/revision/199
[13:21] <Mirv> plus some fixes in later commits
[13:22] <Mirv> mardy: .deb at https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.3.2+dfsg-4ubuntu9/+build/6754505/+files/qt5-qmake-arm-linux-gnueabihf_5.3.2%2Bdfsg-4ubuntu9_amd64.deb
[13:22] <Mirv> mardy: if you copy the binary manually to the chroot, it might work (but it might be it would need to be built from 5.3.0)
[13:22] <Mirv> you can open the .deb with file-roller and extract the file from /usr/bin/
[13:23] <mardy> Mirv: excellent, I'll try
[13:23] <Mirv> mardy: yeah, sorry, it all depends on whether you need something to hack with or if you want something Zoltan offers to all users :)
[13:25] <mardy> Mirv: first let's see how well it works, then we can think whether it's worth the pain :-)
[13:25] <ogra_> dobey, FSVO "soon"
[13:26] <dobey> ogra_: well, hopefully before W is stable ;)
[13:27]  * ogra_ sstill has his doubts :P
[13:27] <dobey> heh
[13:28] <nik90> ogra_: I'm gonna be cheeky and say patches welcome :P
[13:28] <nik90> ogra_: I will see what I kind do
[13:29] <ogra_> nik90, me too then :)
[13:29] <nik90> s/kind/can
[13:29] <nik90> :D
[13:30] <nik90> t1mp: I added the example to the MP. I am hoping that I won't be asked to write a test :P
[13:33] <daker> dholbach: yo, do you remember this place https://youtu.be/tNPZGc0WmfM?t=18s ?
[13:34] <dholbach> daker, which nanosecond shot do you mean? :)
[13:34] <dholbach> but yeah - very nice :)
[13:36] <daker> dholbach: this one https://i.imgur.com/1xUTFIo.png
[13:37] <dholbach> yes, thought so :)
[13:37] <daker> => https://plus.google.com/photos?hl=en%26gpsrc=gplp0&pid=5697853008942523554&oid=109795858099658821877
[13:38] <dholbach> beautiful, yes :)
[13:39] <daker> now let's wait for the movie :)
[13:48] <nik90> ogra_: Is the shadow sufficient? http://imgur.com/bfR0aPr
[13:50] <ogra_> nik90, totally !
[13:51] <ogra_> nik90, i also added a minor hack to make buttons active/inactive in my branch ... (probably wrongly by using opacity 0.5 for the action icon)
[13:51] <ogra_> since i want the back/forward actions to be non-active when there is no history in the webview
[13:52] <nik90> ogra_: ah, well I am converting those buttons into actionButtons (currently they are basically a qml rectangle) which would provide haptic feedback and also expose the "enabled" property.
[13:52] <nik90> ogra_: But I guess visually that can be indicated by reducing the opacity of the button
[13:52] <ogra_> line 83 and 92 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/Main.qml
[13:53] <ogra_> line 11 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/UCSComponents/RadialAction.qml and line 96 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/UCSComponents/RadialBottomEdge.qml
[13:54] <nik90> ogra_: ok I will add that functionality as well in UCS. You would get that automatically when you update the component using ucs
[13:54] <ogra_> (oh, and 118 in the last file)
[13:54] <ogra_> nik90, heh, well, my approach was rather hackish ... cp /opt/..../dekko/.../UCS /opt/.../blah/
[13:55] <ogra_> i'll roll a proper build script later :)
[13:55] <nik90> ogra_: hehe..whatever works for you
[13:55] <ogra_> (this is all after work stuff so it goes a bit slower)
[13:57] <LangeOortjes> Hey, I am developing my first Ubuntu (Touch) app, which I hope to run on my Aquaris 4.5E. Now I've seen that the ListItems I plan to use intensively are being overhauled in Ubuntu.Components 1.2. Now my question is, should I target 1.2 or 1.1? My answer will depend on what the Aquaris will run and how fast updates will be pushed to that device. Is there documentation on this matter?
[14:00] <balloons> LangeOortjes, I would urge you towards using the new components.
[14:01] <LangeOortjes> balloons, any pointers as to what sites/repositories/lists to follow to keep in the loop on these developments?
[14:02] <nik90> LangeOortjes: the phones (BQ, N4, Meizu) etc will all transition to vivid (which provides the new listitems) soon enough ~2-10 weeks
[14:02] <LangeOortjes> that's perfect!
[14:02] <nik90> LangeOortjes: the transition will happen when the QA team give it the green signal *only* everything continues to work as expected
[14:02] <nik90> without any regressions
[14:03] <LangeOortjes> that makes sense
[14:03] <nik90> LangeOortjes: so if you want to release your app now then you would need to target 1.1. If not go for 1.2
[14:03] <balloons> LangeOortjes, to stay in the loop, checkout the phone mailing list: https://lists.launchpad.net/ubuntu-phone/
[14:03] <balloons> and most importantly have fun LangeOortjes !
[14:04] <nik90> LangeOortjes: the current core apps (like clock) for instance, have 2 branches one for the current rtm and another for 1.2 (devel)
[14:04] <nik90> LangeOortjes: good luck with your app!
[14:04] <LangeOortjes> balloons, fun I am already having.
[14:05] <LangeOortjes> nik90, thanks
[14:06] <t1mp> nik90: it is always good to write a test ;)
[14:08] <nik90> t1mp: ;-)
[14:08] <t1mp> nik90: I approved https://code.launchpad.net/~nik90/ubuntu-ui-toolkit/fix-slider-bubble-width/+merge/253620
[14:08] <nik90> thnx
[14:08] <t1mp> nik90: no happroval yet, we are using our staging to land some final things to vivid, after that we'll land new stuff to staging
[14:08] <nik90> t1mp: sure np. I will try to be on the lookout for these kind of low hanging bugs
[14:09] <t1mp> ok :) I'll let you know when I happrove it
[14:11] <nik90> t1mp: If I want to backport to vivid later, I am guessing I would need to propose it against vivid as well? Considering this is just a bug fix..
[14:12] <nik90> t1mp: also, on vivid desktop do you open the toolkit pro file and build it using qtcreator? At the moment I am doing a hackish way of making code changes in qtc and then building and testing it via the terminal
[14:13] <zsombi> t1mp: nik90: this change has no new API to 1.2 so why not to happrove it?
[14:13] <zsombi> nik90: open Ubuntu-sdk.pro in QtC
[14:13] <zsombi> nik90: then build it
[14:14] <nik90> zsombi: I see that it defaults to debug mode, I suppose that is fine?
[14:14] <zsombi> nik90: if you want to run some test app you can add to run
[14:14] <zsombi> nik90: yes, you can change it any tiem to release...
[14:14] <zsombi> time
[14:14] <nik90> zsombi: ok,
[14:15] <zsombi> nik90: if you disable shadow build, and want to run some sample test app from tests/resources, simply use -I modules argument to qmlscene
[14:16] <zsombi> nik90: also, you can launch teh test apps using tests/launcher/launcher with -I modules and -touch
[14:16] <zsombi> nik90: that can be helpful as you get all mouse events as touch
[14:16] <nik90> ah ok
[14:20] <t1mp> zsombi: is ucdeprecatedtheme.cpp new or a copy of an existing file?
[14:21] <zsombi> t1mp: it's a copy of UCTheme API, prepared to deisplay deprecation note on MR #4
[14:21] <t1mp> zsombi: I thought we only land approved bug fixes in vivid now?
[14:21] <zsombi> t1mp: wasn't this a bugfix?
[14:21] <zsombi> t1mp: bugfixes, have you seen any special list that limits us to fix only certain bugs?
[14:22] <t1mp> zsombi: yes it is. What I thought is that we have about 4 bugs that we agreed on for vivid and the rest goes to w?
[14:22] <t1mp> zsombi: no I haven't seen that list
[14:23] <t1mp> zsombi, nik90: ok, this MR looks safe. I'll happrove it.
[14:23] <zsombi> t1mp: afaik only new features go to w, bugfixes still go to Vivid...
[14:23] <t1mp> ok
[14:24] <nik90> t1mp: woohoo. thnx
[14:24] <zsombi> t1mp: we haven't got any blockade on bugfixing for Vivid yet...
[14:28] <zsombi> t1mp: palette change and MainView's auto-theming on backgroundColor is conflicting lilke hell... binding loop and crash is the result if I change the default palette's normal.background color
[14:28] <mardy> Mirv: I launched qmake-cross in the chroot, and it complains about: Could not find qmake configuration file ubuntu-arm-gnueabihf-g++.
[14:28] <t1mp> zsombi: in the theming MR, what's with the docs? In uctheme.cpp you have the same as in ucdeprecatedtheme.cpp, only in uctheme, the ! after /* is missing. Is that intentional?
[14:29] <zsombi> t1mp: I remove dteh UCTheme docs in purpose, as it'll be re-introduced in -2
[14:29] <zsombi> 02
[14:29] <t1mp> zsombi: didn't we get rid of the auto-theming on backgroundColor?
[14:29] <zsombi> t1mp: and will be introduced ans ThemeSettings
[14:29] <t1mp> zsombi: maybe we should get rid of the auto-theming in 1.3
[14:30] <zsombi> t1mp: yes.... or add some property to disable it :/ otherwise lots of apps will be broken
[14:30] <t1mp> zsombi: no the apps import 1.2. When they change to 1.3, they have to set the theme in their MainView.
[14:31] <zsombi> t1mp: right...
[14:31] <t1mp> zsombi: or shall we have a property bool useDeprecatedAutoTheming in MainView? :D
[14:31] <zsombi> t1mp: yeah :D
[14:31] <t1mp> I knew you'd like it :p
[14:31] <zsombi> t1mp: useOldFartAutoTheming
[14:32] <t1mp> zsombi: apps going to 1.3 will have to update some stuff anyway, because the property useDeprecatedToolbar that they most likely set to false, no longer exists
[14:33] <zsombi> t1mp: that doesn't exist already in 1.2
[14:33] <t1mp> ehm
[14:33] <t1mp> yeah I'm confusing the versions...
[14:33] <zsombi> :)
[14:34] <t1mp> I'm happy with 1.2
[14:35] <t1mp> but 1.3 will be even better :)
[14:35] <zsombi> t1mp: useDeprecatedToolbar was removed in 1.2, this affects 1.3
[14:35] <t1mp> yes, I know. I realized that I got confused.
[14:37] <t1mp> zsombi: didn't we think of an alternative name for "styleset"?
[14:37] <Mirv> mardy: seems it's in a wrong place, open up http://launchpadlibrarian.net/195952527/qt5-qmake_5.3.2%2Bdfsg-4ubuntu9_amd64.deb and copy usr/lib/x86_64-linux-gnu/qt5/mkspecs/ubuntu-arm-gnueabihf-g++ to the chroot too...
[14:37] <zsombi> t1mp: yes, theme... do you still see them?
[14:37] <t1mp> zsombi: yes, there are two FIXMEs that mention styleset, and a directory tests/resources/styleset
[14:38] <zsombi> t1mp: ah the directory.. .the FIXMEs are gonna be removed anyway later, so those are not so relevant
[14:40] <mhall119> nik90: I have a new theme manager for you :)
[14:40] <nik90> ogra_: I added the haptic feedback and dropshadow to the upstream ucs component in https://code.launchpad.net/~nik90/component-store/add-haptic-shadow-radial/+merge/253832. Since you took the component from dekko, you will need to wait for them to update it.
[14:40] <zsombi> mhall119: nik90: can you guys also show me that ThemeManager?
[14:40] <ogra_> nik90, yeah, just browsing the tree
[14:41] <ogra_> nik90, i dont think i'll stay with the hackish way of cp'ing stuff around on the phone :)
[14:41] <nik90> mhall119: ooh today has been a productive day for me..only gets better with your ThemeManager
[14:41] <zsombi> nik90: we also have Haptics singleton, perhaps you wanna use that!
[14:41] <nik90> ogra_: it seems that the dekko's radial menu version adds support for the text and iconSource property which isnt yet upstreamed
[14:41] <ogra_> ah
[14:42] <nik90> zsombi: I did see that, but that only comes with Ubuntu.Componennts 1.2 ?
[14:42] <mhall119> nik90: zsombi: http://bazaar.launchpad.net/~mhall119/ureadit/3.0/view/head:/themes/ThemeManager.qml is the manager itself
[14:42] <mhall119> http://bazaar.launchpad.net/~mhall119/ureadit/3.0/view/head:/main.qml#L37 shows how I use it
[14:42] <nik90> zsombi: When we switch to vivid, I will move to the Haptics Singleton
[14:42] <zsombi> nik90: ok
[14:42] <zsombi> mhall119: lemme check that
[14:42]  * nik90 looks
[14:42] <mhall119> zsombi: it doesn't use your stuff (yet, I'm trying to understand how to make them work together)
[14:43] <zsombi> mhall119: I asked it as we'll have some changes there with teh subtheming
[14:44] <mhall119> zsombi: my stuff is mostly concerned with color changes
[14:44] <mhall119> nothing more complex than that
[14:44] <zsombi> mhall119: byt are you using the UITK themes, liek Ambiance or SuruDark?
[14:44] <zsombi> but
[14:44] <mhall119> zsombi: not quite, I didn't know how to import them to use their values
[14:45] <zsombi> mhall119: Ambiance: import Ubuntu.Components.Themes.Ambiance
[14:45] <zsombi> mhall119: same for SuruDark
[14:45] <zsombi> mhall119: and of course the version is 1.2
[14:46]  * mhall119 will try and make those changes
[14:46] <zsombi> mhall119: and if you want to set the app theme, Theme.name = <theme_name>
[14:47] <zsombi> mhall119: nik90: in 1.3 this will become like theme.name: <theme_name>
[14:47] <nik90> mhall119: the new theming infrastructure that was blogged by zsombi is a combination of app specific and component specific theming. Although at the moment it is only limited to a few components that are documented in the API docs at the moment.
[14:47] <zsombi> mhall119: nik90: note the difference is not only the smal caps theme, but also teh declarative value assignment
[14:47] <mhall119> zsombi: you know what would be really useful to me? Being able to specify the color for the Icon in an Action, is that planned?
[14:48] <zsombi> mhall119: nik90: and you will be able to set palette runtime in declarative way, as well as declare a Dialog using a different theme than the rest of teh app
[14:48] <t1mp> zsombi: I left a few commentso n https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/01-multiple-theme-engines/+merge/251942
[14:49] <mhall119> zsombi: nice
[14:49] <zsombi> mhall119: not atm, but you can file a bug - if no tthere already - to be able to do some hinting on the actions
[14:50] <t1mp> mhall119: what is the use case for setting to color of an action? Do you want different colors of actions in the header?
[14:50] <zsombi> mhall119: that particular thing is not really a theming issue, is more like Action specific
[14:50] <zsombi> mhall119: but if the action visualization is context specific, that can be done on the given context
[14:52] <zsombi> nik90: mhall119: but as we discussed with t1mp, we most likelly have to get rid o fthe auto-theming we have in MainView... it causes lots of trouble, and the binding loop sometimes comes back even with the current 1.2 theming
[14:53] <t1mp> if Action gets a color, in each component where you can set an action we have to determine what the color does. For example, in the header it may change the icon color, in a regular button the button color
[14:53] <nik90> zsombi: auto-theming as in if the app dev chooses a dark mainView background color, the text automatically using a lighter color?
[14:54] <zsombi> nik90: yes
[14:54] <zsombi> nik90: the backgroundColor forces the theme to be set to SuruDark when its luminance < 85%
[14:55] <zsombi> nik90: if I change the palette values of the normal.background, I end up in a binding loop, and even worst, binding transfer crash
[14:55] <nik90> ack.
[14:56] <zsombi> nik90: I'm trying to find a workaround, but I doubth it can be solved...
[14:57] <nik90> zsombi: so in 1.3, it would be such that the app dev should use the theming stuff you showed in your blog post to theme every necessary component he uses in his app at least with regards to the colors used.
[14:57] <zsombi> nik90: nope ;)
[14:57] <zsombi> nik90: more
[14:58] <zsombi> nik90: no need to wait till Component.Completed
[14:58] <zsombi> nik90: you can do it straight in teh MainView { theme.name: "Ubuntu.Components.Themes.SuruDark" }
[14:59] <nik90> ok
[15:00] <zsombi> wow...
[15:01] <zsombi> woooooooooow!!!!
[15:01] <nik90> ?
[15:02] <zsombi> nik90: I must test it, but seems I managed to get rid of the binding loop :D
[15:02] <nik90> oh!
[15:02] <JamesTait> In a scope, is a card a single item in the grid? e.g. in the Store scope, "Top Apps" would be a category with, say, six apps, and each app would be a card? And "App of the week" would be a category with a single card?
[15:02] <zsombi> nik90: haha, I did! :D
[15:03] <zsombi> t1mp: ^
[15:04] <zsombi> nik90: also, if you want an AMbiance themed app to open  a Dialog wiuth SuruDark theme, you define your Dialog with Dialog { theme: ThemeSettings { name: "Ubuntu.Components.Themes.SuruDark" } } and that's it
[15:05] <t1mp> zsombi: good :)
[15:05] <zsombi> nik90: or , if you want to have a different palette than the default Ambiance: Dialog { theme: ThemeSettings {name: parentTheme.name; palette: Palette { normal.foreground: "pink" } } }
[15:06] <nik90> zsombi: so the components provide a "theme" property which one can use to theme them individually, that's sweet
[15:06] <zsombi> nik90: yep
[15:06] <zsombi> nik90: and will also gave a font property
[15:06] <zsombi> have
[15:06] <t1mp> nik90: yes, that will theme the item and all its children (unless the children override it by setting another theme) :)
[15:06] <nik90> zsombi: yeah all the properties defined in styles/Themes/Ambiance/DialogStyle.qml I guess
[15:07] <zsombi> nik90: right... and we hope we'll have more API in the Ubuntu.Components.Styles
[15:07] <ahayzen> balloons, ping
[15:07] <nik90> zsombi: precisely
[15:07] <mflow> Any ideas what I get undefined reference to symbol 'dlclose@@GLIBC_2.2.5' ?
[15:08] <balloons> ahayzen, pong
[15:08] <ahayzen> balloons, are you able to easily trigger jenkins on a non-team member mp? ... eg this one https://code.launchpad.net/~darran-kelinske/music-app/lp_bug_1428454/+merge/253566 ?
[15:08] <zsombi> nik90: but, to be honest, a MainView's backgroudn I'd rather change with MainView { theme.palette: Palette { normal.background: "whatever_color" } }
[15:09] <zsombi> nik90: because then teh background can be valid for the whole app, would give more consistency in colors
[15:09] <nik90> zsombi: I agree
[15:09] <zsombi> nik90: changing teh MainView's bacgroundColor only changes teh app's background, but perhaps that's not only the only place one would like to see the color changed...
[15:10] <zsombi> nik90: and, apps could have their own colors on the Ambiance theme. without defining their own theme
[15:10] <dholbach> balloons, I just had a chat with dpm - would it be possible to hook up the help app with the jenkins infrastructure?
[15:12] <balloons> dholbach, ahh right. Certainly, we'll just need to ask CI to coordinate. I think I might be able to propose an MP for some of it to make there lives easier
[15:12] <dholbach> balloons, cool - what do we need to do?
[15:12] <balloons> dholbach, we should also add it to the core apps group so jenkins can acess it
[15:13] <ahayzen> balloons, also i was thinking for your quality section of developer.ubuntu.com ... is there a section on pep8/pyflakes? as it would be useful to be able to point someone to a page explaining what it is, how they can set it up etc
[15:13] <dholbach> yes, sure - do you think you could look into that?
[15:13] <nik90> ahayzen: ooh +1
[15:13] <balloons> dholbach, sure thing
[15:14]  * dholbach hugs balloons
[15:15] <balloons> ahayzen, I added him to the test writers team; shouldn't be a problem anymore
[15:16] <ahayzen> balloons, ah ok thanks :) ... is this the best way of doing things in the future for 'drive-by' or non-team folks?
[15:16] <balloons> ahayzen, if you approve the mp it should kick off jenkins, but I understand why that's annoying
[15:17] <balloons> in this case I think drizzle is going to be doing more than just this contribution, so it makes sense
[15:17] <ahayzen> yeah :/ sometimes i wanna see if jenkins is happy before top approving
[15:18] <balloons> ahayzen, http://91.189.93.70:8080/job/music-app-ci/1282/ is running now
[15:18] <ahayzen> balloons, thanks :)
[15:19] <balloons> dholbach, so we want to make help an official core app n'est pas?
[15:19] <dholbach> yep
[15:29] <zsombi> t1mp: the tests/resources/styleset/Simple I used for testing, later it would be more visible what it does, yet it only prints out the theme it uses
[15:36] <ahoneybun> howdy
[15:37] <ahoneybun> ahayzen: I got it to work
[15:37] <ahayzen> ahoneybun, well done man :)
[15:45] <t1mp> zsombi: okay
[15:45] <ahoneybun> big thanks to you though ahayzen
[15:45] <ahayzen> ahoneybun, no problem :)
[15:45] <ahoneybun> I need to get the emulator to load
[15:46] <ahoneybun> ahayzen: I'm having a problem uploading the package though
[15:46] <ahoneybun> The uploaded package name (com.ubuntu.aaronhoneycutt.gazeteer) does not use your namespace (aaronhoneycutt)
[15:47] <ahayzen> ahoneybun, iirc the package names should be gazateer.aaronhoneycutt now?
[15:47] <t1mp> nik90: your MR landed in staging :)
[15:47] <ahoneybun> ahayzen: I'm on 14.10
[15:48] <ahayzen> ahoneybun, the stores policy has changed...let me see if i can find the docs
[15:48] <ahoneybun> oh darn
[15:48] <dholbach> balloons, sorry... please ignore the next mails about the help-app - I pushed changes to the wrong branches - let me go back and fix it :)
[15:48] <dholbach> I'll let you know when I'm done :)
[15:49] <ahayzen> ahoneybun, https://developer.ubuntu.com/en/publish/ ... "Be sure to pick a unique namespace for your submissions, such as <appname>.<username> – this is the only setting which can not be changed later on."
[15:50] <ahoneybun> that name worked
[15:50] <ahayzen> \o/
[15:51] <ahoneybun> now for someone to review it
[15:51] <ahoneybun> published
[15:52] <t1mp> kalikiana: I resubmitted https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/waitForHeaderAnimation/+merge/253843 with a prerequisite. Nothing changed besides that, but it will need a new approval from you
[15:52] <zsombi> t1mp: btw, those tests do test warnings, the test is failing if there are binding loops, remember?
[15:52] <dholbach> balloons, https://code.launchpad.net/~dholbach/help-app/1434415/+merge/253844 is good to go now
[15:55] <t1mp> zsombi: ok. But can you somehow also verify that setting or unsetting the theme was successful?
[15:56] <zsombi> t1mp: I can, but there are the other tests which do that AFAIR, so it would be a double test
[15:56] <t1mp> zsombi: if you think I am too strict in reviewing,  please take revenge here :) https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/headlock/+merge/253121
[15:56] <zsombi> t1mp: strictnes sis good, I have to convince you that your worries are not needed ;)
[15:57] <t1mp> oh wrong link, I meant here: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/headlock/+merge/253845
[15:57] <kalikiana> t1mp: ack
[15:58] <zsombi> t1mp: I'll take it
[15:58] <t1mp> zsombi: if those tests are there only to check for binding loops, make that obvious from the code. I'd say update the function names (maybe a comment that binding loops generate errors)
[15:58] <t1mp> zsombi: thanks
[15:58] <zsombi> t1mp: ok, will give more descriptive names or comments, whatever :)
[15:59] <t1mp> kalikiana: thanks
[16:01] <ahoneybun> ahayzen: https://appstore.bhdouglass.com/app/gazeteer.aaronhoneycutt
[16:01] <ahayzen> ahoneybun, yey .... version 0.2 already ;)
[16:01] <ahoneybun> had a problem
[16:01] <zsombi> t1mp: you're killing me with these copyright dates :D
[16:02] <t1mp> zsombi: I wonder now whether we really need to update them
[16:03] <t1mp> zsombi: if (C) 2012 means 2012 and after, then we don't need to update
[16:03] <zsombi> t1mp: why only now?
[16:03] <zsombi> t1mp: well, it used to mean...
[16:04] <kalikiana> t1mp: there is no implied "and after" in copyright law…
[16:05] <zsombi> t1mp: tst_theme_engine tests only the deprecated test... I can rename it to tst_deprecated_theme, however teh new one will have a different test module
[16:05] <zsombi> t1mp: it'll be called tst_subtheming, which includes the same tests but with the new context
[16:06] <t1mp> kalikiana: so we should update the year when we make changes to a source file?
[16:06] <kalikiana> t1mp: yes
[16:07] <t1mp> kalikiana: ok, I trust you :)
[16:07] <t1mp> zsombi: ^ there you have it ;)
[16:07] <t1mp> zsombi: better to rename it, so when we do a clean-up for 2.0 eventually we know which files are no longer needed
[16:07] <zsombi> t1mp: I have copyrigth laws
[16:07] <zsombi> yeah, will do
[16:08] <t1mp> zsombi: you have copyright laws? What does that mean?
[16:08] <zsombi> t1mp: I don;t have any laws, I'm not a liar :D
[16:13] <kalikiana> zsombi: but maybe a lier? http://img01.cp.aliimg.com/imgextra/i1/836620130/T22uVwXh0NXXXXXXXX_!!836620130.jpg
[16:14] <zsombi> kalikiana: me not a catman ;)
[16:25] <dee_> hi, is it normal that i have to debug my html 5 app (with a usb connected ubuntu phone) in the webbrowser? i get some errors in the application output http://pastebin.ubuntu.com/10661935/
[16:26] <zsombi> t1mp: pushed an update on the theming
[16:27] <t1mp> zsombi: thanks, I'll check it
[16:27] <t1mp> kalikiana: care for a small review? https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/removeToolbarExample/+merge/253851
[16:27] <t1mp> seb128: ^fyi, fixing your bug
[16:27] <seb128> t1mp, thanks ;-)
[16:29] <dee_> nobody who can help me?
[16:29] <dee_> ..
[16:30] <popey> alex-abreu: are you able to help dee_ ?
[16:30] <t1mp> zsombi: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/01-multiple-theme-engines/+merge/251942 looks good, approved.
[16:31] <zsombi> t1mp: thx!!!
[16:31] <t1mp> zsombi: this one will be 1.3, so no happroval yet.
[16:31] <zsombi> t1mp: yes.... though teh changes are not really something that are altering the 1.2 in any form...
[16:33] <t1mp> zsombi: true. But it is safer to start landing all these changes in w
[16:33] <t1mp> that will be easier to fix if something breaks :)
[16:33] <zsombi> t1mp: yep
[16:39] <zsombi> t1mp: ehh... this MR of your si really hard to review...
[16:40] <t1mp> zsombi: yes, I realized that
[16:40] <t1mp> zsombi: yours too ;)
[16:40] <zsombi> t1mp: :D
[16:40] <t1mp> zsombi: is there a way I can make it easier?
[16:40] <zsombi> t1mp: the only way is to chain them...
[16:41] <zsombi> t1mp: basically both prereqs are approved, so I'd say they'll be landing all at once
[16:41] <t1mp> zsombi: I did. Everything you see in the diff on launchpad is changed only for this MR
[16:41] <zsombi> t1mp: ahh... ok, I thought you have still the logs from one of the prereqs...
[16:42] <zsombi> t1mp: I though I saw already some part of the code :)
[16:42] <zsombi> t1mp: so seems you can also produce 1k+ lines MR ;)
[16:43] <t1mp> zsombi: yeah. A large part of that consists of new unit tests
[16:44] <zsombi> t1mp: same here :)
[16:44] <t1mp> zsombi: also there are now two PageHeadConfiguration versions, and I moved its docs into a separate file. That counts for a lot of lines too
[16:45] <zsombi> t1mp: so you expect the page tiotle being set to "" shoudl not longer hide the header?
[16:45] <t1mp> zsombi: the tst_header_visible.qml can be run with qmltestrunner, but also launched with ../../launcher/launcher :) the app has buttons to test out the functionality manually
[16:46] <t1mp> zsombi: yes, that's correct. But if you are using version <= 1.2, setting the title to "" will still hide it
[16:46] <zsombi> t1mp: make sure guys from this list will know this!!!
[16:46] <t1mp> zsombi: to hide it, use head.visible now. Empty string to hide is no good, see https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1402054
[16:47] <t1mp> zsombi: that change will be for 1.3. We can mail all the changes for that before we release it
[16:47] <zsombi> t1mp: few apps use that now, I feel transitioning to 1.3 would be painful a bit if you remove that functionality...
[16:47] <t1mp> zsombi: perhaps we should track what's changed in 1.3
[16:47] <zsombi> t1mp: good idea
[16:48] <t1mp> zsombi: it is an easy change to use the proper API for hiding the header. But yeah we have to tell people
[16:48] <zsombi> t1mp: perhaps a "What's new?" section should be prepared already in the docs
[16:48] <t1mp> setting the title to "" was always a workaround until the proper API is there
[16:48] <t1mp> zsombi: yes, good idea.
[16:49] <t1mp> zsombi: you want that in this MR?
[16:49] <zsombi> t1mp: I am affraid people will hate us if we'll have lots of these "small" changes... they can easily pile up to a morman of changes...
[16:49] <zsombi> t1mp: I'd rather do in a separate one once we get the W open
[16:49] <t1mp> ok
[16:49] <zsombi> t1mp: till then we should have a doc where we log
[16:50] <zsombi> t1mp: in the API doc folder
[16:50] <t1mp> zsombi: we used to use the CHANGES file for that
[16:50] <zsombi> t1mp: we neve rhad tags for what's new...
[16:51] <zsombi> t1mp: but we can have a CHANGES-1.3 and we add everything we do for 1.3 so at the release time we can create a nice doc out of it
[16:51] <t1mp> zsombi: * ADDED IN: Action: property string iconName
[16:51] <t1mp> zsombi: we never had that in CHANGES.syntax, but we used it
[16:51] <zsombi> t1mp: but nothing like NEW\
[16:51] <dholbach> balloons, https://code.launchpad.net/~dholbach/help-app/1434125/+merge/253658 might be ready now too
[16:51] <zsombi> t1mp: how woudl we add theming? ADDED ID: plugin?
[16:51] <t1mp> zsombi: I had this suggestion a while ago https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/no-NEWS-no-CHANGES/+merge/251579
[16:52] <dholbach> balloons, I'll appreciate your testing on both on pad.lv/mps/help-app :)
[16:52] <zsombi> t1mp: right... those both are pretty outdated, and we've lost track of them. We've added a section to the docs, and that should be one to track things, teh audience is bigger than for those two files tbh
[16:53] <zsombi> t1mp: and at the 1.3 release, we can just blog about it
[16:53] <t1mp> zsombi: your suggestion is good to track it in a doc
[16:53] <t1mp> zsombi: and then when we release we simply copy&paste that into a blog post
[16:53] <zsombi> t1mp: +1
[16:53] <t1mp> and send the link to the blog post to the mailing lists
[16:54] <zsombi> t1mp: and to G+, right
[16:54] <t1mp> and to slashdot.org ;)
[16:54] <ogra_> hey SDK guys ... i'm trying to set applicationName from a variable ... but that shows weird behavior of Qt ...
[16:54] <ogra_> http://paste.ubuntu.com/10662121/
[16:55] <t1mp> ogra_: appName does not exist in your .js file. You called it  webappName
[16:55] <ogra_> any idea what to file a bug against ? i asked ricmm, he says it isnt QML cache related ... pointing me to ted ... who then pointed to SDK
[16:56] <ogra_> t1mp, yeah, thats just a typo when transferring into the pastebin ...
[16:56] <ogra_> assume it says appName there :)
[16:56] <t1mp> the log is indeed not very descriptive.
[16:56] <ogra_> (it wouldnt start at all indeed)
[16:57] <ogra_> here it starts but without using any cached data
[16:58] <ogra_> i actually want to write a generic framework, so all app specific bits should live in config.js ... i.e. so that app devs can bzr pull the upstream source without havin to fiddle with anything but the config file
[16:58] <ogra_> but that restriction kind of gets in my way :)
[16:58] <t1mp> ogra_: hmm, changing the applicationName will change the data folder of the app.. There may be a potential security risk there
[16:59] <t1mp> kalikiana: perhaps you know more about this?
[16:59] <ogra_> it indeed works fine if i just hardcode the value for applicationName in Main.qml
[16:59]  * kalikiana reading
[16:59] <ogra_> t1mp, i think it is rather a matter of processin the import earlier so the value for applicationName is set before it tries to do anything with it
[17:03] <kalikiana> ogra_: is foo-bar.ogra the correct app name here? does it work if you put it in applicationName directly?
[17:03] <ogra_> thats only an example indeed
[17:03] <ogra_> the app name is google-plus.ogra ... and it works fine if i put it into Main.qml directly, yes
[17:08] <kalikiana> ogra_: did you check if any files are written? maybe the name is evaluated more than once
[17:08] <kalikiana> I've seen that happen using Qt.resolvedUrl
[17:09] <ogra_> no, there are no files written at all and i get apparmor denials for the file accesses you se in the log in pastebin
[17:09] <ogra_> it liiks like something in Qt tries to make use of the applicationName before it has any value
[17:09] <ogra_> *looks like
[17:12] <dee_> back ... there was someone who did answer to my question?
[17:13] <ogra_> it actually seems to replace the applicationName with "QtProject"
[17:15] <xhoch3> when building an app for Ubuntu Touch I just get error code 1 by qmake
[17:15] <xhoch3> I have to leave the office in 5 minutes
[17:16] <xhoch3> so building QML only apps works just fine, if I build any of the examples that contain c++ code it fails
[17:17] <dee_> mhhh develope a ubuntu phone app isent so easy at last ... i dont like that docu and that there are no example codes ...
[17:17] <xhoch3> So, new project, then on Applications (not Ubuntu, because I want to write apps that run on all platforms and I need qmake)
[17:17] <xhoch3> then Qt Quick application
[17:18] <dobey> xhoch3: to use qmake for c++ apps you need to target the 15.04 framework
[17:18] <xhoch3> ok, I am on 14.10
[17:18] <dobey> xhoch3: qmake cross compiling wasn't supported on 14.10 framework
[17:18] <xhoch3> ah that would explain a lot
[17:18] <kalikiana> dee_: what are you looking for?
[17:18] <xhoch3> but good to hear this will work
[17:19] <xhoch3> dobey, thank you first, I will upgrade my machine to 15.04 and then we'll see =)
[17:20] <dobey> xhoch3: it's not your machien that's the issue
[17:20] <xhoch3> ok, but in order to get the 15.04 framework I need it, or not?
[17:20] <dobey> xhoch3: in the sdk, you need to create a kit for the 15.04 target, and build your app in that. you will also need to specify the 15.04 framework version in the manifest.json file for the click packge
[17:20] <dee_> kalikiana i wana save a file on the phone, but cant find any api call for that
[17:21] <dee_> html 5 btw
[17:21] <dobey> xhoch3: no, click packages are built inside a chroot. you just need to create the one for the 15.04 framework target
[17:21] <xhoch3> dobey, I cannot select 15.04 in Ubuntu SDK
[17:21] <xhoch3> ie in the QtCreator
[17:22] <xhoch3> the highest I can select is 14.10
[17:22] <xhoch3> ok, I have to go now, I will contact you later, dobey
[17:22] <dee_> xhoch3
[17:22] <xhoch3> do you know when you will be available?
[17:23] <dee_> u can add something in "tools -> options -> ubuntu"
[17:23] <xhoch3> yes, create click target
[17:23] <xhoch3> but it doesn't offer me 15.04 :)
[17:24] <xhoch3> bb, dee_ thx =)
[17:24] <dobey> eh, it does here
[17:24] <dee_> kalikiana, i found that: https://developer.ubuntu.com/api/html5/current/
[17:25] <kalikiana> dee_: hmm I know just a little about html truth be told, there's the tutorial https://developer.ubuntu.com/en/apps/html-5/guides/introduction-to-the-html5-ui-toolkit/ which you might have already seen
[17:26] <dee_> thats all about the UI, i wana start with the logic, if i dont get that to work, i dont need to start the gui ...
[17:28] <kalikiana> dee_: if you want to open files like pictures, dcuments etc there's content hub https://developer.ubuntu.com/api/html5/sdk-14.10/ContentHub/
[17:29] <kalikiana> dee_: if you see a dialog letting you pick a file that's how that's implemented in apps
[17:30] <daker> nik90: anyidea how to solve this ?http://paste.ubuntu.com/10662385/
[17:30] <dee_> kalikiana, no i need to save and load a config file, with my own format
[17:34] <nik90> daker: its got to do with the GPG keyring..since that command works on my comp
[17:35] <nik90> daker: I cant tell why it is unable to retrieve it from the keyserver
[17:35] <daker> nik90: ok i think i found the problem
[17:38] <daker> nik90: i just added --keyserver hkp://p80.pool.sks-keyservers.net:80 to force port 80
[17:38] <nik90> daker: ah ok. does it work now?
[17:38] <daker> nik90: yes it's downloading the rootfs
[17:39] <nik90> ll
[17:39] <nik90> cool
[17:41] <dee_> someone a idea to save and load a config file in a html5 app?
[17:44] <dobey> dee_: if it's html5, wouldn't you just use html5 storage for that?
[17:53] <dee_> dobey ok thats work .... sry ^^
[17:53] <dee_> but i have to test a restart from the phone
[17:54] <dee_> there comes the next question ... how can i install my app c
[17:54] <dee_> ?
[17:54] <nik90> dee_: do you build a click package?
[17:54] <nik90> s/a/the
[17:56] <dee_> did start a "html5 app"
[17:56] <dee_> and test it on my bq ubuntu phone live
[17:56] <dee_> with the debug method
[17:57] <nik90> dee_: if you are using QtC, there should be tools->ubuntu->install application on device
[17:58] <nik90> I don't have experience with html5 apps, so not sure what IDE developers usually use for development
[17:58] <dee_> y found it, thx
[18:06] <dee_> dobey, its work perfect the data is still after a restart avarible
[18:06] <dobey> nik90: the ubuntu sdk is the documented/supported method of creating apps in html5 for the phone
[18:06] <dee_> nice i can start my bitcoin wallet app :)))
[18:19] <daker> nik90: faced this before http://paste.ubuntu.com/10662821/ ?
[18:35] <nik90> daker: hmm not really
[19:24] <wallermadev> hey
[19:25] <wallermadev> having a bit of trouble deploying an application to ubuntu device..
[19:41] <imnichol> I'm setting up a new project, and I'm getting prompted to "select a path to the cmake executable".  Did I do something wrong?
[19:41] <imnichol> I'm testing vivid at the moment.
[19:47] <imnichol> I was able to get around it by creating a project with qmake
[19:49] <nik90> imnichol: I am pretty sure you don't have the package "cmake" installed :)
[19:49] <nik90> imnichol: I had this issue on a fresh ubuntu install
[19:50] <imnichol> nik90, Yeah I kinda figured.  I wasn't sure which one to choose so I flipped a coin and apparently chose the wrong one to begin with
[19:50] <nik90> bzoltan_: ^^ may be "cmake" should be a dependency of the ubuntu-sdk
[19:53] <imnichol> While I'm here: it seems like I don't remember where to get documentation for using plugins with qml
[19:54] <imnichol> I want the user to enter a URL and then hit "go" and get the raw content back from the server
[19:55] <imnichol> My google-fu seems to have failed me, is there a tutorial?
[20:28] <imnichol> Is there a broken image link in https://design.ubuntu.com/apps/getting-started/ui-model for anyone else?
[20:36] <popey> imnichol: yeah, looking into it
[20:41] <popey> imnichol: fired a mail at the person responsible.
[20:41] <imnichol> Is it possible to add a C++ plugin to an existing simple QML project?  Or do I need to start over again?
[20:42] <imnichol> popey, is there a project that I can just file a bug on?
[20:42] <imnichol> (to report issues with d.u.c)
[20:44] <popey> for the C++ plugin option, I don't know, bzoltan_ will.
[20:44] <popey> for the d.u.c, do you mean design.u.c or developer.u.c ?
[20:44] <imnichol> developer.u.c
[20:44] <imnichol> Or, either I guess
[20:44] <popey> well, the answer is different
[20:44] <dobey> it is possible, but it's not trivial to do, for an exissting project
[20:44] <popey> developer.u.c is linked at the bottom
[20:45] <dobey> since the simple qml project doesn't use cmake
[20:45] <popey> "Report a bug on this site"
[20:45] <imnichol> popey, I'm running Chrome on 15.04 and I don't see any links to report bugs
[20:46] <renatu> popey, hi. Who is working on calendar app?
[20:46] <imnichol> But I can figure it out thanks to the link to it's launchpad site
[20:46] <imnichol> dobey, how untrivial is it?
[20:46] <popey> renatu: kunal mainly.
[20:46] <renatu> popey, ok nice thanks
[20:46] <renatu> popey, what is his tz?
[20:46] <imnichol> I have maybe 50 lines of QML, so if it's possible I could just throw it into a new project too.  I wouldn't know where to stick it though
[20:46] <popey> imnichol: in fact both sites have that link at the bottom
[20:47] <popey> renatu: South Korea
[20:47] <renatu> :(
[20:47] <popey> imnichol: and I'm using chrome too
[20:47] <popey> wassup?
[20:49] <dobey> imnichol: it involves adding a build system to the project that doesn't exist in it
[20:49] <dobey> the c++ project template is a fair bit different than the simple qml one
[21:20] <mhall119> rickspencer3: do you know who managed dc.ubuntu-us.org ?
[21:20] <rickspencer3> mhall119, wow, no idea
[21:20] <rickspencer3> Kevin Cole, maybe?
[21:22] <mhall119> ok, thanks
[21:43] <imnichol> popey, ahah you're right, I misinterpreted what you were saying
[21:51] <nik90> Elleo: hey, I am curious as to how many people have downloaded podbird. I see 3 new bug reports from a new reporter ;)
[21:52] <nik90> Elleo: Any spike after the recent BQ phone sales?
[23:03] <daker> nik90: managed to fixed lxc just by restarting :)
[23:04] <daker> fixe*
[23:16] <nik90> daker: so are you able to get it started?
[23:17] <nik90> daker: I don't remember if I restarted or not .. if not I would have mentioned that in my blog post
[23:17] <daker> nik90: it did start, and managed to attach the shell
[23:18] <nik90> daker: cool. Now you just need to create the appropriate .desktop files for the gui apps you want to open using your lxc like Qtcreator and a terminal app where you can build stuff
[23:19] <daker> nik90: the only issue is that when apt-get ubuntu sdk it needs to grab a lot of packages
[23:19] <daker> http://paste.ubuntu.com/10664713/
[23:20] <nik90> daker: yup, there is no work around for that since the lxc container we downloaded was minimal
[23:20] <nik90> daker: it is similar to installing the sdk on xubuntu or ubuntu mate for instance
[23:20] <daker> ok
[23:23] <ahoneybun> 300 users!