[01:17] <ralph> hello room
[01:19] <ralph> I have got a prob while trying to build quagga to a .deb excutable as done in the ubuntu repo. Does anyone know how I can do that?
=== chihchun_afk is now known as chihchun
[06:29] <akiva-thinkpad> Hi all
[06:45] <dholbach> good morning
=== _morphis is now known as morphis
[07:00] <akiva-thinkpad> balloons: ping
[07:01] <akiva-thinkpad> file:///usr/share/filemanager/qml/components/FolderListDelegate.qml:19:1: module "Ubuntu.Components" version 1.2 is not installed
[07:01] <akiva-thinkpad> junkins is still giving me this error.
[07:02] <akiva-thinkpad> bah hes probably sleeping.
[07:02] <akiva-thinkpad> dholbach: Do you know if jenkins supports ubuntu.components 1.2 yet?
[07:02] <dholbach> akiva-thinkpad, I have no idea
[07:02] <dholbach> zbenjamin, ^ do you know?
[07:03] <akiva-thinkpad> ty
[07:09] <akiva-thinkpad> dholbach: curious, do you know if the sdk works on unity 8 yet?
[07:09] <akiva-thinkpad> also do you know the ubuntu channel that mainly is for developing unity 8? I'd like to contribute some things if I can.
[07:10] <dholbach> akiva-thinkpad, I think somebody mentioned that it worked there, but I haven't confirmed it yet
[07:11] <akiva-thinkpad> dholbach: cool thanks
[07:11] <dholbach> akiva-thinkpad, AFAIK changes to unity8 and friends are auto-published to wily
[07:11] <dholbach> zbenjamin and bzoltan_ can likely confirme all the bits above
[07:12]  * bzoltan_ grabs a coffee
[07:12] <akiva-thinkpad> dholbach: Ah going to go download wily then!
[07:13] <akiva-thinkpad> bzoltan_: can you take a look at this small merge: https://code.launchpad.net/~akiva/qtcreator-plugin-autopilot/Improve-code-issue-readability
[07:16] <akiva-thinkpad> the main change is refining the issues displayed when tests fail to load: http://i.imgur.com/Xzc0mov.png
[07:17] <akiva-thinkpad> Prior, it used to be in one issue, and it expanded to an annoyingly large pane.
[07:17] <bzoltan_> akiva-thinkpad:  looks good, it will take few ten minutes to read the code and then I will test it.
[07:17] <akiva-thinkpad> bzoltan_: thanks.
[07:19] <akiva-thinkpad> bzoltan_: just curious, do you know if jenkins supports ubuntu.components 1.2 yet? its failing my patch to the filemanager app file:///usr/share/filemanager/qml/components/FolderListDelegate.qml:19:1: module "Ubuntu.Components" version 1.2 is not installed
[07:20] <bzoltan_> akiva-thinkpad:  I am wondering about that failure ... 1.2 was available already in Vivid ...
[07:20] <akiva-thinkpad> bzoltan_: are there any core apps that are using 1.2 that are passing jenkins?
[07:21] <bzoltan_> akiva-thinkpad:  now that is a good question ... UITK itself is using it for the component gallery app... and it does pass
[07:21] <bzoltan_> akiva-thinkpad:  I do not know by heart what APIs the core apps are using
[07:22] <akiva-thinkpad> bzoltan_: do you know the lp for the uitk?
[07:23] <akiva-thinkpad> nvm
[07:23] <bzoltan_> akiva-thinkpad:  I do : lp:ubuntu-ui-toolkit
[07:23] <akiva-thinkpad> :)
[07:23] <akiva-thinkpad> ty
[07:39] <akiva-thinkpad> bzoltan_: zbenjamin just an fyi, Jenkins is directing people here for troubleshooting: https://developer.ubuntu.com/api/devel/ubuntu-14.10/python/autopilot/faq/troubleshooting.html
[07:39] <bzoltan_> akiva-thinkpad: OMG
[07:40] <akiva-thinkpad> o_O
[08:16] <didrocks> kalikiana: bzoltan_: hey! I'm trying a basic deleteDoc(docId) in u1db and I can confirm (stringifying the database as well) that the .contents is empty (but the docId still exists). However, db.listDocs() still returns the Document that I deleted (not the contents, but the docId), and so, using it as a model, it doesn't filter it
[08:16] <didrocks> kalikiana: bzoltan_: this sounds like some part of bug #1213013 isn't fixed, do you mind confirming?
[08:16] <ubot5> bug 1213013 in U1DB Qt/ QML "Deleted documents show up in Query in a ListView" [Critical,Fix committed] https://launchpad.net/bugs/1213013
[08:19] <didrocks> it seems to be bug #1219862 as well
[08:19] <ubot5> bug 1219862 in U1DB Qt/ QML "Deleted documents show up in Database as a model" [High,Confirmed] https://launchpad.net/bugs/1219862
[08:22] <akiva-thinkpad> dholbach: is wily unity8 by default, or is there two images just like there was back in 15.04?
[08:22] <dholbach> akiva-thinkpad, no, it's still unity7 by default
[08:22] <akiva-thinkpad> dholbach: is there a special image then? or just install through the repos?
[08:23] <dholbach> yes, just install through the repos should work
[08:23] <akiva-thinkpad> okay :)
[08:24] <akiva-thinkpad> I guess I should have gotten this: http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
[08:24] <dholbach> that doesn't look very up to date
[08:24] <dholbach> you can ubuntu-desktop-next
[08:24] <dholbach> err
[08:24] <dholbach> you can install ubuntu-desktop-next
[08:24] <akiva-thinkpad> okay thanks
[09:29] <ohmy> hello everybody
[09:29] <ohmy> i'm quite confused please help me. I have two projects one depends on the other (only qml files with lot of subdirectories)
[09:29] <ohmy> I'm new to .qmlproject syntax, i've copied one of the provided in examples
[09:29] <ohmy> in QmlFiles section i've added the needed code from my main project but i still have foo_bar unavailable
[09:29] <ohmy> How to tell qmlscene where to find the needed qml files please ?
[09:34] <ohmy> is there any docs about .qmlproject  syntax ?
=== alecu_ is now known as alecu
[12:08] <kalikiana> t1mp: remember to mark a bug as Incomplete if you're asking for clarification, otherwise it's stuck at New forever https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1466410
[12:08] <ubot5> Ubuntu bug 1466410 in ubuntu-ui-toolkit (Ubuntu) "Tabs/Pages don't work correctly when Repeater used" [Undecided,Incomplete]
[12:12] <didrocks> kalikiana: hey, did you see my questions above about bug #1219862?
[12:12] <ubot5> bug 1219862 in U1DB Qt/ QML "Deleted documents show up in Database as a model" [High,Confirmed] https://launchpad.net/bugs/1219862
[12:15] <kalikiana> didrocks: sorry, I apparently missed the notification, I see it now. why are you using listDocs as a model rather than an actual model if I may ask?
[12:16] <didrocks> kalikiana: no worry! At first, I was using "db" directly as the model as some examples from u1db-qt do that. Then, I wanted to check the behavior as I was seeing those additional elements with listDocs() as I thought it will return only valid docs
[12:17] <didrocks> kalikiana: so the behavior was confusing, especially as I used it for debugging purpose :)
[12:18] <kalikiana> didrocks: I agree it is confusing. Right now I would actually suggest you just use Query and forget about the Database. It has more features and if I could change back time, only one would exist
[12:19] <didrocks> kalikiana: yeah, maybe a warning or something in the documentation should be written if the bug isn't fixable?
[12:20] <didrocks> (and yeah, I used a query on a dummy index to fix it)
[12:22] <kalikiana> it might be misleading to just deprecate it since it is needed to delete docs at least
[12:22] <kalikiana> hmm
[12:25] <didrocks> kalikiana: I guess at least a warning in the API doc would be good enough (and telling to use Index + Query)
=== tedg is now known as ted
=== _salem is now known as salem_
=== chriadam is now known as chriadam|away
[14:37] <notmorpheus> Anyone know why attempting to read /bin/lesskey would hang (in Python, open() 'rb')?
[14:39] <popey> notmorpheus: in an app in a click package
[14:39] <popey> ?
[14:40] <notmorpheus> Nah, Python script
[14:50] <didrocks> zsombi: I'm sure I'm doing some wrong things in term of Layout, (like I don't understand why I need for things to look ok to set width: parent.width on a lot of components), but I wonder why setting visible: false and then visible: true without doing anything else may change some positionning?
=== chihchun is now known as chihchun_afk
[14:54] <kalikiana> rhuddie: can you have a look at this? https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1471848
[14:54] <ubot5> Ubuntu bug 1471848 in ubuntu-ui-toolkit (Ubuntu) "Autopilot always wants to emulate Nexus10 on desktop for UITK gallery tests" [Undecided,New]
[14:55] <zsombi> didrocks: well, if a component is marked not to be visible, you may not even want to occupy a space for it
[14:55] <zsombi> didrocks: Positioners may however not take that into acount...
[14:56] <didrocks> zsombi: but when restoring, it should restore at the same place, isn't it?
[14:56] <zsombi> didrocks: there were lots of bugs around that upstream, not sure whether it has been fixed everuwhere
[14:56] <zsombi> didrocks: not necessarily, depends on the positioning policy
[14:56] <didrocks> zsombi: I'm sure that my bugs results by a bad way of dealing with width/height, I would be happy when you get some time to get some advice/cleanup
[14:57] <didrocks> (not sure when would be a good time for you)
[14:57] <zsombi> didrocks: :D never and always is good
[14:58] <rhuddie> kalikiana, sure, I'll take a look later on
[14:58] <kalikiana> rhuddie: thanks!
[14:59] <didrocks> zsombi: heh, I pushed it to https://github.com/didrocks/splitthebill. You can see that the 2 Total lines (corresponding to Total.qml) have their content switched out of the window after changing the section header back and force
[15:00] <didrocks> zsombi: Basically Main.qml includes DetailsPage which includes a bunch of components (one of them being Total.qml)
[15:00] <didrocks> zsombi: you will see a lot of:
[15:00] <didrocks>     width: parent.width
[15:00] <didrocks>     Layout.maximumWidth: parent.width
[15:00] <didrocks> I'm unsure about the best practice, but I bet the issue can come from this
[15:01] <didrocks> (width and height have always to be set it seems, right? they don't get an implicit width/height from their children?)
[15:24] <zsombi> didrocks: without looking on your code, if you use Layout attached property, it doesn't make any sense to set the width of the component, as Layout attached widths will overrule those
[15:26] <zsombi> didrocks: then, if you have a Positioner (Row, Column, etc) you don't have to set their width, height as those are set based on their children's size
[15:27] <zsombi> didrocks: RowLayout or ColumnLayout are not positioners, those are layouters, so they should have a width, and they do adjust their content based on what you specify in the Layout attached properties
[15:34] <didrocks> zsombi: that's what I was thinking, but I saw that if I didn't set the height on some elements, this didn't really work to me
[15:34] <didrocks> zsombi: so, let me do a pass on the code, cleaning that as it's the logical way to me, and then, we can fix together my "wronglyness"? ;)
[15:35] <zsombi> didrocks: if you are dealing with a RowLayout, you need to set the height, or you can use Layout.preferredHeight
[15:35] <didrocks> zsombi: ah, that starts to make sense, why is that btw?
[15:35] <didrocks> (Row doesn't need height, but RowLayout needs?)
[15:36] <zsombi> didrocks: well, as said, Row is a positioner, it distributes teh items based on the width
[15:36] <zsombi> didrocks: but RowLayout is not a positioner, si a layout distribution element
[15:37] <zsombi> didrocks: Row does only care on teh widths, but RowLayout also needs to know what height should an element have, and it takes those values from the Layout.xxxxHeight and Layout.xxxWidth oproperties
[15:38] <didrocks> zsombi: so, RowLayout enables to have multiple heights elements contrary to Row, am I correct?
[15:38] <zsombi> didrocks: you can also simply set Layout.fillHeight, then you can be sure the element will take the full height of the RowLayout
[15:38] <zsombi> didrocks: no, RowLayout has to have the height, Row doesn't care about those
[15:39] <didrocks> zsombi: I think I did read the qml help too quickly or some explanation on this positions/layout distribution element are missing (at least, in my mind), do you have good refs so that I can get the concept?
[15:39] <zsombi> didrocks: the only time Row uses the height (implicitHeight) when it calculates how much height shoudl it have, and that is talken from the childrenRect.height
[15:39] <didrocks> but RowLayout can't do that automatically? You need to say Layout.fillHeight to have the same "behavior" then?
[15:39] <zsombi> didrocks: well, not more than the QtQuick.Layouts has or eventually the QWidget layout boxes...
[15:40] <didrocks> so that it's using the implicitHeight based on childrenRect.height?
[15:40] <zsombi> didrocks: as said, RowLayout has to have a height, and a width, so it knows where to render its children :)
[15:40] <zsombi> didrocks: Row arranges the items in a row taking into account the item width
[15:41] <zsombi> didrocks: RowLayout *can* resize each element when its size is changed
[15:41] <didrocks> yeah, I understood that difference (and for the width, it makes sense to me)
[15:42] <zsombi> didrocks: for instance, a RowLayout whith 3 children, where the first one's minWidth = maxWidth=prefWidth, the third one minWidth=40GU, maxWidth=50GU and f=prefWidth=40GU
[15:42] <didrocks> I've more issues to understand why it doesn't have another behavior for the height
[15:42] <didrocks> zsombi: yeah, no worry on the width, I understood the difference on that one (and it matches most of the Box models that exists in other toolkits)
[15:43] <zsombi> didrocks: the the mid (second) one is having fillWidth, when you resize the RowLayout you will see the first column size not changing, the third one width changing between 40GU and 50GU, and the mid one filling th erest of the space available
[15:43] <didrocks> yeah, I'm using this kind of behavior (that's why I'm using RowLayout instead of Row)
[15:43] <zsombi> didrocks: but as these elements can have different height, the same applies on the height of each element
[15:44] <zsombi> didrocks: you and there, in RowLayout, you can decide whether you use height: parent.height or - and I'd suggest this one - use Layout.fillHeight: true so you can be sure your sizing is correct
[15:46] <didrocks> zsombi: I would expect such behavior in GridLayout, not in RowLayout TBH (at least, that the default would be Layout.fillHeight: true)
[15:46] <didrocks> but I can use this anyway, now that I know there is no magic for this
[15:46] <zsombi> didrocks: each Row/ColumnLayout is derived from GridLayout, so perhaps that;'s why they work like this
[15:46] <zsombi> didrocks: but never the less, you have to specify a height
[15:47] <zsombi> didrocks: even for a Row, you have to specify a height for each element you put in the row
[15:47] <didrocks> zsombi: they never inflate based on content height?
[15:48] <zsombi> didrocks: :)
[15:48] <zsombi> didrocks: you still don't get it, don't you?
[15:48] <zsombi> didrocks: check how a Row { Item{...} Item {...} Item {...}} works
[15:48] <didrocks> zsombi: well, I get what needs to be done (like setting it), I don't understand why it's not explicit
[15:48] <didrocks> implicit*
[15:49] <zsombi> didrocks: if you do it like that, Row will get its height/width set implicitly
[15:49] <zsombi> didrocks: ok?
[15:49] <didrocks> until here, yeah :)
[15:49] <zsombi> didrocks: because it is a Positioner
[15:49] <zsombi> it does positioning
[15:50] <zsombi> didrocks: now RowLayout *must have* a width/height set, because it is NOT a positioner
[15:50] <zsombi> didrocks: it is a layout element
[15:50] <zsombi> each layout element must have a size
[15:50] <zsombi> like Item, Rectangle, etc
[15:50] <zsombi> didrocks: ok?
[15:51] <didrocks> because the "content" size doesn't change their own size (and that's by definition), am I correct?
[15:51] <zsombi> didrocks: exactly
[15:51] <didrocks> and the content can as well (if you don't set clip: true) get outside of the parent element
[15:51] <didrocks> so ok, only positioners can get some implicit height/width
[15:51] <zsombi> didrocks: not from the Row/ColumnLayout
[15:51] <zsombi> didrocks: only from Row/Column
[15:52] <didrocks> yeah
[15:52] <zsombi> didrocks: so, none of the layout element sdo force their children to take an implicit size, ever
[15:53] <zsombi> didrocks: therefore you have to specify these manually
[15:53] <zsombi> didrocks: if you use the width/height, you lose the dynamic resizing capabilities of the layout
[15:53] <didrocks> ok, but children can change their sizes to accomodate the parent layout element
[15:53] <zsombi> because you can only set a value
[15:53] <zsombi> yes, they can
[15:54] <didrocks> ok, starting to make sense
[15:54] <zsombi> didrocks: so, for height, you can do this in a RowLayout
[15:54] <zsombi> didrocks: for width, you may want to evenly fill the content available, and have a dynamic resizing... so you use the attached properties
[15:55] <didrocks> attached properties, you mean Layout.<...>?
[15:59] <zsombi> didrocks: yes
[16:01] <didrocks> zsombi: I think I get it now, thanks for this explanation (wasn't that clear from the Qt doc to me at least :)). Let me fix my example tomorrow morning and if you don't mind, I would love you checking that I got it right so that I don't spread misinformation
[16:01] <zsombi> didrocks: sure, just ping me, I'll find a slot to check it ;)
[16:02] <didrocks> zsombi: thanks a lot! :)
[16:02] <zsombi> didrocks: yw
[16:04]  * rickspencer3 tries creating a 15.04 armhf kit
[16:04]  * rickspencer3 braces
=== karni is now known as karni-away
[20:19] <cwayne> hiya, are there any docs/guides to writing an html5 app that can use location service?
[20:47] <deekay> hi
[20:47] <deekay> can someone help me with the autostart at ubuntu phone?
[20:47] <deekay> wana use syncthing
[20:48] <deekay> its work well, but i need to start it automatic or by a webapp ...
[20:49] <deekay> the dir /usr/share/upstart/sessions/ is read-only
=== javiercrowsoft1 is now known as javiercrowsoft
=== salem_ is now known as _salem