[11:23] <Cimi> tsdgeos, hey dude
[11:24] <Cimi> tsdgeos, we remove the qmlproject, but now with cmake I think it's just less handy to deal with the qml files
[11:26] <mzanetti> Cimi: what's the problem?
[11:27] <Cimi> mzanetti, loses all the integration and highlight with ubuntu components, here
[11:27] <mzanetti> oh really?
[11:27] <mzanetti> hmm
[11:27] <Cimi> mzanetti, might be false
[11:27] <mzanetti> Cimi: can you point me to an example?
[11:28] <Cimi> mzanetti, while I was texting you
[11:28] <Cimi> mzanetti, I realised I should double check I have them installed
[11:28] <Cimi> might be that apt uninstalled them
[11:28] <mzanetti> Cimi: if it doesn't work, let me know
[11:28]  * Cimi upgrades
[11:41]  * mzanetti is reading the design spec for the tablet right edge
[11:41] <mzanetti> as a user: \o/
[11:41] <mzanetti> as a developer: /o\
[11:41] <tsdgeos> hehe
[12:11] <Cimi> ahah
[12:40] <Cimi> mzanetti, yeah I don't have highlight anymore after this qmlproject -> cmake
[12:40] <mzanetti> Cimi: what doesn't highlight?
[12:40] <mzanetti> Cimi: everything or just some stuff?
[12:41] <Cimi> mzanetti, the components
[12:41] <Cimi> Label, UbuntuShape...
[12:41] <mzanetti> SDK?
[12:41] <Cimi> yes
[12:42] <Cimi> mzanetti, thus I don't have auto completion on properties too
[12:42] <mzanetti> Cimi: hmm... works here
[12:43] <Cimi> mzanetti, you have highlight of Label?
[12:43]  * mzanetti tries
[12:43] <Cimi> Button
[12:44] <mzanetti> Cimi: http://i.imgur.com/2P9YKgl.png
[12:44] <Cimi> mzanetti, with cake??
[12:44] <Cimi> cmake?
[12:44] <mzanetti> Cimi: yeah
[12:44] <Cimi> mzanetti, how did you open the file?
[12:45] <Cimi> you open cake, then it asks to build here
[12:45] <mzanetti> Cimi: opened the cmakelists.txt as project
[12:45] <Cimi> cake is my cmake
[12:45] <Cimi> I have autocorrection
[12:45] <mzanetti> then ctrl + k -> She -> enter
[12:45] <Cimi> for the recotds
[12:45] <mzanetti> doesn look like ^ :P
[12:45] <Cimi> indeed
[12:45] <Cimi> hah
[12:48] <Cimi> mzanetti, build location of project doesn't affect?
[12:48] <mzanetti> Cimi: no, it shouldn't... however, I always change that to unity8/builddir
[12:48] <mzanetti> (where unity8 is the folder of the current branch)
[12:49] <mzanetti> Cimi: that way ./run and qtcreator share the same builddir
[12:53]  * Cimi tried
[12:53] <Cimi> *s
[12:53] <Cimi> first I'll build with our tool, then I import
[12:53] <Cimi> let's see
[13:01] <mzanetti> Cimi: now I have the same issue
[13:01] <mzanetti> Cimi: not sure what I did tho
[13:06] <mhr3_> mzanetti, holy ..., what display are you using?
[13:06] <mhr3_> frickin huge screenshot
[13:06] <mzanetti> mhr3_: 2880x1900
[13:06] <mzanetti> on 15"
[13:07] <mhr3_> 15"? whaaaat?
[13:07] <mzanetti> they call it Retina screen
[13:08] <mhr3_> you can like... see something there?
[13:08] <mzanetti> mhr3_: sure... using 200 dpi fonts
[13:08] <mzanetti> and "huge" icons everywhere
[13:08] <mzanetti> some issues here and there
[13:09] <mzanetti> but KDE does okayish
[13:09] <mzanetti> not so much unity7
[13:09] <mzanetti> unit8 is perfect
[13:09] <mhr3_> i'd like to see you try to hit the search prev and next icons
[13:10] <mzanetti> yeah... unity7 doesn't really work on this screen
[13:10] <mzanetti> for unity8 I use GRID_UNIT_PX=18
[13:52] <Cimi> mzanetti, now every highlight is broken :|
[13:52] <mzanetti> Cimi: yeah... same here. I don't know what made it work before...
[13:53] <mzanetti> Cimi: just tried with some core apps
[13:53] <mzanetti> Cimi: same issue there
[13:53] <Cimi> let's google
[13:57] <Cimi> nah
[14:05] <Cimi> mzanetti, missing plugins.qmltypes?
[14:05] <Cimi> mzanetti, from ubuntu components
[14:05] <mzanetti> Cimi: no, I don't think so
[14:05] <mzanetti> Cimi: plugins.qmltypes is only there to resolve compiled stuff
[14:05] <Cimi> ok
[14:06] <mzanetti> Cimi: everything written in QML should appear without it
[14:06] <mzanetti> Cimi: http://i.imgur.com/nc59df0.png
[14:06] <mzanetti> Cimi: so the issue is that qtcreator knows only qmake and qmlproject to set this import path
[14:07] <mzanetti> Cimi: which means, right now there is no chance to load our internal plugins located in the builddir
[14:07] <Cimi> so why we used cmake?
[14:07] <mzanetti> Cimi: however, for stuff that is installed system wide (e.g. Ubuntu .Components) it should load it automatically
[14:07] <Cimi> if it doesn't fully work with our sdk?
[14:07] <Cimi> ah I see
[14:08] <mzanetti> Cimi: yeah... we definitely need to report a bug about this. If the company guideline is to use cmake, we need to fix the qtcreator cmake integration
[14:08] <mzanetti> but it did load Ubuntu.Components for me
[14:08] <mzanetti> but then I closed everything and reopened it and now its gone
[14:09] <Cimi> :P
[14:09] <mzanetti> I'll report a bug
[14:20] <mzanetti> Cimi: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1271184 and https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1271185
[14:24] <karni> Why is it that I have to kill mumble twice before it connects property the third time hah
[14:32] <Cimi> karni, but in ubuntu, works on osx
[14:33] <Cimi> ubuntu/linux
[14:33] <karni> heh ;)
[14:37] <Cimi> I meant bug
[14:38] <karni> Right
[14:40] <mzanetti> Cimi: can you confirm the bugs?
[14:48] <kgunn> didrocks: moving here :)....but just wanted to ask
[14:48] <kgunn> can the autopilot test for attempting to join a wifi
[14:49] <kgunn> actually fail ? (meaning we won't know the passwords when the test may be run anywhere)
[14:49] <kgunn> and the point is really to prove the unity8-mir stack...correct ?
[14:50] <didrocks> kgunn: not sure if you can have a mock, the goal is to ensure that I see a wifi access point, click on the shell indicator, and get a WPA/WEP passphrase prompt where I can ack it
[14:51] <didrocks> (which was what failing, due to the stacking issue)
[14:51] <kgunn> Cimi: ^ as we were just discussing
[14:51] <Cimi> didrocks, we can maybe create an access point
[14:51] <Cimi> local one
[14:51] <Cimi> but it's rather not-easy
[14:51] <kgunn> didrocks: i apologize, i'm catching up...what specificaly was failing ? osk reveal ?
[14:52] <didrocks> kgunn: no WPA snap decision prompt
[14:53] <didrocks> so basically, clean phone
[14:53] <didrocks> click on an access point
[14:53] <didrocks> then, nothing
[14:53] <didrocks> there were also stacking issues which were mentionned on the ubuntu-phone ML
[14:53] <kgunn> got it...and this was only with nested mir ?
[14:53]  * kgunn finds that a little hard to believe
[14:54] <didrocks> kgunn: it was
[14:54] <didrocks> kgunn: 3 people confirming
[14:54] <didrocks> we only reverted ubuntu-touch-session to disable it
[14:55] <didrocks> kgunn: just read my emails on the phone ML, everything and what we tested/reverted is detailed there
[15:16] <Cimi> Wellark, hey dude, have you done any autopilot tests for network?
[15:17] <mzanetti> MacSlow: can this land? https://code.launchpad.net/~macslow/unity-notifications/extended-snap-decisions-part2/+merge/188851
[15:19] <MacSlow> mzanetti, as is hardly... it's been idling for months because that special use-case was no longer needed by use-cases from Design
[15:19] <mzanetti> ok...
[15:19] <mzanetti> so seems we don't have anything to land just now
[15:19] <MacSlow> mzanetti, much wasted time :/
[16:18] <tsdgeos> meh
[16:18] <tsdgeos> we have non square icons that don't make QIcon happy and thus we end up with blurry icons :-(
[16:19] <mhr3_> tsdgeos, you sure it isn't a problem with the theme itself?
[16:20] <mhr3_> last time i checked it didn't specify scalable icons for everything
[16:20] <tsdgeos> mhr3_: the problem is we are installing a 144x135 png in a 144 folder
[16:20] <tsdgeos> and the spec is made only for square icons
[16:21] <mhr3_> can't we just add some margins?
[16:21] <tsdgeos> so the loader things that if it's inside a 144 folder it means it's 144x144 and then bad things happen when you ask for a 144x135 one
[16:21] <tsdgeos> we could, but that would probably break something else :D
[16:22] <mhr3_> sigh
[16:22] <tsdgeos> that would not be epecting the margins
[16:23] <mhr3_> tsdgeos, well, it does work for square icons on the desktop
[16:24] <tsdgeos> mhr3_: i guess if we add margins, then you'd get margins on the rendering too, no?
[16:24] <tsdgeos> that's surely not what we want i guess
[16:26] <mhr3_> unless the shader just centers the current icons anyway
[16:28]  * tsdgeos adds some more debug code and finds weirder stuff
[16:30] <Wellark> Cimi: ?
[16:30] <Wellark> haven't got that far
[16:30] <Wellark> I'm finishing the project I'm currently working this week and then it's all-in for networking
[16:49] <cwayne> thostr_1, ping
[16:50] <thostr_1> cwayne: pong
[16:50] <cwayne> thostr_1, hi, i was wondering if you guys had any status on the scopes-registry being able to query remote scopes?
[16:52] <tsdgeos> boo, i think i found a bug in Qt (another one) :D
[16:53] <thostr_1> cwayne:marcus is still working to get remote scopes fully working
[16:53] <tsdgeos> can anyone see why this would happen?
[16:53] <tsdgeos> http://paste.ubuntu.com/6792543/
[16:53] <thostr_1> cwayne: he estimated to have it done by end of this week
[16:53] <tsdgeos> mzanetti: ↑↑
[16:53] <cwayne> thostr_1, done as in having a MR to trunk, or done as in having it in a package in the ppa?
[16:54] <thostr_1> cwayne: first one, second is often out of our hands unfortunately
[16:54] <thostr_1> cwayne: we're trying but I cannot promise this
[16:55] <cwayne> thostr_1, who controls the ppa releasing bits?
[16:55] <mzanetti> tsdgeos: seems to preserve the aspect ratio
[16:55] <mzanetti> PreserveAspectFit
[16:55] <tsdgeos> mzanetti: sure, but look at the last one
[16:56] <tsdgeos> why do i get QPixmap(QSize(105, 99) ) instead of QPixmap(QSize(144, 135) ) as i did get?
[16:56] <mzanetti> hmm... interesting
[16:56] <mzanetti> seems to actually scale down the QImage
[16:57] <mzanetti> QIcon
[16:57] <tsdgeos> i'd say the cachine code is confused
[16:57] <tsdgeos> and returning me the last pixmap for no real reason
[17:06] <tsdgeos> oh lol
[17:06] <tsdgeos> huge bug in the qiconloader code
[17:06] <tsdgeos> i'll fix it tomorrow
[17:06] <tsdgeos> wonder how noone found this yet :-S
[17:07] <tsdgeos> it does indeed scale the pixmap down
[17:11]  * tsdgeos waves
[19:24] <myNameIsWho> Hello there I was wondering if I could get some help on debugging Unity.  I have ran unity --debug and it shows that "unity-panel-service: no process found"   the shell does not show up at all neither does the launcher,dash nor panel.  Thanks for your time.
[19:26] <myNameIsWho> I am taking it that it is a glib service that is not found.  I am going to look into that.  I also see where some non-useful gdb and compiz messages.
[19:34] <myNameIsWho> Ok nevermind I was able to get unity going again after removing ~/.config/compiz-1 and dconf reset -f /org/compiz/