[07:17] <sil2100> mmrazik: hi! I see there are some problems merging https://code.launchpad.net/~veebers/unity/update-tests-for-autopilot-1.3/+merge/162176
[07:17] <mmrazik> sil2100: I know. was just talking with thomi.
[07:18] <mmrazik> sil2100: trying to build on a different panda ATM
[07:19] <sil2100> mmrazik: geh, MultipleShotsRun again... I would really like to get rid of those time-measuring unit tests finally
[07:19] <sil2100> mmrazik: thanks!
[07:41] <tsdgeos> mmrazik: any idea why http://10.97.2.10:8080/job/unity-phablet-qmluitests/807/console failed?
[07:43] <mmrazik> tsdgeos: not quite sure. I would say somebody added the ppa to the VM but not the key. There is a commented out apt-add-repository (this one was adding the key)
[07:43] <mmrazik> tsdgeos: I've added --force-yes
[07:43] <mmrazik> should work now
[07:43] <tsdgeos> thanks
[07:43] <mmrazik> mzanetti: ^^^
[07:43] <mmrazik> mzanetti: any idea ?
[07:44] <tsdgeos> he's on holiday afaik
[07:54] <Saviq> tsdgeos, quick look at result highlighting, couldn't we use color: "#80ffffff" and only wrap the highlights in <font />?
[07:55] <tsdgeos> hmmmm
[07:57] <tsdgeos> can give it a try
[07:57] <tsdgeos> sounds weird to me
[07:57] <tsdgeos> but might work
[07:58] <tsdgeos> seems to work
[08:03] <tsdgeos> whatte
[08:03] <tsdgeos> Cannot mix incompatible Qt library (version 0x50001) with this library (version 0x50002)
[08:03] <tsdgeos> mmrazik: ↑↑ http://10.97.2.10:8080/job/unity-phablet-qmluitests/810/console
[08:04] <mmrazik> tsdgeos: mhm... I guess there is something broken on the VM
[08:04] <mmrazik> let me check
[08:10] <mmrazik> tsdgeos: I actually start to wonder if it is not a bug in qmlscene packaging
[08:11] <mmrazik> Mirv: can you have a look: http://10.97.2.10:8080/job/unity-phablet-qmluitests/810/console
[08:11] <mmrazik> I would expect I don't see that sort of errors if I use apt-get install
[08:12] <tsdgeos> it works here otoh
[08:12] <tsdgeos> locally i mean
[08:14] <sil2100> mmrazik, tsdgeos: to me it seems that it uses some library that has been built against the old, 5.0.1 Qt5
[08:14] <tsdgeos> sure
[08:14] <mmrazik> yeah... which is something that should not happen due to deps
[08:14] <sil2100> mmrazik, tsdgeos: is the qt5-proper PPA enabled for the PPA where the test package has been built?
[08:15] <sil2100> We need to check if the PPA that's building the package actually used the new Qt5
[08:15] <sil2100> Where does the package come from?
[08:15] <mmrazik> sil2100: there isn't really any package... the job just tries to run qmlscene to workaround some other bug
[08:15] <mmrazik> with some super simple qml
[08:15] <sil2100> Oh
[08:15]  * sil2100 wasn't up-to-date it seems
[08:15] <mmrazik> sil2100:  http://pastebin.ubuntu.com/5647120/
[08:16] <mmrazik> I'm just trying to reproduce there
[08:17] <sil2100> Interesting, then it looks to me like indeed some dependency problem, maybe the Qt5 packaging would need an update, just I wonder which used package is not updated
[08:17] <sil2100> Actually, let me check ldd
[08:17] <mmrazik> sil2100: working on figuring that out
[08:18] <sil2100> mmrazik: I think we're missing updating libqt5qml5
[08:19] <sil2100> mmrazik, tsdgeos, Mirv: as you can see, qtdeclarative5-qtquick2-plugin is updated, but libqt5qml5 is not
[08:21] <sil2100> Or maybe it got removed, one moment?
[08:21] <sil2100> No, it did not
[08:21] <sil2100> Ok, so it's clearly something wrong with Qt5 deps - it should update libqt5qml5 as well in this case
[08:22] <sil2100> Mirv, mmrazik: I think that an update of either qtdeclarative5-qtquick2-plugin or qmlscene should also require the update of libqt5qml5, don't you think?
[08:22] <sil2100> Otherwise QML apps won't run anyway
[08:23] <sil2100> Mirv: ^^
[08:25] <mmrazik> sil2100, Mirv : it must be something more than that. I upgraded libqt5qml5 to 5.0.2-2ubuntu1~raring1~test2 and still getting the same error
[08:26] <sil2100> mmrazik: so probably something else as well
[08:26] <sil2100> mmrazik: sadly, from what popey says, Mirv might be off today ;(
[08:26] <mmrazik> sil2100: where should I report this sort of bugs?
[08:27] <mmrazik> I guess we can find the missing piece ourselves and workaround in jenkins
[08:27] <sil2100> mmrazik: one moment
[08:27] <popey> yeah, checked the holiday calendar, timo is out today, national holiday I believe
[08:27] <sil2100> mmrazik: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src <- maybe this is the right place for this bug
[08:31] <mmrazik> sil2100: libqt5quick5 seems to be the thing
[08:31] <sil2100> Awesome
[08:31] <sil2100> mmrazik: good catch
[08:32] <mmrazik> tsdgeos: can you try to retrigger the build?
[08:35] <mmrazik> lp:1178147
[08:35] <mmrazik> fyi
[08:37] <sil2100> mmrazik: thanks
[08:38] <tsdgeos> mzanetti: sure
[08:41] <tsdgeos> mmrazik: ↑ sure was for you :D
[08:41] <mmrazik> :)
[08:51] <tsdgeos> garg
[08:52] <tsdgeos> need to fix the qpa thing
[08:57] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity/qpa_502/+merge/163111
[08:57] <Saviq> tsdgeos, if I register a type, do you think there's any way to retrieve that type's name in QML?
[08:58] <Saviq> tsdgeos, the JS type is "object", and there seem to be no members
[08:58] <tsdgeos> no members?
[08:58] <tsdgeos> ouch
[08:58] <Saviq> tsdgeos, no properties / methods nothing
[08:58] <tsdgeos> Saviq: did a (for var in obj) console.log(var)?
[08:58] <Saviq> yeah
[08:58] <Saviq> nothing
[08:59] <tsdgeos> no idea then :-/
[08:59] <tsdgeos> errr
[08:59] <tsdgeos> wait
[08:59] <Saviq> I wonder if it'd be possible to pass it to C++ somehow
[08:59] <Saviq> but what would it be...
[09:00] <Saviq> tsdgeos, hum, why do we need private-dev
[09:00] <Saviq> ?
[09:00] <tsdgeos> Saviq: qpa
[09:00] <tsdgeos> Saviq: no, no idea sorry :/
[09:01] <Saviq> tsdgeos, that's fine
[09:02] <Saviq> tsdgeos, maybe the other way, ideas about getting an object by its name? other than eval()?
[09:03] <Saviq> i.e. eval("Type") could return the registered type
[09:04] <tsdgeos> nope :/
[09:04] <Saviq> so eval() works, but there's a "don't use eval" comment right next to it ;)
[09:05] <tsdgeos> :D
[09:06] <Saviq> fook it
[09:15] <tsdgeos> Saviq: what about https://code.launchpad.net/~aacid/unity/remove_qsortfilterproxymodelqml_get/+merge/162955 anything else we need?
[09:18] <mmrazik> sil2100: veebers's unity-3d MP just landed (FYI)
[09:18] <Saviq> tsdgeos, no, looks fine, will test and review in a bti
[09:18] <Saviq> bit
[09:18] <tsdgeos> okidokig
[09:18] <Saviq> tsdgeos, coming right up to some more stuff to take a look at on the interface test
[09:19] <tsdgeos> sure, just shout when you want me to have a look
[09:49] <Saviq> tsdgeos, pushed
[09:50] <Saviq> tsdgeos, the tests themselves should be more readable now
[09:50] <Saviq> tsdgeos, and there's been some refactoring...
[09:50] <tsdgeos> ok
[09:56] <tsdgeos> Saviq: fails to build here
[09:56] <tsdgeos> lp:~unity-team/+junk/shell-interfaces , right?
[09:56] <Saviq> tsdgeos, yeah, what does it complain about?
[09:56] <Saviq> tsdgeos, the enums by any chance?
[09:56] <tsdgeos> yep
[09:56] <Saviq> tsdgeos, that's just random
[09:56] <tsdgeos> says need c++11
[09:56] <Saviq> tsdgeos, yeah, I've no idea what's going on
[09:57] <tsdgeos> well, enum class needs c+11
[09:57] <tsdgeos> do we have it enabled?
[09:57] <Saviq> tsdgeos, I think so
[09:57] <Saviq> tsdgeos, and it builds here
[09:57] <Saviq> tsdgeos, anyway, I had that issue, removed the "class" from the enums
[09:57] <Saviq> tsdgeos, built fine
[09:57] <Saviq> tsdgeos, work, work, work
[09:57] <Saviq> add the "class" back
[09:57] <Saviq> builds fine
[09:58] <Saviq> I might be missing something somewhere, but dunno waht
[09:58] <Saviq> what
[10:00] <Saviq> tsdgeos, if you manage to find it, great, otherwise we'll drop them
[10:00] <tsdgeos> Saviq: http://paste.kde.org/~tsdgeos/740492/ works here
[10:00] <Saviq> tsdgeos, ah
[10:00] <tsdgeos> not sure why the difference you vs me though :-/
[10:00] <Saviq> tsdgeos, it might be that project() resets the flags
[10:00] <tsdgeos> would make sense
[10:00] <tsdgeos> but why works for you?
[10:02] <Saviq> tsdgeos, cache, probably
[10:02] <Saviq> tsdgeos, i.e. once it builds
[10:02] <Saviq> tsdgeos, it saves the new cflags in the cache
[10:02] <Saviq> and uses those
[10:02] <Saviq> or something
[10:04] <Saviq> tsdgeos, some more small commits just went in
[10:05] <Saviq> tsdgeos, actually, I need to roll back
[10:05] <tsdgeos> ok
[10:05] <tsdgeos> tell me again when you're done
[10:07] <Saviq> tsdgeos, now
[10:08] <Saviq> tsdgeos, ugh, one more minute
[10:09] <Saviq> tsdgeos, now, sorry
[10:09]  * Saviq wants git
[10:19] <tsdgeos> Saviq: void invokeAction(QString id); -> void invokeAction(const QString &id); to save 0.0005 µs? :D
[10:19] <Saviq> tsdgeos, indeed
[10:29] <tsdgeos> Saviq: i'm confused
[10:29] <Saviq> tsdgeos, go
[10:29] <tsdgeos> i've put a console.log at tst_notifications.qml in function test_model(data) {
[10:29] <mhr3> sil2100, what's up with utah today?
[10:29] <tsdgeos> before it calls verifyData
[10:29] <tsdgeos> and i see that log
[10:30] <tsdgeos> but then i've put a console.log in Verifier.qml in the verifyData and i don't see the log
[10:30] <tsdgeos> why¿?¿
[10:30] <mhr3> sil2100, ap tests taking 14minutes today... clearly something is broken :)
[10:30] <tsdgeos> running with qmltestrunner
[10:31] <Saviq> tsdgeos, where did you put the log at?
[10:31] <tsdgeos> Saviq: http://paste.kde.org/~tsdgeos/740516/
[10:31] <Saviq> tsdgeos, ah I know
[10:31] <Saviq> tsdgeos, Verifier.qml isn't copied
[10:31] <tsdgeos> i see calling verifyData and called verifyData
[10:31] <Saviq> tsdgeos, after changing
[10:31] <tsdgeos> but not the others
[10:31] <Saviq> tsdgeos, you need to edit the one in build/
[10:31] <Saviq> tsdgeos, we need to find a way for CMake to update those copied files
[10:32] <Saviq> tsdgeos, but otherwise you need to build
[10:32] <Saviq> tsdgeos, for the changed one to be copied
[10:32] <tsdgeos> make didn't help
[10:32] <tsdgeos> let me clear
[10:32] <tsdgeos> n
[10:32] <Saviq> check that the change is there in your $BUILD_DIR
[10:33] <tsdgeos> ah yeah, cleaning works
[10:33] <tsdgeos> so yeah that has to be fixed, at least make should update them
[10:36] <Saviq> in theory it does
[10:36] <Saviq> I've seen it updating it..
[10:36] <Saviq> but yeah we need a generic, reliable solution
[10:37] <tsdgeos> should
[10:37] <tsdgeos> { tag: "Model.roles[urgency]", role: "urgency", type: "number" },
[10:37] <tsdgeos> be
[10:37] <tsdgeos> { tag: "Model.roles[urgency]", role: "urgency", type: "enum" },
[10:37] <tsdgeos> ?
[10:40] <tsdgeos> Saviq: ↑↑
[10:40] <Saviq> tsdgeos, that could be a shortcut
[10:40] <Saviq> tsdgeos, but there's no way of distinguishing a number from an enum
[10:40] <Saviq> in JS
[10:43] <tsdgeos> right
[10:43] <tsdgeos> ok
[10:44] <tsdgeos> Saviq: in general looks good
[10:45] <Saviq> tsdgeos, cheer
[10:45] <Saviq> s
[10:45] <tsdgeos> there's still the
[10:45] <tsdgeos> if (writable) {
[10:45] <tsdgeos> in writeable
[10:45] <tsdgeos> which you said yesterday had to go away?
[10:47] <Saviq> tsdgeos, is there?
[10:48] <tsdgeos> yep
[10:48] <Saviq> tsdgeos, hmm not seeing it..
[10:48]  * tsdgeos pulls
[10:48] <Saviq> I do, however, see two debugs in there...
[10:48] <tsdgeos> ah, i was old
[10:48] <Saviq> wait
[10:48] <Saviq> wrong file
[10:49] <Saviq> tsdgeos, yeah, I fixed it... in a different project
[10:49] <tsdgeos> Saviq: you forgot to add the & to the QString
[10:49] <tsdgeos> :D
[10:49] <Saviq> ugh
[10:54] <Saviq> tsdgeos, I --overwrote, so you'll have to do the same next time
[10:56] <tsdgeos> ok
[10:58] <tsdgeos> Saviq: that's still the writable function i'm seeing http://paste.kde.org/~tsdgeos/740528/
[10:59] <Saviq> tsdgeos, pushed
[11:00] <tsdgeos> oki
[11:00] <tsdgeos> so yeah, seems good to me, haven't done a line per line check of Verifier
[11:00] <tsdgeos> but the tst_Notifications makes sense
[11:05] <Saviq> yeah, I need to write a test suite for the Verifier itself
[11:06] <Saviq> later
[11:06] <Saviq> tsdgeos, any idea of the simplest way to fake a QAbstractListModel?
[11:07] <Saviq> I was thinking QList<QVariantMap>, but that didn't work
[11:07] <Saviq> another possibility is QQmlListProperty, but that won't give up roles IIRC
[11:09] <Saviq> brb
[11:09] <tsdgeos> Saviq: what do you mean by fake?
[11:09] <Saviq> tsdgeos, mock, more than fake
[11:10] <Saviq> tsdgeos, i.e. what ListModel really does, but I'd need to pass it up from C++
[11:10] <Saviq> tsdgeos, so that I can, without implementing a complete QALM
[11:10] <Saviq> tsdgeos, get role-based data in a Repeater
[11:11] <tsdgeos> i see
[11:28] <tsdgeos> Saviq: what's the problem with qlist+qvariantmap?
[11:29] <Saviq> tsdgeos, didn't work here?
[11:29] <tsdgeos> you mean assigning it to a model: property?
[11:29] <Saviq> tsdgeos, yeag
[11:29] <tsdgeos> right
[11:29] <tsdgeos> that probably won't work unless it's a QALM
[11:29] <tsdgeos> afaik there are internal checks in what you can assign there
[11:30] <Saviq> I'll have a play with QQmlListProperty
[11:30] <Saviq> but then again...
[11:31] <Saviq> QALM is minimal, is it actually worth it...
[11:32] <Saviq> and not sure QQLP can at all work if it's not a property, but returned from QALM::data()
[11:51] <Saviq> tsdgeos, can you make sure that all the three videos still play with your remove_..._get branch?
[11:51] <Saviq> tsdgeos, I seem to only be able to play he Sintel one
[11:51] <tsdgeos> weird
[11:51] <tsdgeos> Saviq: playging from the carousel or after a search?
[11:51] <Saviq> tsdgeos, carousel
[11:51] <tsdgeos> oki
[11:51] <tsdgeos> lunch waiting
[11:51] <tsdgeos> will do first thing after
[11:52] <Saviq> tsdgeos, both, actually
[11:52] <Saviq> tsdgeos, sure, enjoy
[12:23] <sil2100> mhr3: good question! Let me check that now (just got back from lunch)
[12:48] <sil2100> Utah is strange
[12:49] <sil2100> It looks as if utah was killing all the tests prematurely
[12:49] <sil2100> How are we supposed to merge in the 100scopes when we can't get the right test results?
[12:50] <sil2100> mhr3: btw. what autopilot are you guys using for the 100scopes branch?
[12:50] <sil2100> Since this might be a blocker as well
[12:51] <sil2100> Of course this depends on whether you were modifying/adding any autopilot tests or all is in trunk already
[12:52] <mhr3> sil2100, one that trunk was using up until a week ago
[12:55] <dandrader> today (booting up the computer after yesterday's updates) unity is no longer starting up for me on 13.04. If I run it manually there's a compiz error saying that plugin 'opengl' could not be loaded.
[12:57] <bregma> dandrader, do you have any suspicious PPAs in your sources list anywhere?
[12:57] <kgunn> dandrader: hmmm, i actually updated yesterday....kinda early in the day...and no problems for me
[12:58] <dandrader> bregma, I have http://ppa.launchpad.net/phablet-team/desktop-deps/ubuntu  and http://ppa.launchpad.net/phablet-team/tools/ubuntu
[12:59] <dandrader> bregma, if I run it manually (typing "unity" in the terminal) it says plugin 'opengl' could not be loaded
[13:00] <kgunn> dandrader: sounds like a binary mismatch on the proprietary drivers....x version vs what they were compiled against
[13:01] <bregma> yeah, I see new xorg drivers in my update list in a fresh 13.04 install
[13:01] <kgunn> paulliu: ping
[13:02] <dandrader> I even removed the nvidia packages and switched to use my onboard intel graphics
[13:02] <dandrader> but problem remains
[13:04] <paulliu> paulliu: hi
[13:04] <tsdgeos> Saviq: we sould do a release
[13:04] <tsdgeos> Saviq: to get the qpa thing in
[13:04] <Saviq> tsdgeos, yeah, we should
[13:05] <tsdgeos> Saviq: otherwise the run_on_device fails
[13:05] <tsdgeos> Saviq: want me to do it?
[13:05] <Saviq> tsdgeos, go for it
[13:06] <tsdgeos> Saviq: btw all the videos fail here but that's because the device video player seems to be borked (i.e. doesn't work without my patch either) but the paths seem to be correctly passed, where are you trying it on? device or pc?
[13:07] <Saviq> tsdgeos, device, and it plays fine on stock qml-phone-shell
[13:07] <tsdgeos> Saviq: which image?
[13:07] <Saviq> tsdgeos, 115, probably, checking
[13:07] <Saviq> where do we find the image number again...
[13:08] <tsdgeos> /etc/somewhere
[13:08] <Saviq> phablet-flash it is, then
[13:13] <dandrader> well, gnome-fallback works at least. will use it for now...
[13:17] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity/release175/+merge/163143
[13:18] <Saviq> tsdgeos, all plays fine on image 119 on the N10
[13:18] <kgunn> dandrader: this is really hacky, but i had a similar issue recently, i did apt-get dist-upgrade/upadate/autoremove/autoclean...twice, everything got happy
[13:19] <tsdgeos> Saviq: i updated/dist-upgraded and my qsortfilterbranch can now play the 3 videos correctly
[13:19] <tsdgeos> you can't?
[13:19] <kgunn> dandrader: this is really hacky, but i had a similar issue recently, i did apt-get dist-upgrade/upadate/autoremove/autoclean...twice, everything got happy
[13:19] <Saviq> tsdgeos, didn't try with your branch yet, stock 119 for now
[13:29] <Saviq> tsdgeos, yeah, seems the media player is unstable
[13:29] <Saviq> tsdgeos, works
[13:30] <tsdgeos> :)
[13:45] <tsdgeos> Saviq: do you want to do https://code.launchpad.net/~aacid/unity/hud-result-highlighting/+merge/163115 or maybe dandrader can do it?
[13:47] <Saviq> tsdgeos, I don't have to
[13:48] <tsdgeos> cool
[13:48] <tsdgeos> dandrader: can you do it?
[13:50] <dandrader> tsdgeos, yes, I can review it
[13:50] <tsdgeos> dandrader: tx
[13:57] <tsdgeos> dandrader: your edge drag now passed :-)
[13:57] <tsdgeos> oh lol
[13:57] <tsdgeos> long lines dude again :D
[13:58] <dandrader> :)
[13:58] <tsdgeos> should have chosen someone else
[13:58] <dandrader> heehhe
[13:58] <tsdgeos> where's mzanetti when you need him :D
[13:58]  * tsdgeos adds some newlines
[14:03] <tsdgeos> dandrader: lines splitted
[14:03] <dandrader> \o/
[14:30] <Saviq> uurgfh
[14:31] <Saviq> note to self: do not do "property var something; something: Item { }"
[14:34] <Saviq> the Item is not considered as it would be normally
[14:43] <tsdgeos> Saviq: what's the difference?
[14:43] <Saviq> tsdgeos, it must be marked non-visual or something
[14:43] <Saviq> tsdgeos, so when I had a Repeater there
[14:43] <Saviq> tsdgeos, it would not query the model at all
[14:44] <Saviq> tsdgeos, it would query the count, but not the roles
[14:44] <tsdgeos> interesting
[14:44] <Saviq> tsdgeos, nor, effectively, the actual data
[14:44] <Saviq> tsdgeos, could deserve a check if it's a feature, and not a bug
[14:45] <tsdgeos> Saviq: fwiw the support enum class in QFlags was merged and will be available for 5.1
[14:45] <tsdgeos> Saviq: true
[14:46] <Saviq> tsdgeos, interesting
[14:46] <tsdgeos> i mean, i did a quick fix yesterday in 10 minutes i was waiting for something else to compile with the guidance of some of the Qt guys
[14:46] <tsdgeos> just neeed to throw some more casting around
[14:47] <Saviq> yup
[14:53] <paulliu> tsdgeos: https://code.launchpad.net/~paulliu/unity/phablet-fake-peoplepreviewdata/+merge/161514
[14:53] <paulliu> tsdgeos: I just re-use the branch.
[14:53] <tsdgeos> oki
[14:54] <tsdgeos> dandrader: to be honest doing the check that we are in bounds twice feels a bit weird, but ok, no point in discussing over that :D
[14:55] <dandrader> tsdgeos, I don't feel strongly about it, you're free to not do it
[14:56] <tsdgeos> dandrader: pushed
[15:00] <tsdgeos> paulliu: lol, setUnityPeoplePreview was defined but not implemented?
[15:01] <paulliu> tsdgeos: No.. :P
[15:01] <tsdgeos> :D
[15:01] <tsdgeos> nice one
[15:02] <tsdgeos> paulliu: yes, that's what i meant
[15:02] <paulliu> tsdgeos: ok. I'll add data into that variants.
[15:02] <tsdgeos> makes mroe sense to have a mock PeoplePreviewData than a almost reimplement half of the qml we wanted to test
[15:02] <tsdgeos> cool :)
[15:08] <tsdgeos> Saviq: how much into know of the ListViewWithPageHeader tasks are you?
[15:08] <Saviq> tsdgeos, E_SYNTAXERROR
[15:08] <tsdgeos> :D
[15:08]  * tsdgeos stops trying to sound smart
[15:09] <tsdgeos> Saviq: the ListViewWithPageHeader tasks at https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-dash
[15:09] <tsdgeos> Saviq: there's one that says "reimplement in C++"
[15:09] <tsdgeos> do we really need that¿
[15:09] <tsdgeos> or that's exposed as a possibility to have the other issues we have wiht the component if we can't fix them in pure QML?
[15:10] <Saviq> tsdgeos, it felt like the sounder approach
[15:10] <Saviq> tsdgeos, to not fight with the tool
[15:11] <tsdgeos> sure
[15:11] <tsdgeos> but has it's own set of problems as Gerry discovered
[15:11] <tsdgeos> i.e. basically has the small problem of "can't be done" :
[15:11] <tsdgeos> :D
[15:11] <Saviq> yeah indeed
[15:13] <Saviq> tsdgeos, based on past experience, though, I'm afraid of QML approach being unmaintainable
[15:13] <tsdgeos> why?
[15:13] <tsdgeos> i mean not the current thing we hav
[15:13] <tsdgeos> but something that may be "better"
[15:14] <tsdgeos> if we can make it happen of course :D
[15:14] <Saviq> tsdgeos, yeah exactly
[15:14] <tsdgeos> Saviq: as far as i understand the problem is having the flickable + listview
[15:14] <tsdgeos> that makes the listview unhappy
[15:14] <tsdgeos> right?
[15:15] <Saviq> tsdgeos, not really
[15:15] <tsdgeos> oh
[15:15] <Saviq> tsdgeos, the biggest issue is, I'd say, the fact that you have to clip manually
[15:15] <Saviq> tsdgeos, the flickable + listview is just a hack
[15:15] <tsdgeos> well, that's listview for you
[15:16] <tsdgeos> listview is weird in that it needs to be clipped
[15:16] <Saviq> but if originY and contentY behaved as advertised
[15:16] <Saviq> not even that it needs to be clipped
[15:16] <Saviq> that's relatively fine
[15:16] <Saviq> but the fact that you need to clip the delegates when they go behind the section header
[15:16] <Saviq> that was a o_O moment for us
[15:17] <Saviq> == we don't support transparent section headers
[15:17] <tsdgeos> do we need to?
[15:18] <Saviq> with the design we have, yes
[15:18] <Saviq> and tbh it's not an unreasonable request
[15:18] <Saviq> unless you copy parts of the background to the section headers
[15:18] <tsdgeos> don't know, looks weird to have something going behind the section header
[15:18] <tsdgeos> but i guess i'd have to see it
[15:19] <Saviq> tsdgeos, that's what happens now
[15:19] <tsdgeos> not on the phone, no?
[15:19] <Saviq> yes
[15:20] <Saviq> but we manually clip the delegates
[15:20] <tsdgeos> ah
[15:20] <tsdgeos> ok, so it's not happening :D
[15:20] <Saviq> otherwise you could see them behind the section header
[15:20] <tsdgeos> i thought i wasn't looking at the correct place
[15:21] <Saviq> tsdgeos, I dunno, doing it all "properly" in C++ felt like a good solution
[15:21] <Saviq> tsdgeos, but obviously that seems to be "unsupported" even more
[15:21] <tsdgeos> yep
[15:21] <Saviq> we could try and upstream parts of it
[15:22] <Saviq> I do believe the "clip behind section headers" part
[15:22] <Saviq> could be received by upstream
[15:22] <Saviq> disabled by default
[15:22] <tsdgeos> we could always extend listview to do what we want i guess
[15:22] <Saviq> well, that was the idea
[15:23] <Saviq> but it seems it would mean distropatching
[15:23] <Saviq> tsdgeos,we had one other potential idea
[15:24] <Saviq> tsdgeos, one that would require even more maths
[15:24] <tsdgeos> :D
[15:24] <Saviq> but would support "don't create items that are offscreen"
[15:24] <Saviq> tsdgeos, do you know all the requirements for the component?
[15:24] <tsdgeos> for ListViewWithPageHEader?
[15:24] <tsdgeos> not really
[15:25] <Saviq> yes
[15:25] <tsdgeos> i was waiting for gerry
[15:25] <tsdgeos> while doing some other stuff today
[15:25] <Saviq> read through that paragraph
[15:26] <tsdgeos> which paragraph?
[15:26] <Saviq> the whole doc, really
[15:27] <Saviq> there's a few navigation patterns that we need to support, and consider resource constraints for
[15:27] <Saviq> because as you know we're doing "let's load everything we could ever show" now
[15:28] <Saviq> tsdgeos, let's do a hangout tomorrow morning
[15:28] <Saviq> tsdgeos, and we'll try to pass on the knowledge
[15:28] <tsdgeos> yeah
[15:28] <tsdgeos> that doc seems different to what we do have at the moment
[15:28] <tsdgeos> no point in doing what we have now if it's not what we want :D
[15:28] <Saviq> we don't have everything indeed
[15:29] <Saviq> well, we're mostly missing the "collapse" / "expand" behavior
[15:29] <Saviq> but that's really an extension of the default one
[15:29] <tsdgeos> and the index view thing
[15:29] <Saviq> yeah, that's the "collapse"
[15:30] <tsdgeos> ah :D
[15:30] <tsdgeos> ok
[15:30] <Saviq> but that's easy
[15:30] <Saviq> just make all delegates 0 height
[15:30] <Saviq> assuming the ListView won't die on us
[15:30] <Saviq> when we do that
[15:30] <Saviq> anyway
[15:30] <tsdgeos> he he
[15:30] <tsdgeos> yes, let's do a hangout tomorrows
[15:31] <Saviq> gtg, started 7am today again
[15:31] <tsdgeos> enojy the evening!
[15:31] <Saviq> you too
[15:31] <Saviq> o/
[15:33] <mhr3> sil2100, here?
[15:45] <dandrader> tsdgeos, where is this 5.0.2+dfsg1-3ubuntu1~raring1~test2 qt version? I need to add some testing ppa for that?
[15:45] <dandrader> s/testing/special
[15:52] <tsdgeos> dandrader: qt5-proper ppa
[15:53] <tsdgeos> but with the new variation of the code you may not even need it
[15:54] <tsdgeos> anyways
[15:54] <tsdgeos> https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-proper
[15:54] <tsdgeos> dandrader: ↑↑↑
[15:56] <tsdgeos> dandrader: you should probably install it since it's what the device is using nowadays
[16:09] <sil2100> mhr3: here
[16:11] <mhr3> sil2100, there's a nasty bug in 100scopes right now, any chance you could restart the build job?
[16:11] <mhr3> so new stuff gets into the prevalidation ppa
[16:12] <sil2100> mhr3: let me check if I have the permissions to do that, if not I'll poke someone who can
[16:13] <sil2100> But I think I can
[16:13] <mhr3> dziekuje
[16:26] <sil2100> mhr3: ok, triggered the rebuild of the stack, will take a while
[16:27] <mhr3> sil2100, thx, there weren't too many changes, so should be fairly fast
[16:48] <sil2100> mhr3: anyway, in overall, are you guys ready with merging everything to trunk? i.e. all regressions fixed, autopilot tests running on 1.3 etc. ;) ?
[16:50] <mhr3> sil2100, i was told that we need one more ack from john and he's on holiday until tuesday.... so
[16:50] <sil2100> Ah, ok, I'll note it down
[16:50] <mhr3> we'll prepare everything, all merges will be there, just waiting for someone to press approved on all of them
[16:51] <sil2100> Since on my schedule it was 'help getting it merged and enabled for daily-build till the EOW', but it seems we'll do that next week
[16:51] <mhr3> but apparently the earliest that can happen is on tuesday
[16:51] <sil2100> I'll also prepare the addition branches to the configs
[16:51] <sil2100> mhr3: ok, thanks for the info
[16:52] <jtolds> what mailing list is appropriate for emailing libappindicator development questions?
[16:52] <jtolds> anyone know?
[18:18] <sil2100> fginther: ping!
[18:19] <sil2100> fginther: do you know if there is autolanding for this branch enabled? Since it doesn't get merged somehow: https://code.launchpad.net/~attente/unity-gtk-module/autopilot-menus/+merge/163161