[00:20] <nik90> loicm: yeah I managed to get exactly what I want
[00:21] <nik90> loicm: but the only issue I am facing is I am unable to hide the shadereffectsource itself :P
[00:21] <nik90> if I hide it, then the ubuntu shape shows black
[00:22] <loicm> nik90: have you tried to explicitly call scheduleUpdate() on the source?
[00:22] <nik90> loicm: no I haven't. I wasnt aware of that function
[00:22]  * nik90 looks at the doc
[00:23] <nik90> loicm: do I have to call scheduleUpdate() ? Since this ubuntu shape will be used in a listview where the data is static. so no live changes
[00:25] <nik90> loicm: also for now, I have assigned a width and height of units.gu(1) to hide it below the ubuntushape.
[00:25] <nik90> Although it seems a bit hacky way.
[00:25] <nik90> :P
[00:25] <loicm> nik90: sure but that might allow to render it once at creation and have the source correctly hidden
[00:27] <nik90> loicm: were you referring to my scheduleUpdate() question or the width/height to units.gu(1) ?
[00:27] <nik90> s/referring/answering?
[00:27] <loicm> nik90: to the scheduleUpdate() one
[00:28] <loicm> nik90: and if it works, it would solve your last issue as you wouldn't have to do that anymore
[00:29] <nik90> loicm: so I would call the scheduleUpdate() when the component has been loaded? Using the component.onCreation signal?
[00:32] <loicm> nik90: IIRC you could do something like that: Component.onCompleted: { source.scheduleUpdate(); }
[00:33] <loicm> in your main view
[00:34] <nik90> loicm: that's didn't work :/
[00:37] <loicm> nik90: just make sure it's called by putting a print in there, if it's called then I guess I'll have to take a deeper look at it, it's a use case that hasn't really been used so far
[00:38] <loicm> nik90: but that's perfectly valid and useful
[00:44] <nik90> loicm: I can confirm it is called, but it doesn't hide it. But thats fine for now I think. Thanks for your help.
[00:44] <nik90> I managed to implement the design spec as required :)
[00:45] <loicm> nik90: it's not meant to hide it, it's meant to avoid having it black when source is set as not visible :)
[00:45] <loicm> nik90: cool
[08:14] <dholbach> good morning
[09:22] <JamesTait> Good morning all! :-D
[09:35] <Smit-Tay> Can anyone please explain why attempting to install 32 bit development libraries should result in this:  http://pastebin.com/QbqZuCZR
[09:36] <Smit-Tay> I am trying to target 32bit from x86_64 Ubuntu 12.04
[09:36] <Smit-Tay> target 32bit intel
[09:41] <Smit-Tay> Are there good (current) instructions for how to go about setting up a development environment for targeting both x86 and x86_64 on Ubuntu 12.04 x86_64.  I find tons of info, but, most of it is related to multilib, which I understand to be deprecated.  In fact, I think part of my problem is exactly that I have attempted to use multilib but somehow by updating my compiler to 4.7 I have invalidated that.
[10:43] <drpaneas> Hello there
[10:44] <drpaneas> I have a Python script and I want to embed it inside Dash
[10:44] <drpaneas> how can I do that ?
[10:45] <drpaneas> I mean, I want to output of the script to be printed inside the Dash instead of the terminal
[10:56] <drpaneas> no one ?
[11:05] <ogra_> drpaneas, http://saravananthirumuruganathan.wordpress.com/2011/08/05/tutorial-on-writing-ubuntu-lensesplaces-in-python/ (among the first hits on google... not sure how up to date it is though)
[11:12] <drpaneas> ogre thanks mate
[11:12] <drpaneas> @ogra_ thanks
[12:11] <mzanetti> dpm: o/
[12:12] <dpm> hey mzanetti, belated happy new year :)
[12:12] <mzanetti> dpm: :) thanks. you too
[12:13] <mzanetti> dpm: I'm trying to clean up the reminders-app state for tomorrow's meeting. could you please give this one a shot? https://code.launchpad.net/~mzanetti/reminders-app/add-image-support/+merge/199031
[12:13]  * dpm looks
[12:17] <dpm> mzanetti, sure, give ~30 mins to give it a go
[12:17] <dpm> I meant give *me
[12:17] <mzanetti> ok, sure
[14:35] <zsombi> nik90: hi man, I've checked the MR, I haven't seen anything wrong in using the component
[14:36] <nik90> zsombi: ah thnx :)
[14:37] <nik90> zsombi: There is one issue I faced
[14:37] <zsombi> nik90: which one?
[14:37] <nik90> zsombi: that is when you assign hand.draggable = true (in the case of the timer), and the user adjusts the timer and presses start. The animation is choppy on my desktop.
[14:38] <nik90> zsombi: the issue goes away when I set hand.draggable = false
[14:38] <zsombi> hmm...
[14:38] <zsombi> nik90: have you filed a bug?
[14:38] <nik90> so in my custom component I had before, I used to disable the animation while the timer is running
[14:38] <nik90> zsombi: no not yet
[14:38] <nik90> I will do it now
[14:39] <zsombi> nik90: as workaround you could set the draggable to false while you have the timer running
[14:39] <nik90> zsombi: yeah. I will do that
[14:39] <nik90> zsombi: but I really like the dialer.
[14:39] <zsombi> nik90: but not sure whether I could provide any better solution for that... but file the bug, I will check it
[14:40] <nik90> I must ask though, the style is exactly like the clock app.
[14:40] <zsombi> nik90: ;)
[14:40] <nik90> but the dialer is different from the picker style
[14:40] <nik90> is that okay?
[14:40] <zsombi> nik90: what do you mean? the visuals?
[14:40] <nik90> yeah the visuals
[14:40] <nik90> the default purple tone for the dialer
[14:41] <zsombi> ah, yeah... the visuals have not been checked by the design, so in case I need to change it to use different color, I will ping you, so you can create a different style for your app
[14:41] <nik90> zsombi: awesome.thxn
[14:41] <nik90> zsombi: that was all
[14:41] <zsombi> nik90: for now use it as is
[14:41] <nik90> ok
[14:42] <zsombi> nik90: glad you like it... I made it for the TimePicker, but then the design had changed and time picker uses tumbler style Pickers... so the component was there for you to use it ;)
[14:42] <zsombi> nik90: dedicated to Clock app :D
[14:43] <nik90> zsombi: :D
[14:43] <zsombi> nik90: actually I've reused some of your design for the component :)
[14:44] <nik90> zsombi: I noticed..but you also inherited some bugs as a result :p
[14:44] <nik90> zsombi: which is what I will report about :)
[14:44] <zsombi> nik90: but in the rush hour I forgot to ping you to let U know about the component
[14:44] <zsombi> nik90 :P yes, I imagined so :D
[14:45] <zsombi> nik90: if you have the solution, you could also post them... or better, you could post a fix for those :D
[14:45] <nik90> zsombi: I will
[14:45] <zsombi> nik90: btw, what bothers me a bit is the fact that the hour hand in Clock app uses 360 for 24h not for 12h...
[14:46] <zsombi> nik90: so when I'm at 6h, it is actually 12h...
[14:46] <nik90> zsombi: true, this is where we need a setting for 12/24 hours format
[14:47] <nik90> zsombi: I am planning to add one soon, so that should help fix your issue
[14:47] <nik90> zsombi: by default I stuck to 24 hours since I couldn't display AM/PM in the UI
[14:47] <zsombi> nik90: I'd say no matter of that, when the hour hand points to 6, it should be either 6 or 18/6pm.. like in N9
[14:48]  * nik90 is checking the android clock for the behaviour
[14:49] <zsombi> nik90: I feel Android is not the best example :/
[14:49] <nik90> zsombi: it also uses the N9 behaviour you described
[14:49] <zsombi> nik90: ok... didn't knew that... I don't have Android, I don't like them at all :)
[14:50] <nik90> zsombi: I will remember to report this as a design bug and get some eyes on this to decide on the best behaviour
[14:50] <zsombi> nik90: ok, thx
[15:28] <dholbach> hey guys... could anyone help with porting lp:~karni/+junk/todo-qt to use U1DB?
[15:29] <dholbach> it's one example we'd like to use for the app dev schools project, so folks get a first experience in writing good apps
[15:30] <dholbach> ... any other pointers on how the code could be simplified/improved would obviously be appreciated too :)
[15:39] <daker> kenvandine: how much i need to pay so that friends becomes like this http://www.canonical.com/static/img/home/tablet-home.png ?
[15:39] <kenvandine> not pay :)
[15:40] <daker> :)
[15:40] <kenvandine> just need someone to implement it :)
[15:40] <kenvandine> looks very nice
[15:43] <daker>     WOW!
[15:43] <daker> MUCH NICE!
[15:43] <daker>        SO PICTURES!
[15:52] <daker> kenvandine: i would like also to have a details page for the comments part, rather than opening them on the same place
[15:56] <kenvandine> daker, it does that already
[15:56] <kenvandine> as of recently
[15:57] <daker> kenvandine: perfect!!
[15:57] <kenvandine> that landed before the holidays
[15:57] <ErWinR> anyone familiar with quickly and glade ??
[16:18] <daker> kenvandine: still blue ?
[16:22] <kenvandine> daker, yeah
[16:23] <kenvandine> daker, where did you find that image?  i haven't seen it before
[16:23] <daker> kenvandine: leaked :p
[16:23] <kenvandine> it must be on some site :)
[16:23] <kenvandine> i've just never seen it
[16:24] <daker> kenvandine: on the new canonical website http://www.canonical.com
[16:24] <kenvandine> i had played with some organic stuff like that, i love shorts
[16:25] <kenvandine> but haven't had time for friends in a while
[17:02] <mzanetti> balloons: hey
[17:03] <mzanetti> balloons: what exactly does an app need to ship in terms of test packages?
[17:03] <mzanetti> do we need to have a .deb with the tests and a click pacakge with the tests?
[17:04] <balloons> mzanetti, howdy. For now, yes we need both. Jenkins merge bot uses the debs, while the dashboard uses click
[17:05] <mzanetti> balloons: hmm... can you point me to a tutorial for click packages containing tests?
[17:27] <balloons> mzanetti, I can't.. I may be misinformed.. so much has changed with click I would suggest asking sergio
[17:28] <balloons> the tests should be copied to /home/phablet/autopilot and run from there
[17:35] <balloons> perhaps the dashboard does it the same, pulls the branch rev, builds click, copies the tests over from branch
[18:04] <popey> nik90: mzanetti has reviewed that merge..
[18:04] <popey> ah, you're on it ☻
[18:04] <popey> too fast for me you younguns
[18:05] <nik90> popey: lol..I didnt see his comment before posting mine...I am in the process of fixing it
[18:08] <mzanetti> nik90: hmm.. the timer still seems to run out of sync
[18:09] <nik90> mzanetti: on which device?
[18:10] <mzanetti> PC
[18:10] <nik90> mzanetti: also do you mean the text and the timer go out of sync?
[18:10] <mzanetti> nik90: seems the pointer is slightly faster than the text
[18:10] <mzanetti> hmm... maybe not
[18:11] <mzanetti> maybe its just my brain going ot of sync watching the click go round and round
[18:11] <nik90> mzanetti: the pointer is intended to be faster than the text
[18:11] <nik90> as in, the text should update only when the pointer reaches its destination
[18:12] <mzanetti> I think that's what confused me. in all the other pages first the time ticks, and then the pointer moves
[18:12] <mzanetti> while in the timer page its the other way round
[18:12] <nik90> previously we had it such that the text and timer update at the same time.
[18:12] <nik90> mzanetti: what would your recommended behaviour be?
[18:13] <nik90> should it stay as it is or change it?
[18:13] <popey> I always prefer the time to change in the middle at the point when the hand hits that number
[18:13] <mzanetti> hmm... without having spend as much thought as you did, I would say moving at the same time would be the best from a users pov
[18:13] <popey> so 11:59 (hand leaves 59)... (hand arrives on 00).. 12:00.
[18:13] <mzanetti> like the time ticks exactly in the middle of the pointer movement
[18:14] <mzanetti> hmm...
[18:14] <popey> it always seemed odd to me that the clock might say 12:00 while the hand was only just leaving 11:59
[18:14]  * nik90 meanwhile fixes the required stuff in the background
[18:14] <popey> because technically it's 11:59.000 then 11:59.001 etc, not 12:00 yet
[18:14] <mzanetti> yeah... your right
[18:15] <mzanetti> like it is in the timer page its the best. but I have a feeling that there is a small delay which makes it look odd again
[18:15] <popey> yeah
[18:15] <nik90> mzanetti: it is hard to get that timing right.
[18:15] <mzanetti> I guess so
[18:16] <mzanetti> hmm... actually not
[18:16] <mzanetti> well, depends on the code.
[18:16]  * mzanetti reads
[18:16] <nik90> right now it is delayed by 0.5 secs (the text update)
[18:20] <mzanetti> nik90: from what I can see the SDK uses a default RotationAnimation. And according to the Qt docs the default duration for that one is 250ms
[18:25] <nik90> mzanetti: on trying that value, it definitely seems more smoother :)
[18:26] <mzanetti> cool
[18:26] <nik90> mzanetti: should I change it in this MP itself?
[18:26] <mzanetti> I'd say yes. it touches all that code anyways
[18:26] <mzanetti> but you have more insights on the practices in the clock apps team than I do
[18:27] <mzanetti> nik90: could we align all the pages to do the same?
[18:29] <nik90> mzanetti: I rather do that in a separate MP since these qml timers have introduced delays before like timer set for 2 mins running for 02:03 due to the phone hardware.
[18:29] <nik90> so it would be easier to track that regression in a separate MP.
[18:29] <mzanetti> ok. fine with me
[18:34] <popey> mzanetti: "clock apps team" basically == nik90
[18:35] <popey> (and you now)
[18:35] <popey> (you can never leave)
[18:37] <mzanetti> :D
[18:39] <ahayzen> no pressure nik90 ;)
[18:40] <ahayzen> nik90, thanks for ur help with the CoverRow stuff :)
[18:47] <nik90> ahayzen: np
[18:47] <nik90> popey: lol
[18:47] <nik90> mzanetti: fixed ur comments in the MP
[18:50]  * nik90 rejoices at image 119 adding haptic feedback finally..
[19:25] <mzanetti> nik90: much better with the 250ms :)
[20:58] <nik90> ahayzen: just 1 more small fix.
[20:58] <ahayzen> nik90, yep?
[20:58] <ahayzen> nik90, ah u commented on the MP ;)
[21:00] <nik90> ;)
[21:01] <ahayzen> nik90, pushed up :)
[21:04] <ahayzen> nik90, yey ready for merge! ... now back to my attempt at a massive refactor....
[21:07] <nik90> ahayzen: which files?
[21:08] <nik90> ahayzen: I am targetting a code refactor too :P
[21:08] <ahayzen> nik90, hah probably most of them ;)
[21:08] <ahayzen> nik90, wht for?
[21:08] <ahayzen> nik90, i started developing some new features and have got fed up with the way things currently work so gonna change it all
[21:09] <ahayzen> nik90, i'm basically attempting to centralising the MediaPlayer object into its own file so it handles itself, eg all the shuffle, repeat, next, previous etc
[21:09] <nik90> ahayzen: I am planning a code refactor for MusicArtists and MusicTracks.qml files
[21:09] <nik90> ahayzen: similar to https://code.launchpad.net/~nik90/music-app/album-code-refactor-and-fixes/+merge/200946
[21:10] <ahayzen> nik90, because at the moment if u want to change shuffle/repeat it is pretty difficult (u'll have to set the settings, the global variables and go and find any UI items and change their state lol)
[21:10] <ahayzen> nik90, ah cool...also note (in ur refactoring) https://code.launchpad.net/~vthompson/music-app/use-sheet-pattern/+merge/200140
[21:11] <nik90> ahayzen: ah okay
[21:11] <nik90> ahayzen: i plan to get my branch in before that :P
[21:11] <nik90> so I wouldnt have to deal with conflicts
[21:11] <nik90> lol
[21:11] <ahayzen> nik90, so wht i'm planning is tht everything else listens to the mediaplayer object so if u wanna change shuffle/repeat u just go player.shuffle = true .. job done :)
[21:11] <ahayzen> nik90, hahah lol
[21:12] <ahayzen> nik90, i've got a similar issue with the sheet pattern and my reorder code lol
[21:12] <nik90> ahayzen: since we both have (will have) conflicts with the sheet pattern MP, we ask him to wait until we are done
[21:12] <nik90> victor will listen to 2 of us :)
[21:13] <ahayzen> nik90, well at least one of us will have merge conflicts lol ;)
[21:13] <nik90> rofl
[21:13] <Ahmed_> Hi geeks
[21:13] <ahayzen> nik90, my reorder code is blocked/buggy anyway
[21:14] <Ahmed_> I wanna some docs for beginners devlopers
[21:14] <nik90> ahayzen: oh true, you are waiting on ur upstream branch to be merged first
[21:14] <ahayzen> nik90, yep
[21:14] <ahayzen> nik90, even if we don't enabled scrolling in tht MP it'll get rid of our custom swipedelete finally \o/
[21:14] <nik90> ahayzen: oh btw, there is one thing I thought is recommended..keep your files small..
[21:15] <ahayzen> nik90, yeah thts why i'm trying to move Mediaplayer out
[21:15] <nik90> for instance the MusicAlbums.qml was massive while it could have been split into two files easily
[21:15] <ahayzen> nik90, it has cause music-app.qml to become HUGE!
[21:15] <nik90> I will help with that organisation
[21:15] <ahayzen> nik90, MusicAlbums.qml is much smaller after lp:~vthompson/music-app/use-sheet-pattern ?
[21:15] <nik90> I am first starting to clean and refactor code before proposing organization stuff
[21:15]  * nik90 looks
[21:16] <ahayzen> nik90, u agree with my thoughts on moving Mediaplayer into its own 'thing'
[21:17] <nik90> ahayzen: I agree on your reasoning to allow for easy global access. however I need to look more closer at the code to make a decision in all honesty
[21:17] <ahayzen> nik90, i think i can get rid of half of the global variables ... just accessing the trackQueue model could be the interesting part...
[21:18] <ahayzen> nik90, but i'll see how it all looks when it is ripped out :)
[21:18] <nik90> :)
[21:19] <nik90> ahayzen: +1 to the MusicAlbums.qml being smaller in victor's branch
[21:19] <nik90> I wonder where all the deleted code went?
[21:19]  * nik90 digs deepre
[21:19] <ahayzen> nik90, well he has a generic sheet now :)
[21:19] <nik90> clever
[21:19] <ahayzen> nik90, or maybe 2... http://bazaar.launchpad.net/~vthompson/music-app/use-sheet-pattern/view/head:/common/AlbumsSheet.qml
[21:19] <ahayzen> nik90, http://bazaar.launchpad.net/~vthompson/music-app/use-sheet-pattern/view/head:/common/SongsSheet.qml
[21:20] <nik90> ahayzen: that's much better.
[21:20] <ahayzen> nik90, yep :)
[21:20] <nik90> ahayzen: he still has to bring in the CoverRow component into his MP
[21:20] <nik90> that should reduce it more
[21:21] <ahayzen> nik90, just now we have the issue of the toolbar not being shown over the sheet
[21:21] <ahayzen> nik90, any ideas how to force an object ontop of everything else?
[21:22] <nik90> ahayzen: that's a tough one, since dialogs, sheets etc take precedence over everything
[21:22] <ahayzen> nik90, yep i know but it is really annoying, i tried setting the z to 1000 lol
[21:22] <nik90> lol
[21:23] <nik90> ahayzen: have you tried talking to timp or Kaleo perhaps?
[21:23] <nik90> they are the qml experts
[21:23] <ahayzen> nik90, not yet
[21:23] <ahayzen> nik90, it is only gonna become a *real* issue when tht branch lands
[21:23] <ahayzen> nik90, at the moment it is only one use case...but it is on my list of things to investigate :)
[21:24] <nik90> ahayzen: actually it is also a bug before that in the album tracks sheet
[21:24] <nik90> Albums->Click on Album-> Try revealing toolbar
[21:25] <nik90> ahayzen: out of curiosity why sheets instead of pagestack?
[21:25] <ahayzen> nik90, ^^ is the one use case i mean
[21:25] <nik90> I thought sheets were meant for getting user actions like email compose sheet etc
[21:25] <nik90> ah
[21:26] <ahayzen> nik90, haha don't get me started on tht i wanted just to use Pages like i did with the now playing page (it works perfectly) ...
[21:26] <nik90> ahayzen: ah so victor is pushing for it?
[21:26] <ahayzen> nik90, but see the link for wht the structure basically became https://docs.google.com/document/d/12ZvFDfH-7zjk-seTFpP205yOuUNi9ticEkvmQFi_bTY/edit#heading=h.qbx9jfq13q3e
[21:27] <ahayzen> nik90, designers+Victor > me
[21:27] <ahayzen> nik90, except i have won on the play queue...but shhhh don't tell anyone ;)
[21:28] <nik90> ahayzen: so looking at that structure, does that mean there is only 1 sheet (albums) in the app then?
[21:28] <ahayzen> nik90, potentially but don't think it sortof works out like tht because Victor has 2 in the end
[21:29] <nik90> ahayzen: hmm weird
[21:29] <ahayzen> nik90, oh no playlists is probably the second
[21:29] <ahayzen> nik90, but tht says PageStack in the spec ;)
[21:30] <nik90> ahayzen: exactly
[21:30] <nik90> ahayzen: sheets arenot recommended by the sdk yet since they need a huge design revamp first
[21:30] <nik90> they look ugly
[21:30] <ahayzen> nik90, +1
[21:30]  * ahayzen hugs pages
[21:31] <nik90> actually I hug pages and pagestack
[21:31] <nik90> pagestack is a genius
[21:31] <nik90> it load/unloads dynamically
[21:31] <nik90> ahayzen: are there any design meetings you guys might have?
[21:32] <nik90> I would love it join them to provide the "No sheet" reasoning :)
[21:32] <ahayzen> nik90, we used to have weekly design meetings last cycle
[21:32] <nik90> me too
[21:32] <ahayzen> nik90, but design don't really have time anymore and i think all the specs we have are basically considered the final phone designs
[21:32] <ahayzen> nik90, but idk just the impression i've got
[21:32] <nik90> okay
[21:32] <ahayzen> nik90, u know of the other specs?
[21:33] <nik90> I have 2 Music App Spec links
[21:33] <nik90> a google presentation and a document
[21:33] <ahayzen> nik90, yep :)
[21:34] <ahayzen> nik90, oh there maybe another...
[21:34] <nik90> another sheet or spec?
[21:34]  * nik90 hopes the latter
[21:34] <ahayzen> nik90, spec
[21:34] <ahayzen> lol
[21:34] <ahayzen> nik90, have u got the UDS session spec?
[21:34] <nik90> ahayzen: no
[21:35] <nik90> ahayzen: https://docs.google.com/presentation/d/1D0lDUSp7CZv7UwjMDUMdqHWbnR_N9L6ovgt1PPO8CmE/edit#slide=id.g117c27a6e_018?
[21:35] <ahayzen> nik90, so there is the UX Spec, UX concept (from UDS) and the 'Music Player Specification'
[21:35] <ahayzen> nik90, https://docs.google.com/presentation/d/1nc7RTAD5ViEAdc3VsZyN-lkmG-AnO664uV-5wXZoZZg/edit#slide=id.p
[21:35] <nik90> okay
[21:36] <nik90> ahayzen: I saw the UX Spec and the Music Player Specification
[21:36] <ahayzen> nik90, and this https://docs.google.com/presentation/d/1D0lDUSp7CZv7UwjMDUMdqHWbnR_N9L6ovgt1PPO8CmE/edit#slide=id.g117c27a6e_018
[21:37] <ahayzen> nik90, think it is basically a summary of the UX Spec...IIRC there is a video somewhere
[21:37] <nik90> ahayzen: do you see this slide at https://docs.google.com/presentation/d/1D0lDUSp7CZv7UwjMDUMdqHWbnR_N9L6ovgt1PPO8CmE/edit#slide=id.ge29b68e7_0149
[21:37] <nik90> it shows a different toolbar
[21:37] <nik90> did that get revised?
[21:37] <ahayzen> nik90, http://summit.ubuntu.com/uds-1308/meeting/21922/appdev-1308-design-review-music/
[21:38] <ahayzen> nik90, tht was pushed back due to a) complexity b) those buttons won't actually do anything at the moment anyway
[21:39] <nik90> ah okay
[21:39] <nik90> good decision :)
[21:39] <nik90> the current toolbar is just freaking amazing!
[21:39] <ahayzen> nik90, thanks only slightly custom ;)
[21:40] <nik90> ahayzen: oh btw I cant run music-app on the phone through qtcreator
[21:40] <ahayzen> nik90, once we move to pagestacks we can get rid of tht stupid gap on the left on the 'compact' toolbar
[21:40] <ahayzen> nik90, yeah i know it is a *nightmare* to even run the music-app on the phone :/
[21:40] <ahayzen> nik90, wht error do u get?
[21:40] <nik90> ahayzen: I get file:///home/phablet/dev_tmp/convergence-alt-toolbar-show/music-app.qml:26 module "org.nemomobile.grilo" is not installed
[21:41] <ahayzen> nik90, yep same which is obviously not true because the app installed on it runs :P
[21:41] <nik90> exactly1
[21:41] <nik90> !
[21:41] <nik90> any tricks up your sleeve to get it working?
[21:41] <ahayzen> nik90, and when i use the autopilot automated testing script tht popey gave me tht runs any branch
[21:42] <ahayzen> nik90, go back to ~3-4 rev before Mir was introduced... or ~November when it magically worked for a bit
[21:43] <ahayzen> nik90, i've tried to manually get it in many times but haven't had much success lately
[21:43] <nik90> ahayzen: you mean like image #70 something? oh god no :/
[21:43] <ahayzen> nik90, yh pahahah
[21:43] <ahayzen> nik90, u have the autopilot testing script?
[21:44] <nik90> ahayzen: I came to know of its existence only today :)
[21:44] <nik90> popey told me during the meeting about the script
[21:44] <ahayzen> nik90, i tried to hack tht to let me pick a branch to install and run on the device
[21:44] <nik90> ah so you install the music-app on ur phone everytime you want to test it
[21:45] <ahayzen> nik90, no tht doesn't work, just get a white screen
[21:46] <ahayzen> nik90, i haven't *recently* been able to get the app running on the phone
[21:46] <ahayzen> nik90, i'm hoping it is due to app confinement and when we get rid of Grilo it'll all work :)
[21:47] <nik90> ahayzen: okay...so how do you gurantee when it goes on store, it will open correctly?
[21:47] <nik90> u r getting rid of Grilo?
[21:47] <ahayzen> nik90, autopilot testing...and somehow victor used to get his to work
[21:48] <nik90> okay
[21:48] <ahayzen> nik90, if u get it working let me know lol i would greatly appreciate it :)
[21:49] <nik90> ahayzen: alrite can you organize a hangout or somethig with victor? I really want to discuss with him and you about using pages instead of sheets (with his new MP).
[21:49] <nik90> ahayzen: ofc. But if you couldn't then I doubt I can considering I haven't much experiecne with qml plugins like grilo
[21:50] <ahayzen> nik90, probably, he is best contactable via email although the timezones cause havoc for tht sortof thing lol
[21:50] <nik90> ahayzen: where do you live?
[21:50] <nik90> and where does victor live?
[21:50] <nik90> I noticed he replied to my MP at 05:00 AM
[21:50] <nik90> (my time)
[21:51] <ahayzen> nik90, me UTC, Victor UTC-6, Daniel UTC+1
[21:51] <nik90> ah UTC-6....no wonder
[21:51] <ahayzen> nik90, but when i go back to uni i'm usually up late ;)
[21:52] <nik90> ahayzen: dude I was coding yesterday on the music MP until 04:00 AM :P
[21:53] <ahayzen> nik90, 4AM easy :P.... i got up to 5/6AM consistently last semester lol
[21:53] <ahayzen> nik90, but i should probably reel tht back in lol
[21:53] <nik90> rofl
[21:54] <ahayzen> nik90, but back on topic i suspect the issues with the app running on device are click/confinement related
[21:55] <nik90> ahayzen: I suppose
[21:55] <ahayzen> nik90, which i have very limited knowledge of
[21:55] <nik90> yeah me too
[21:55] <nik90> haven't the single clue about how click packages work yet
[21:56] <ahayzen> nik90, wonder who we could talk to about this?
[21:57] <ahayzen> nik90, i've tried just randomly asking for help before but to no avail
[21:57] <nik90> ahayzen: I heard sergio is really good with click packages since he is the one who updates the core app click packages...
[21:57] <nik90> ahayzen: but I think we should talk to popey before that..
[21:57] <ahayzen> nik90, yeah probably
[21:57] <nik90> he can point to the right person immediately
[21:57]  * popey waves
[21:57] <popey> wassup?
[21:58] <ahayzen> nik90, IIRC victor used to just manually overwrite the files tht have changed
[21:58] <ahayzen> nik90, but tht only used to randomly work for me
[21:58] <ahayzen> popey, running the development builds of the music-app on device
[21:59] <nik90> ahayzen: that is too messy
[21:59] <ahayzen> popey, if u try and run through the QtCreator u get file:///home/phablet/dev_tmp/convergence-alt-toolbar-show/music-app.qml:26 module "org.nemomobile.grilo" is not installed
[21:59] <nik90> popey: we are having trouble running music-app on phone through qtcreator to test it
[21:59] <nik90> we get the error message ^^'
[21:59] <ahayzen> popey, when i've tried to manually install i usually get a blank white screen
[21:59] <ahayzen> popey, i think u tried to help me before by looking through the upstart logs but we didnt get far
[22:00] <popey> ah
[22:00] <popey> so I have recently been pointing people at a funky script mzanetti wrote to do that
[22:01] <popey> https://bazaar.launchpad.net/~reminders-app-dev/reminders-app/trunk/view/head:/run_on_ubuntu_touch.sh
[22:01] <popey> that script
[22:01] <popey> would need fiddling for music app but not much
[22:02] <ahayzen> popey, thanks
[22:02]  * ahayzen tries the script
[22:02]  * nik90 looks eagerly
[22:04] <ahayzen> popey, so do we put it in the same dir as the app we want to run or pass arguments ?
[22:05] <popey> i pass no arguments
[22:05] <popey> i just run it with -s to setup
[22:05] <ahayzen> popey, where is it pulling the code from?
[22:06] <popey> its in the root of the application directory
[22:06]  * ahayzen squints at bash script
[22:06] <popey> bzr branch lp:reminders-app
[22:06] <popey> to test it
[22:06] <popey> run it first with -s
[22:06] <popey> then once setup is done, run it again and it runs the app
[22:07] <ahayzen> popey, bash: cd: music-app/builddir/src/app/: No such file or directory
[22:08] <ahayzen> popey, ah their code layout is quite different
[22:10] <popey> ?ok
[22:10] <popey> the other option is balloons's magic script
[22:10] <ahayzen> more magic scripts :)
[22:10]  * ahayzen wonders how many magic scripts popey has along with subdomains
[22:11] <popey> mnuhahah
[22:11] <nik90> ahayzen: looking at that script, we need to change the build() and build_click_package() functions
[22:11] <ahayzen> nik90, yeah there is quite a bit to change :/
[22:11] <nik90> +1
[22:14] <popey> ok
[22:14] <popey> is the balloons script not useful?
[22:14] <popey> http://paste.ubuntu.com/6721815/
[22:15] <popey> ./test.sh lp:foo/bar/ music_app
[22:15] <popey> which should install music app then start tests, actually if you miss off the "music_app" off the end it will install it and then fail to start tests
[22:15] <popey> getting you what you want
[22:16] <ahayzen> popey, is tht the autopilot testing one u gave me before?
[22:16] <popey> yes
[22:16] <ahayzen> popey, tht was very useful for autopilot testing :)...but i tried to make it only install and run but didn't know the cmds to run :/
[22:17] <popey> you should not need to
[22:17] <popey> it will replace the current version, just launch as normal from the icon on phone
[22:17] <balloons> yes, it builds a click package and sends to the phone
[22:17] <ahayzen> popey, ooo ok i'll try it :)
[22:17] <ahayzen> balloons, o/
[22:17] <balloons> if you peek at the script a bit, you can manipulate it to your hearts content
[22:18]  * ahayzen wonders if u could point a local bzr location at it
[22:18] <balloons> the tests are run from /home/phablet/autopilot
[22:18] <balloons> in theory, yes you could.. but it's simple enough to commit
[22:18] <balloons> I should say more than theory, hah.. you could tweak it to do so.. use a location, instead of an lp location
[22:21] <ahayzen> ok so i just did $ ./testing.sh lp:~vthompson/music-app/use-sheet-pattern
[22:21] <ahayzen> it install the app and failed to run the tests
[22:21] <ahayzen> now when i try and run the app from the phone i just have a white screen
[22:22] <balloons> ahayzen, if it fails or you simply want to re-run, just use phablet-test-run to re-run
[22:23] <ahayzen> balloons, i wanted to run the app so i can test myself
[22:23] <balloons> it's already installed so you can re-run without running the whole script again
[22:24] <ahayzen> balloons, i ran the script then tried to run from the dash... looking at the log of upstart ' Manifest 'com.ubuntu.music' version '1.1.299' doesn't match AppID version '1.1.291''
[22:24] <popey> have a look in /home/phablet/.cache/upstart.... for a recent log file
[22:24] <ahayzen> and 'WARNING **: Desktop file unable to be found'
[22:25] <popey> ☹
[22:33] <ahayzen> ...damn crashed unity
[22:34] <ahayzen> popey, balloons ok so running ./testing.sh lp:music-app then letting unity crash and reset has allowed me to run the app again
[22:35] <balloons> yea, once it's copied.. you can reboot the device, re-run the test, whatever
[22:36] <ahayzen> balloons, so why didn't it run Victor's branch was the manifest incorrect?
[22:36] <ahayzen> balloons, basically we currently have no easy way of running custom builds of the music-app on device so are searching for a solution
[22:36] <balloons> ahayzen, sorry I'm not following closely :-) Dealing with calendar tests atm :p
[22:36] <balloons> ahayzen, yes, I understand
[22:37] <ahayzen> balloons, aha no problem ;)
[22:37] <balloons> the easiest way RIGHT now is the script.
[22:37] <balloons> what I'm working on is modifying phablet-test-run to do this
[22:37] <balloons> so in theory.. I want you to run local, run lp branch, and run on emulator or device
[22:37] <ahayzen> balloons, it is a shame running from QtCreator doesn't work :/
[22:38] <balloons> nik90 mentioned this desire too. I don't play in qtcreator much :-)
[22:40] <balloons> so, ahayzen does your current options make sense? did it work ok/
[22:41] <ahayzen> balloons, i'm gonna try the script on another branch see if i can get it to do something
[23:04] <ahayzen> nik90, u had any luck running the app?
[23:33] <nik90> ahayzen: no I tried for a while then started working on other things
[23:33] <ahayzen> nik90, haha same i need to spend some time properly investigating :/
[23:34] <nik90> ahayzen: hey do you know how to copy files from the device to the laptop?
[23:34] <ahayzen> nik90, i do...hang on
[23:35] <ahayzen> nik90, oh device to laptop?
[23:35] <nik90> ahayzen: yes...a file outside the user directory
[23:35] <nik90> so I dont see it in the nautilus folder in nexus 4 device
[23:35] <ahayzen> nik90, adb pull <remote> [<local>]  - copy file/dir from device
[23:37] <nik90> ahayzen: perfect. thnx
[23:37] <ahayzen> nik90, np
[23:40] <ahayzen> nik90, moving the mediaplayer out is starting to work quite nicely i just hope i'll get it approved :)
[23:45] <nik90> ahayzen: nice