[01:58] <DF__> some one here??
[11:28] <nik90> mhall119: It seems that the theme manager doesn't seem to work with Ubuntu.Components 1.2 without restarting the app. Are you seeing this issue on your end?
[12:04] <DF__> hi ho
[12:05] <akiva-thinkpad> DF__, ho ha
[12:06] <DF__> akiva-thinkpad, at least today some one is here
[12:11] <DanChapman> nik90: hey o/ have you ever had any luck getting the qml profiler to work when running on device. I've been pulling my hair out over it for a few hours now
[12:12] <DanChapman> ^^ or anyone else :)
[12:13] <akiva-thinkpad> DF__, It is sunday~
[12:14] <ahayzen> DanChapman, have you tried disabling the JIT cache by putting this in your /etc/environment and restarting? QV4_NO_JIT_CACHE=1
[12:15] <ahayzen> (on device that is)
[12:15] <DanChapman> ahayzen: I have not tried that! :-) lets see............
[12:32] <nik90> DanChapman, ahayzen: Yeah the qml profiler works for me without any additional arguments required
[12:33] <nik90> I haven't tried disabling the JIT cache yet
[12:34] <ahayzen> nik90, yours worked on device straight away?
[12:34] <nik90> ahayzen: assuming we both are referring to the qml profiler in qtc, then yes..it works on the device straight away
[12:35] <ahayzen> nik90, interesting, before when i last tried it you had to disable JIT to get it working, maybe something has changed in vivid
[12:35] <DanChapman> ahayzen: \o/ it worked thanks alot. Just out of curiosity is that env change actually documetned anywhere?
[12:35] <nik90> ahayzen: could be since I only tried this using the 15.04 chroot on devel-proposed images
[12:36] <ahayzen> DanChapman, erm i don't think it was on the web as me and Florian kept forgetting what it was so i eventually wrote it down lol
[12:37] <DanChapman> lol ok then. Best make a note of it myself then :-D
[12:38] <ahayzen> :)
[12:38] <ahayzen> nik90, you appear to be right with a 1504 chroot and vivid-proposed it appears to work
[12:39] <ahayzen> DanChapman, i assume your not on 15.04 then?
[12:40] <nik90> ahayzen: may be its the sdk dev elves at work ... (yes bzoltan I know u r reading this ;D )
[12:40] <ahayzen> nik90, hopefully it just sets it for you when you hit the button now :) (thats what it seems anyway)
[12:44] <DanChapman> ahayzen: no rtm r21 trying to get to get some benchmarks from krillin to solve some poor listview performance problems.
[12:44] <ahayzen> that makes sense then :)
[12:45]  * ahayzen is just porting music to the 'new' listitems \o/
[12:53] <nik90> ahayzen: so much code removal with the new listitems since all features are provided by the sdk itself..I ported podbird yesterday to the new listitems and is much better as a result in terms of the listview performance
[12:54] <ahayzen> nik90, yeah its looking pretty good so far...minimal changes lots of code removal :) haven't noticed much performance gain/loss yet but haven't really checked that part totally out
[12:57] <ahayzen> nik90, for the trailing actions do you get a white background when you drag too far?
[12:58] <ahayzen> ...and is there any way of changing that colour without putting a big box somewhere lol .. i want it to all be the same colour like the leading actions
[13:00] <nik90> ahayzen: yes I notice that..I changed the box color to green or red and still notice the white color when pulling it too much
[13:00] <ahayzen> :/
[13:00] <nik90> ahayzen: zsombi would be the best person to ask that ^^
[13:01]  * ahayzen senses a bug report
[13:01] <DF__> does some one know how to install org.qtproject.examples.calendar 1.0??
[13:01] <ahayzen> nik90, i also assume the leading actions would be the same just it happens i want them to be the red they are already set to :)
[13:01] <nik90> ahayzen: I think so...I only tested it for the trailing edge
[13:02] <nik90> ahayzen: but to be honest, it looks like the default behavior is to show only negative actions on the leading edge
[13:02] <ahayzen> yeah but i guess there should be a way of changing that 'background' colour to the overflow of the actions
[13:03] <nik90> ahayzen: may be its possible using Ubuntu.Styles for ListItemActions..although there isn't a stable API released for that
[13:04] <ahayzen> yeah that'll probably be the answer :)
[13:16] <DF__> guys can some one help me ??
[13:17] <DF__> i have a problem here, the compiler says that he doesnt recognize page
[13:23] <akiva-thinkpad> DF__, hmmmm? Do you have a screenshot?
[13:25] <DF__> i can send you the code if you want
[13:25] <akiva-thinkpad> DF__, sudo apt-get install shutter
[13:26] <akiva-thinkpad> you can use that program to export screenshots directly to imgur, and it gives you a link that is easy to share
[13:26] <DF__> http://pastebin.ubuntu.com/10977454/
[13:31] <akiva-thinkpad> DF__,
[13:31] <akiva-thinkpad> okay
[13:31] <akiva-thinkpad> do you know what a component is?
[13:32] <akiva-thinkpad> no pm's please
[13:32] <DF__> kind off
[13:32] <akiva-thinkpad> okay, here is a component
[13:32] <akiva-thinkpad> Item { }
[13:32] <akiva-thinkpad> Notice how it is capitalized
[13:32] <DF__> yea, i understand that
[13:32] <akiva-thinkpad> okay
[13:32] <DF__> yep
[13:32] <akiva-thinkpad> now do you know what a property is?
[13:32] <DF__> i have that with the page that i'm calling in main
[13:32] <akiva-thinkpad> Yes
[13:33] <akiva-thinkpad> you have many Components
[13:33] <akiva-thinkpad> Tab {} is a component
[13:33] <DF__> yes i see
[13:33] <akiva-thinkpad> so is Page{}, Rectangle{}, etc
[13:34] <akiva-thinkpad> now, do you know what a property is?
[13:34] <DF__> the thing is that yesterday befor i made changes to the code it worked well
[13:34] <DF__> kind off
[13:34] <akiva-thinkpad> okay
[13:34] <akiva-thinkpad> Does Rectangle {} have properties?
[13:35] <DF__> yes width
[13:35] <DF__> color etc.
[13:35] <akiva-thinkpad> yes
[13:35] <akiva-thinkpad> Does it have a property, "model:"?
[13:36] <akiva-thinkpad> or for that matter, a property, "bacon:"?
[13:36] <DF__> nope
[13:36] <akiva-thinkpad> How do you know, or how can you figure out, without using google?
[13:37] <DF__> i always use google to find those things
[13:37] <akiva-thinkpad> DF__, okay then I'll teach you a trick
[13:37] <akiva-thinkpad> create a Tab {} componenent, make a new line within that component
[13:38] <akiva-thinkpad> then hold <ctrl> and press <spacebar>
[13:38] <DF__> yes
[13:38] <DF__> and then
[13:38] <akiva-thinkpad> and then a box should appear
[13:38] <DF__> i know crtrl and spacebar thats what i use to make code faster
[13:39] <akiva-thinkpad> a menu with a list of valid properties is displayed
[13:40] <DF__> yes i see
[13:40] <akiva-thinkpad> DF__, http://i.imgur.com/3Dk0iej.png
[13:41] <akiva-thinkpad> I type "pag" for "page:", and nothing showed up
[13:41] <akiva-thinkpad> meaning that "page:" is not a valid property of "Tab {}"
[13:42] <akiva-thinkpad> which puts this error into context
[13:42] <akiva-thinkpad> file:///home/akiva/Programming/_tmp/QML_App_with_Simple_UI_qmlproject/Main.qml:19 Cannot assign to non-existent property "page"
[13:42] <akiva-thinkpad> "Cannot assign to -----Non-existent-property------ "page"
[13:42] <DF__> thats strange, i must have done something so that he could not find it
[13:43] <DF__> yesterday it workd very well
[13:43] <akiva-thinkpad> DF__, are you sure that the Tab {} component has that property?
[13:44] <akiva-thinkpad> DF__, mmmm I see...
[13:44] <DF__> see http://imgur.com/zuatFsy
[13:45] <DF__> that was yesterday
[13:46] <akiva-thinkpad> DF__, hmmm you may have found a bug...
[13:47] <DF__> yep
[13:47] <DF__> i jujst wanted the tabs to work that way and then i had this error
[13:50] <akiva-thinkpad> DF__, http://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Tabs/
[13:50] <akiva-thinkpad> try the example
[13:50] <akiva-thinkpad> it works
[13:50] <akiva-thinkpad> you must of did something
[13:54] <DF__> yep i was looking that right now
[13:54] <akiva-thinkpad> good luck
[13:54] <DF__> ty
[13:54] <DF__> btw do you know how to implement a calendar??
[13:55] <akiva-thinkpad> DF__, bzr branch lp:ubuntu-calendar-app
[13:55] <akiva-thinkpad> ;)
[13:57] <DF__> ty akiva :)
[13:58] <akiva-thinkpad> DF__, np good luck!
[13:58] <akiva-thinkpad> :)
[14:46] <bzoltan> nik90:  Of course I do read it :)
[14:55] <ahayzen> bzoltan, are you aware of the issue/behaviour we described?
[14:55] <bzoltan> ahayzen:  I have not read yet back all the lines... would you please brief me in few words?
[14:56] <ahayzen> bzoltan, when you have trailing actions, if you pull them 'further' you get a white background behind that i have not found a way of changing the colour of
[14:59] <bzoltan> ahayzen: I see. No I have not heard about it. It sounds like something what zsombi will be interested to hear about
[14:59] <ahayzen> :)
[15:00] <ahayzen> bzoltan, is it best to report a bug with a mini app example?
[15:16] <bzoltan> ahayzen:  that would helpt the case fore sure
[15:17] <ahayzen> cool i'll do that then :)
[15:38] <bzoltan> ahayzen:  thank you
[17:15] <ahayzen> Hi, anyone tried running autopilot with the 1.2 sdk components...seems the MainView helper assumes useDeprecatedToolbar still exists as a property?
[17:16] <bzoltan> ahayzen:  of course we run autopilot tests on the 1.2 components. Several per week.
[17:16] <ahayzen> bzoltan, do you have an example that uses MainView ? mine explodes
[17:16] <ahayzen> unless i add... property bool useDeprecatedToolbar: false  :)
[17:20] <ahayzen> bzoltan, this is the line it hits http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_mainview.py#L130
[17:21] <bzoltan> ahayzen:  the simple application template from teh QtC?
[17:22] <ahayzen> no when i've ported music-app to Components 1.2 and then trying to get autopilot to run
[17:22] <ahayzen> as you then have MainView12
[17:22] <ahayzen> but it seems the helper still has stuff that refers to useDeprecatedToolbar .. unless there is some other helper for MainView12 that I should be using?
[17:54] <spammer31> don't check this is a spam :p http://pastebin.ubuntu.com/10980019/
[17:57] <newsages> hi
[18:18] <newsages> I can get focus of TextField,, how?
[19:21] <t1mp> ahayzen: the same autopilot helper should work for mainview 1.2
[19:21] <t1mp> ahayzen: which errors are you getting?
[19:22] <ahayzen> useDeprecatedToolbar is undefined
[19:22] <ahayzen> or something along those lines
[19:23] <ahayzen> t1mp, AttributeError: Class 'MainView' has no attribute 'useDeprecatedToolbar'.
[19:23] <ahayzen> t1mp, but i'm not sure if my way of getting the MainView was correct
[19:24] <t1mp> ahayzen: it sounds like a bug in the mainview helper
[19:24] <ahayzen> t1mp, i had to put return false in the validate_dbus_object http://bazaar.launchpad.net/~ahayzen/music-app/refactor-bump-framework-1504/view/head:/tests/autopilot/music_app/__init__.py#L436
[19:24] <t1mp> some of the tests for the mainview helper still import uitk 1.0.. because we don't want to break that
[19:25] <ahayzen> otherwise you get ... ValueError: More than one custom proxy class matches this object: Matching classes are: <class 'music_app.MainView12'>,<class 'ubuntuuitoolkit._custom_proxy_objects._mainview.MainView'>.
[19:25] <ahayzen> t1mp, yeah looking at the actual helper, http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/tests/autopilot/ubuntuuitoolkit/_custom_proxy_objects/_mainview.py#L130, you can see it detecting MainView12 at the top but still using useDeprecatedToolbar further down
[19:25] <ahayzen> t1mp, shall i report a bug?
[19:26] <t1mp> ahayzen: yes, please
[19:26] <t1mp> ahayzen: about the validate_dbus_object function I don't think that returning false is the right approach, since then it will not use your class
[19:27] <t1mp> ahayzen: if you can catch elopio on irc tomorrow he probably knows best how to deal with this
[19:27] <t1mp> ahayzen: I can try to help you too, but on Monday and Tuesday I will be away for most of the time
[19:27] <ahayzen> t1mp, yeah i'm not sure what i should do though lol ? everything i did either ended up with it saying it didn't exist or there were two
[19:28] <t1mp> ahayzen: maybe it will work if you just rename the MainView12 in your AP helper to MyMainView or something similar?
[19:29] <ahayzen> t1mp, also if you are still working on the new headers (when they were in the image) i noticed that with a dark theme the divider is dark, should it not be light or calculated like the text colour? https://drive.google.com/file/d/0B3XynHVKfrvMVE51dlRFWXdjMlU/edit
[19:29] <ahayzen> i'll try that..
[19:30] <ahayzen> oh but that won't work as it won't be able to find the type
[19:30] <t1mp> ahayzen: do you use the type to select a qml object?
[19:30] <t1mp> ahayzen: don't do that. Better to always select by objectName
[19:30] <ahayzen> i use both
[19:31] <t1mp> selecting by type gives us a lot of issues like this
[19:31] <ahayzen> eg self.app.wait_select_single(MainView12, objectName="music")
[19:32] <t1mp> ahayzen: in the UITK tests I changed the code everywhere to use only objectName. Using type is tricky because the type names we can get from qml are not versioned, and don't have namespaces, and probably some other issues that I forgot again
[19:33] <t1mp> ahayzen: I would have something like select_single(objectName='MusicAppMainView') instead
[19:33] <ahayzen> ie bug 1341671 ;) but i have a workaround for that
[19:34] <t1mp> ahayzen: ah yes, like that bug
[19:35] <ahayzen> but then by just specifying the objectName how does it use your helper?
[19:35] <ahayzen> ...but then my hack wasn't earlier anyway :/ ugh
[19:38] <ahayzen> t1mp, reported bug 1451243 for you :)
[19:39] <t1mp> ahayzen: I cannot find the code right now for the CustomEmulatorBase in autopilot to see what validate_dbus_object does.. but I hope that contains some code to match the helper in this case...
[19:40]  * t1mp gotta go nwo
[19:40] <t1mp> ahayzen: thanks for reporting the bug.
[19:40] <ahayzen> no problem o/
[19:41] <t1mp> I assigned myself, and then unassigned because I won't be available for 2 days and someone else may like to take the bug in the meantime
[19:41] <ahayzen> cool