[02:04] <Israel> I am having a bit of an issue with QML.  tools: ToolbarItems  keeps giving me an error when I try to run my program. "Cannot assign to non-existent property "tools""  though I import Ubuntu.Components.Popups 0.1
[02:05] <Israel> Does Ubuntu.Components.Popups 0.1 conflict with another, such as Ubuntu.Components.ListItems 0.1 ??
[02:17] <Israel> is this a bug?  does anyone know?
[02:24] <AskUbuntu> How do I make a random amount of an elements in QML | http://askubuntu.com/q/315678
[03:02] <Denubis> Is this the appropriate channel to discuss different packaging strategies for part of an app we're planning on running on an ubuntu laptop?
[03:02] <Denubis> or is this more for the process of developing the thing itself?
[03:17] <tsimpson> Denubis: #ubuntu-packaging is more for packaging, though this and that channel are both rather quiet. you may find http://developer.ubuntu.com/packaging/html/ useful
[03:40] <Denubis> tsimpson, I'm more interested in discussing the different approaches, the link you gave is quite useful in the more pragmatic howto sense
[06:27] <dpm> good morning all
[06:28] <AskUbuntu> Design standard for "About" and "Options" | http://askubuntu.com/q/315729
[06:39] <gusch> mhall119: ping
[06:40] <AskUbuntu> Clickable emails in Label | http://askubuntu.com/q/315733
[06:42] <dholbach> good morning
[06:45] <xzcvczx> evening actually :)
[07:26] <AskUbuntu> get the ubuntu sdk preview | http://askubuntu.com/q/315751
[07:50] <oSoMoN> hey gusch, would you have some time to review https://code.launchpad.net/~osomon/webbrowser-app/toolbar-buttons/+merge/172604 today?
[07:50] <gusch> oSoMoN: sure - I'm on it ...
[07:50] <oSoMoN> thanks!
[07:57] <gusch> oSoMoN: the icons are bigger now, an vertical centered
[07:58] <gusch> oSoMoN: the problem is, for "Tabs" the text and icon overlap slightly
[07:58] <oSoMoN> gusch: interesting, I haven’t seen that, are you testing on desktop or phone?
[07:58] <gusch> oSoMoN: on the desktop
[07:59] <oSoMoN> gusch: let me test again then
[08:00] <gusch> oSoMoN: I updated UITK today
[08:00] <oSoMoN> gusch: ah, I haven’t yet (doing it now), might be the reason of the difference
[08:01] <gusch> oSoMoN: but I'd say that is a bug in UITK
[08:02] <oSoMoN> gusch: it was working well (looking exactly the same as standard toolbar buttons) with yesterday’s uitk
[08:02] <gusch> oSoMoN: hmmm - or you have to use (anchor?) the ToolbarButton different
[08:04] <gusch> oSoMoN: gallery looks fine with the new UITK
[08:10] <oSoMoN> gusch: I updated to the latest uitk, and I’m not seeing the issue you’re describing, in fact I’m running the browser (my branch) and the gallery (latest trunk), and the size and appearance of the toolbar buttons is exactly the same
[08:10] <oSoMoN> gusch: can you take a screenshot of the issue and send it my way?
[08:10] <gusch> oSoMoN: ok
[08:12] <gusch> oSoMoN: oh - mixed that up - the old one looks wrong
[08:14] <gusch> oSoMoN: ok - so I'll approve
[08:15] <gusch> oSoMoN: approved - sorry for the fuzz
[08:21] <oSoMoN> gusch: no worries, thanks for the review
[08:39] <JamesTait> Good morning all, happy Compliment Your Mirror Day! :-D
[09:12] <dpm> hi oSoMoN, I hope you had a nice holiday and welcome back! :) - quick question: I've noticed that after the work to get desktop files for the core/system apps internationalized, they still don't appear translated in the dash. I'm not sure if it's a regression or if they never appeared translated, do you have any ideas why the desktop file translations might not be loaded?
[09:13] <oSoMoN> dpm: hey, thanks :)
[09:14] <oSoMoN> dpm: not sure about unity8, it might be that it doesn’t use the correct mechanism to get the translated names
[09:14] <oSoMoN> dpm: when I tested on my desktop though, it was
[09:14] <oSoMoN> working
[09:14] <dpm> oSoMoN, how did you do the testing on your desktop?
[09:15] <oSoMoN> dpm: I installed the package from the ppa on the desktop and searched for the app in the dash
[09:16] <dpm> oSoMoN, yeah, that works. I can confirm that, but on the device they're untranslated.
[09:16] <dpm> I'll file a bug against unity
[09:22] <seb128> hey toolkit guys
[09:23] <seb128> is there a magic to tell a ListView "height: whatever is needed to include the ListItem stacked in the list"?
[09:27] <nik90> seb128: not a toolkit guy, but cant you use height: ChildRect.height or something?
[09:27] <nik90> I mean ChildrenRect
[09:29] <seb128> nik90, that seems to work, thanks!
[09:29] <seb128> qml is weird, I wonder why those are not default
[09:29] <seb128> it's like columns
[09:29] <nik90> seb128: yes
[09:30] <seb128> when using qml you keep running into stuff not doing what you want because their default size is null
[09:30] <seb128> rather than being the one needed for the things they include
[09:31] <nik90> seb128: I think qt quick and qml is still picking up and is a bit new.
[09:33] <seb128> right
[09:37] <seb128> ok, next question :p
[09:38] <seb128> is there a way to have an icon: of a ListItem do "look in the theme if that's a name, use the path if that's a path"?
[09:38] <seb128> e.g I want to use "icon: desktop.Icon" where desktop.Icon is the Icon=... from /usr/share/applications/<name>.desktop
[09:39] <seb128> those are sometime a theme icon, sometime a filepath
[09:43] <nik90> seb128: sry no experience with that. I am still trying to figure that myself.
[09:43] <nik90> seb128: although how do they do it in the current .desktop files?
[09:52] <seb128> nik90, "they"?
[09:52] <seb128> nik90, well, desktop files can contain an icon name or a path to an icon, gtk handles that fine, not sure what qt does which is what I was asking
[09:52] <seb128> "icon: icon" works for a themed icon
[09:53] <seb128> but if you have a filename you need "icon: Qt.resolvedUrl(icon)" it seems
[09:54] <nik90> seb128: I use Qt.resolvedUrl(icon) for the clock-app
[09:55] <nik90> seb128: However there I give it a relative path. But am not sure what happens when the theme is changed
[09:55] <seb128> where icon is a name from an icon in the theme or a path to a file?
[09:55] <nik90> path to a file
[09:55] <seb128> k, that makes sense
[10:32] <seb128> nik90, just for info, using "icon: "image://gicon/" + iconname" seems to do the trick
[10:38] <nik90> seb128: thnx. Will keep that in mind
[12:47] <gema> boiko: ping
[12:47] <boiko> gema: pong
[12:47] <gema> boiko: remember the ssh command we discussed to make the phone send a call to a given number?
[12:47] <gema> boiko: I cannot find it in my logs
[12:49] <boiko> gema: there is a dbus command, but it won't call directly, it will only fill the dialer page with the number and wait for the call button to be pressed
[12:49] <gema> boiko: I remember we discussed a way to ssh into the phone and make it call
[12:49] <gema> boiko: maybe calling the app from the command line?
[12:50] <gema> boiko: I haven't tried it , I was going to, but cannot find the line
[12:51] <boiko> gema: wasn't that for accepting incoming calls? for that there is a dbus command (omer asked me to add that)
[12:51] <gema> boiko: that's another thing we need indeed
[12:51] <gema> boiko: this is to be able to control the phone at the other end from the testing phone
[12:51] <gema> and make a call to the testing phone initiating it from outside
[12:52] <boiko> gema: ah ok, there is the ofono phone simulator, but as far as I know it is not fully controllable from the command line, let me check
[12:52] <gema> boiko: thanks
[12:53] <boiko> gema: let me check what can be done from the command line, just a minute
[12:53] <gema> boiko: thanks a lot
[12:55] <oSoMoN> Kaleo: hey, any idea
[12:55] <oSoMoN> Kaleo: hey, any idea what could cause bug #1197293
[12:55] <ubot2`> Launchpad bug 1197293 in Ubuntu UI Toolkit "ReferenceError: UbuntuColors is not defined" [Undecided,New] https://launchpad.net/bugs/1197293
[12:55] <oSoMoN> ?
[13:00] <Kaleo> oSoMoN: looking
[13:01] <oSoMoN> thanks
[13:03] <seb128> could somebody knowing qml help us and review https://code.launchpad.net/~laney/ubuntu-system-settings/background-welcome-image-accountsservice/+merge/172595 ?
[13:04] <seb128> (that's for system settings, most of us working on it are new to qml and that's the first "plugin" we use ... it would be good if somebody who knows those stuff better could check things are done the right way)
[13:04] <seb128> (that's likely going to used as base/copied in other panels)
[13:04] <seb128> oSoMoN, Kaleo, ...: ^ if you have some spare cycle, it's not a big diff to review ... ;-)
[13:05] <seb128> Laney, ^ fyi
[13:06] <Laney> cool
[13:06] <oSoMoN> seb128: I’ll have a look later today
[13:06] <seb128> oSoMoN, thanks!
[13:08] <Kaleo> seb128: camel case
[13:08] <Kaleo> seb128: (just going through it quickly, that struck me, names should be camelcase)
[13:08] <boiko> gema: so, once you get ofono-phonesim running (omer was working on that) you can follow the instructions
[13:08] <boiko> gema: here: https://kernel.googlesource.com/pub/scm/network/ofono/phonesim/+/c94e6c0c64dd10da2a297d37336653ef707be49a/doc/scriptable.txt
[13:08] <gema> boiko: excellent thanks
[13:09] <boiko> gema: but that's not real phone calls, it is using the modem simulator from ofono
[13:09] <gema> uhmmm, that;s not good enough
[13:09] <gema> I need to make a real phone call
[13:09] <boiko> gema: for real calls I don't know a way to do that, cause you have to call from another phone, and that I don't know how to do
[13:09] <Kaleo> seb128: use property bindings: instead of "onBackgroundFileChanged: testWelcomeImage.source = backgroundPanel.backgroundFile"; do "source: backgroundPanel.backgroundFile"
[13:10] <seb128> Laney, ^
[13:10] <gema> boiko: ack, no worries
[13:10] <boiko> gema: from the app you can do that easily using autopilot (omer already created code for that)
[13:11] <gema> boiko: I'd like not to depend on the app
[13:11] <gema> for the testing
[13:11] <boiko> gema: but from the other end (to simulate an incoming call), I don't know how to do
[13:11] <gema> boiko: no worries we'll write a little C program if needed be
[13:11] <gema> I thought there was one already , will ping rsalvetti again
[13:11] <Kaleo> Laney: seb128: QString backgroundFile(); is protected but should be public
[13:12] <Laney> that came from the template
[13:12] <Kaleo> Laney: seb128: there is some qDebug statements lying around and the qdebug import unneeded
[13:12] <boiko> gema: so if the idea is to use two ubuntu touch phones, then there are some tricks that we can do
[13:12] <Laney> how do I do the property binding thing while keeping the fallback as default?
[13:12] <gema> boiko: the idea is to use two, one of them will be quite stable
[13:13] <gema> able to make/receive calls and send / receive smss
[13:13] <gema> but I don't want to depend on the UI apps to do that
[13:13] <Kaleo> Laney: in the constructor you do background_file = get_background_file(); twice
[13:13] <gema> just a command line that we can send through ssh to that phone
[13:13] <gema> to get it going
[13:13] <gema> becuse the phone under test is the other one
[13:13] <Kaleo> Laney: you could even do get_background_file() lazily in the backgroundFile() getter; that would speed up startup time
[13:13] <gema> that one would only be test infrastructure
[13:13] <Kaleo> Laney: let me see about the binding
[13:14] <boiko> gema: in that case there is something you can do to make a call, let me get the command here
[13:14] <Laney> Kaleo: Will it be cached by qml?
[13:14] <gema> boiko: thanks
[13:14] <boiko> gema: (sorry, I didn't realize you were going to use two ubuntu-touch phones)
[13:14] <gema> boiko: ok
[13:14] <Laney> The thought of doing it in the ctor was to avoid dbus roundtrips
[13:14] <Kaleo> Laney: no
[13:15] <Kaleo> Laney: the background() function will be called everytime you type object.background in QML
[13:15] <Kaleo> Laney: to answer your question/issues in the description of the MR:
[13:15] <Laney> then wouldn't it be better to have that cost once at startup?
[13:15] <Kaleo> Laney: 1. it's right
[13:15] <Kaleo> Laney: no
[13:15] <Kaleo> Laney: it's still a one time cost
[13:16] <Kaleo> Laney: if you keep storing the result in your private member variable
[13:16] <Kaleo> Laney: and not call the dbus function every time
[13:16] <Kaleo> Laney: 2. ubuntu-system-settings and not libsystemsettings1: are those package names?
[13:16] <Laney> yes
[13:16] <Kaleo> Laney: 3. your way is better
[13:17] <kenvandine> Kaleo, yes those are package names
[13:18] <Kaleo> Laney: 4. that's alright
[13:18] <mhall119> gusch: pong
[13:18] <Kaleo> Laney: 2. we have convention names for those
[13:18] <Kaleo> Laney: qtdeclarative5-qtfeedback-plugin qtdeclarative5-localstorage-plugin qtdeclarative5-ubuntu-ui-toolkit-plugin
[13:18] <Kaleo> Laney: etc.
[13:19] <Kaleo> Laney: but hang on
[13:19] <Laney> -system-settings-plugins?
[13:19] <gusch> mhall119: I tried to merge to music-app
[13:19] <Kaleo> Laney: I would not separate the plugin into a separate debian package at all
[13:19] <Kaleo> Laney: unless you intend other apps to use it
[13:19] <Laney> right
[13:19] <Laney> not really
[13:19] <Kaleo> Laney: so no
[13:19] <gusch> mhall119: lanuchpad says it's merged, but it isn't
[13:20] <Kaleo> Laney: 5. I don't know yet
[13:21] <Laney> Kaleo: so the variable name convention is camelCase for all variables?
[13:21] <gusch> mhall119: any idea why?
[13:21] <Kaleo> Laney: yes
[13:21]  * Laney discovers Qt Creator has a refactoring tool for this
[13:21] <Laney> :D
[13:22] <mhall119> gusch: no, let me look though
[13:22] <gusch> mhall119: https://code.launchpad.net/~schwann/music-app/music-fix-warnings/+merge/172573
[13:22] <Kaleo> Laney: and member variables prefixed with m_
[13:22] <Kaleo> Laney: about the binding, you are right
[13:22] <gusch> mhall119: and https://code.launchpad.net/~schwann/music-app/music-declarative-duration/+merge/172620
[13:22] <Kaleo> Laney: no use for one
[13:22] <Laney> cool
[13:22] <Laney> Kaleo: Give me 5 minutes to do your fixes
[13:22] <Kaleo> Laney: you can take a look at the following file from the toolkit
[13:23] <gusch> mhall119: oh - maybe dpm fixed that already?
[13:23] <Kaleo> Laney: for something similar: modules/Ubuntu/Components/ListItems/ImageWithFallback.qml
[13:23] <Laney> ok
[13:23] <gusch> mhall119: oh dpm did - thx
[13:23] <mhall119> ok,cool
[13:23] <Laney> ah interesting
[13:23] <mhall119> yeah, I'm seeing them in trunk
[13:24] <dpm> gusch, np, I just noticed that Jenkins hadn't kicked in because the MP hadn't been top-approved and approved it (it was manually marked as merged)
[13:31] <Kaleo> oSoMoN: that's beyond me so far
[13:33] <oSoMoN> Kaleo: ok, thanks, I’ll keep digging
[13:34] <Kaleo> oSoMoN: try to call the plugin with something that does not start with Ubuntu.Components
[13:36] <oSoMoN> Kaleo: do you mean renaming it?
[13:36] <Kaleo> oSoMoN: yes
[13:36] <Kaleo> oSoMoN: that's the only change that Isee could be relate
[13:36] <Kaleo> d
[13:37] <oSoMoN> yes, that makes sense
[13:37] <Kaleo> oSoMoN: When you have eliminated the impossible, whatever remains, however improbable, must be the truth.
[13:39] <Kaleo> oSoMoN: something is odd
[13:39] <Kaleo> oSoMoN: you did not put the browser plugin under Ubuntu/Components/Extras/Browser
[13:40] <Kaleo> oSoMoN: forget it, my bad
[13:40] <Kaleo> oSoMoN: was looking at the wrong tree :)
[13:40] <oSoMoN> the tree that’s hiding the forest? ;)
[13:42] <Kaleo> oSoMoN: yes, I'm starting to have a good idea of what's going on
[13:42] <Kaleo> oSoMoN: I doubt it has anything to do with the naming
[13:43] <Kaleo> oSoMoN: I had not noticed that message before "QQmlComponent: Component is not ready"
[13:43] <oSoMoN> Kaleo: good, I don’t feel like renaming again
[13:43] <oSoMoN> ah, me neither, good catch
[13:51] <Kaleo> oSoMoN: found it!
[13:51] <Kaleo> oSoMoN: createQmlObject  QUrl( "file:///home/kaleo/Projects/apps/webbrowser-app/src/Ubuntu/Components/Colors/UbuntuColors.qml" )
[13:51] <Kaleo> that's not gonna work :)
[13:51] <oSoMoN> Kaleo: where in the code is that?
[13:52] <Kaleo> oSoMoN: the toolkit
[13:52] <Kaleo> oSoMoN: ok it _is_ a naming problem
[13:52] <Kaleo> oSoMoN: what's happening is that inside the toolkit plugin "Ubuntu.Components" I'm trying to guess what the path on disk to the plugin is
[13:53] <Kaleo> oSoMoN: Qt 5.1 has a method for that http://doc-snapshot.qt-project.org/qt5-stable/qtqml/qqmlextensionplugin.html#baseUrl
[13:53] <Kaleo> oSoMoN: but Qt 5.0 does not
[13:53] <Kaleo> oSoMoN: so the way I do it is that I convert Ubuntu.Components into Ubuntu/Components
[13:53] <Kaleo> oSoMoN: and then go through the importPathList
[13:54] <Kaleo> oSoMoN: to look for a directory that ends in Ubuntu/Components
[13:54] <Kaleo> oSoMoN: I did not anticipate there could be another Ubuntu/Components
[13:54] <oSoMoN> ahah
[13:54] <Kaleo> oSoMoN: which there is not when the webbrowser is installed
[13:54] <Kaleo> oSoMoN: so the warnings don't happen when installed I guess
[13:55] <Kaleo> oSoMoN: that's wild
[13:55] <oSoMoN> Kaleo: not tested installed, I must admit
[13:55] <oSoMoN> Kaleo: can that be fixed in the toolkit, or should I try to address that in the uninstalled scenario for the browser?
[13:55] <Kaleo> oSoMoN: nah, I can fix it
[13:56] <Kaleo> oSoMoN: somehow
[13:56] <oSoMoN> cool
[13:58] <Kaleo> oSoMoN: I don't know how yet :/
[13:59] <Kaleo> oSoMoN: ok, I do
[13:59] <oSoMoN> Kaleo: that’s ok as I can live with the issue for now, it’s not blocking me in any way
[13:59] <seb128> Kaleo, thanks for the review comments ;-)
[14:00] <Kaleo> seb128: yw
[14:00] <Kaleo> oSoMoN: done, fixed
[14:00] <Kaleo> oSoMoN: ugly
[14:04] <Kaleo> oSoMoN: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/fix_1197293/+merge/172824
[14:06] <Laney> Kaleo: ok, pushed an update if you feel like looking again
[14:17] <oSoMoN> Kaleo: thanks, approved, you might want to have someone on your team give it a quick sanity check too
[14:41] <inaciando> hi all. i am looking the incredible "quickly" an my question is : is it possible develop for ubuntu tablet using "quickly" and gtk liberies?
[14:44] <inaciando> or i have to use qt and qml ?
[14:46] <Kaleo> oSoMoN: you're enough :)
[14:47] <Kaleo> oSoMoN: the code will go away with 5.1
[14:47] <oSoMoN> Kaleo: ok, so feel free to top-approve
[14:48] <Kaleo> oSoMoN: ok
[15:05] <Kaleo> seb128: can you look at the email I fwed you?
[15:56] <seb128> Kaleo, sure (I was out for some exercice, taking a shower and looking at ità
[15:56] <seb128> )
[15:56] <mhall119> jvrbanac: hey, are you around for the API website call in 5 minutes?
[15:58] <jvrbanac> mhall119,
[15:58] <jvrbanac> mhall119, yeah
[15:58] <mhall119> cool
[15:59] <Kaleo> seb128: thx
[16:01] <mhall119> jvrbanac: https://plus.google.com/hangouts/_/08c66ad1e28595b54c403c1771de1ac4fc4c66bf?authuser=1
[17:23] <doanac> boiko: i'm looking at getting some sms stuff automated in the qa lab. I was told you might have some info to help me get stated
[17:24] <doanac> the first question i have. are there some API's for things like "wait for sms"
[17:24] <doanac> ie - how to tell when an sms has arrived
[17:24] <boiko> doanac: hi
[17:25] <boiko> doanac: so, you mean in the phone app or just to test the infrastructure itself?
[17:26] <doanac> boiko: i guess via the phone-app. ie - i'm running a test on the phone and it needs to know if it got an SMS or not
[17:27] <doanac> so a cool CLI like "wait-for-sms --timeout 60s" would be an example
[17:27] <boiko> doanac: ok, are the tests C++ or what?
[17:28] <doanac> boiko: the tests don't exist. i'd prefer python, but I don't know what my options are
[17:28] <boiko> doanac: ah ok, got it, I think python is fine
[17:29] <boiko> doanac: without having to rely on the phone-app itself, you could write a program that listen to ofono signals telling you that you got a new sms
[17:29] <doanac> boiko: is this a dbus sort of thing, or does ofono include its own api?
[17:29]  * doanac googles :)
[17:30] <boiko> doanac: it's dbus
[17:30] <doanac> boiko: cool. i'm going to do some research, but any pointers would be greatly appreciated
[17:30] <boiko> doanac: salem_ can give you more info (as he recently implemented the telepathy component that talks to ofono using those interfaces)
[17:32] <doanac> boiko, salem_: is something like this were I might get started: https://github.com/c4milo/ofono/blob/master/test/list-messages ?
[17:33] <salem_> salem_, kind of, will you be using a real phone, or ofono emulator?
[17:33] <boiko> doanac: that for messages that are already there, but there is a signal emitted when new messages arrive
[17:33] <boiko> doanac: https://github.com/c4milo/ofono/blob/master/doc/messagemanager-api.txt
[17:34] <salem_> doanac, ^
[17:34] <doanac> boiko: thanks!
[17:34] <boiko> doanac: those are for real phone calls and messages, right?
[17:34] <salem_> doanac, org.ofono.MessageManager.IncomingMessage is the signal you have to listen to.
[17:35] <doanac> boiko: yes. we are going to send the phone real sms's
[17:40] <boiko> salem_: ^
[17:42] <salem_> doanac, ok, so the object path will be /ril_0 and the signal is org.ofono.MessageManager.IncomingMessage. a simple python script should do the trick. if you need help to create the script, let me know.
[18:09] <doanac> salem_: if you could share the script it would be incredibly helpful.
[18:09] <doanac> i haven't done DBUS signals before, so i'm guessing i'd make a few dumb mistakes before getting something working
[18:22] <AskUbuntu> autopilot ImportError: No module named input | http://askubuntu.com/q/315996
[18:28] <salem_> doanac, https://pastebin.canonical.com/93763/
[18:29] <salem_> doanac, just change /phonesim by the real modem object path
[18:29] <doanac> salem_: thanks so much! i owe you a beer
[18:30] <salem_> doanac, no problem!
[19:16] <AskUbuntu> I wish to translate for Ubuntu! | http://askubuntu.com/q/316019
[19:50] <AskUbuntu> Can I download Ubuntu for my Galaxy S lll Fido? | http://askubuntu.com/q/316028
[21:43] <boiko> Kaleo: ping
[21:44] <boiko> Kaleo: nevermind, let me double check here
[23:18] <Kaleo> boiko: pong