[05:58] <kivi> hi all
[06:43] <kivi> i'm trying to build a self contained snappy package which has zsh. It requires ncurses; now should I download Ncurses, and extract into my zsh directory? If yes, what folder should I put it in?
[06:43] <kivi> should I create a folder called "dependencies" or "src" [already exists], and put it in there?
[06:43] <kivi> or am I doing this all wrong?
[06:44] <kivi> actually I'll ask ubuntu packaging.
[07:03] <dholbach> good morning
[07:04] <kivi> dholbach, morning
[07:04] <kivi> dholbach, because click packages/ snaps are statically linked, do I need to provide every single dependency, or should I be relying on some dependencies from the system?
[07:05] <kivi> does that make sense? I'm just wading into this.
[07:07] <dholbach> hey kivi
[07:08] <dholbach> kivi, you don't necessarily need to link statically - you could also bundle libraries which are necessary and set someting like LD_LIBRARY_PATH (or something) if that makes things easier
[07:09] <dholbach> clicks/snapps can only require a framework to be installed, not packages as in the .deb based world
[07:09] <dholbach> I don't know if there's a list of packages that are guaranteed to be in the snappy base...
[07:10] <kivi> dholbach, the question for me is knowing what I can and can not use. Like for example; I can't use an installed python interpreter, so I need to bundle one myself, right?
[07:10] <dholbach> yes
[07:11] <dholbach> if you log into your phone (or emulator) you can try it out
[07:11] <dholbach> phablet@ubuntu-phablet:~$ python
[07:11] <dholbach> -bash: python: command not found
[07:11] <dholbach> phablet@ubuntu-phablet:~$
[07:11] <dholbach> on the phone right now you can even use 'dpkg -l'
[07:11] <dholbach> on a snappy based system that won't exist anymore
[07:12] <kivi> dholbach, okay, but if I want to be on the safe side, I should bundle all the dependencies myself? Or will that come at a huge cost?
[07:14] <dholbach> it'll be a bigger download for your users
[07:15] <kivi> dholbach, but performance will still be fine?
[07:17] <dholbach> yep
[07:19] <kivi> dholbach, okay thanks!
[07:20] <kivi> Once I get this down, I think I'll make a few youtube tutorials on this.
[07:32] <dholbach> kivi, excellent - thanks a lot! :)
[07:40] <dholbach> dpm, I think we wanted to talk about https://strawpoll.me/4482403/r at some stage
[07:57] <dpm> dholbach, didn't we make a decision already to use ubuntu-app-devel@?
[08:00] <dholbach> dpm, I can't remember - I'm happy to update developer.u.c and let folks on both lists know
[08:02] <dholbach> ah developer.u.c is already up to date
[08:05] <dpm> ok, cool
[08:38] <dholbach> mhall119, do you have any deployment news? :)
[10:55] <rpadovani> popey, mzanetti I would love a feedback by you on bug #1478094
[10:56] <mzanetti> rpadovani, what kind of feedback?
[10:56] <mzanetti> oh, I see
[10:56] <mzanetti> hmm
[10:56] <rpadovani> mzanetti, wait for an upstream solution or disable predictive text?
[10:56] <mzanetti> rpadovani, well, there is an upstream solution
[10:57] <rpadovani> really?  I wasn't aware of
[10:58] <mzanetti> rpadovani, https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.TextField/
[10:58] <Elleo> rpadovani: it sounds like you're checking for text before enabled the Okay button, you can fix that by checking for text or the text field's inputMethodComposing being true
[10:58] <mzanetti> rpadovani, inputMethodComposing
[11:01] <rpadovani> mzanetti, Elleo thanks :-)
[12:26] <dholbach> dpm, did mhall119 say anything about deploying developer.u.c soon?
[12:26] <dholbach> or do we just need to wait for IS to take care of the ticket?
[12:36] <dpm> dholbach, as far as I understood it from the call with Mike, we're now just waiting for IS to work on that ticket
[12:37] <dpm> dholbach, RT #83291
[12:37] <dpm> I'll have to see if they need some prodding
[12:38] <dholbach> ok
[12:38] <dholbach> thanks
[12:40] <dpm> I can't see the current status atm, as I can't log into the RT system for some reason
[12:40] <dholbach> it appears unchanged
[12:40] <dholbach> it's "size estimate: L"
[12:40] <dholbach> so might take a bit longer
[12:41] <dpm> yeah, I could now log in
[13:00] <dholbach> dpm, the ticket will need escalation
 dholbach: nope nothing is blocking it other than lots of tickets with higher priority
[13:09] <didrocks> zsombi: small question about ListItems: I'm using the new ones from 1.2 (with leading/trailingActions), I was wondering if it can be combined with the Expandable one in any blessed way?
[13:10] <dpm> dholbach, ok, will work on escalating it, thanks for following up
[13:10] <zsombi> didrocks: nopez, I'm working on expansion
[13:10] <dholbach> dpm, thank you!
[13:11] <didrocks> zsombi: I guess a current solution would be (if no leading/trailing actions are shown) to listen to pressAndHold and change the height?
[14:09] <karni> "If the ListItem contains a component which contains an active MouseArea, the clicked signal will be supressed when clicked over this area." -- even if the contained MouseArea is smaller? I'm having an issue where the ListItem's clicked signal is not emitted (I have MouseAreas within, but smaller)
[14:09] <karni> Any ideas?
[14:23] <popey> JamesTait: any news on whether we can get rid of all the clutter in https://myapps.developer.ubuntu.com/dev/click-apps/reviewer/ ?
[14:25] <JamesTait> popey, it's still being worked on.
[14:26] <popey> ok
[18:51] <ahayzen> popey, is there a maximum length to the changelog/what's new field in the store? I thought you were going to have to cut the list of changes we had this time ;-)
[19:04] <kalikiana> if only those were even visible in the ui
[19:04] <kalikiana> very time I update I briefly see what apps there are, then they're gone, and if by any chance I remember what they were I'll have to dig it up in uappexplorer
[19:05] <ahayzen> kalikiana, you can see the what's new when you press'n'hold the app in the app scope? if thats what you mean?
[19:07] <kalikiana> hmmm press and hold doesn't seem to work anymore, it's loading forever
[19:07] <ahayzen> kalikiana, yeah its really slow at loading, but if it does you can see the changelog/reviews there
[19:08] <kalikiana> oh, it can't cope with my network for some reason trying to login to a coffee shop that's two streets down and totally out of range
[19:08] <ahayzen> hah!
[19:09] <kalikiana> I would think an installed app should somehow be... installed
[19:09] <kalikiana> yet it only works with wlan
[19:09] <ahayzen> yeah i guess half of the information is stored locally
[19:09] <ahayzen> but like the reviews etc is probably remote
[19:09] <kalikiana> indeed the changelog is there
[19:09] <ahayzen> \o/
[19:10] <kalikiana> so I guess if I can write down all apps before hitting "update" and spend 10 seconds each, I can hunt down the changes
[19:10] <ahayzen> yeah lol
[19:10] <kalikiana> sadly I'm not seriously going to
[19:11] <kalikiana> so I will stick to uappexplorer's "recently changed" view
[19:13] <kalikiana> thanks anyway for the tip
[19:14] <ahayzen> np
[19:17] <mcphail> having a changelog on the update screen would be a great boon
[19:21] <DanChapman> wow now that's an interesting bug https://bugs.launchpad.net/dekko/+bug/1479464
[20:12] <mcphail> DanChapman: all I can say is doing things in the _other_ direction (using Dekko on the desktop and connecting via USB/phone) works well
[20:45] <DanChapman> mcphail: yeah i'm not sure what the problem is tbh. Dekko doesn't do anything _special_ here. Cool to know it works the other way round though.:-)
[23:41] <DF_> hi
[23:41] <DF_> some one here??