[02:21] <liuxg__> how to make a button un-clickable in QML?
[05:24] <Guest94518> hi.  someone know how to delete document completely from U1DB and not just do him blank by deleteDoc()?
[07:23] <dholbach> good morning
[12:07] <ahoneybun> omg almost 900 downloads!
[13:15] <sturmflut2> https://uappexplorer.com/app/com.ubuntu.developer.robert-ancell.mines Woohoo! Another entry on my wishlist goes away!
[13:18] <seb128> Robert rocks ;-)
[15:48] <mhall119> popey: what do I have to do to make neverball look nice on my N4?
[15:49] <popey> we're working on that
[15:49] <popey> https://github.com/pseuudonym404/neverball-touch/issues/2#issuecomment-106852605
[15:50] <mhall119> cool
[15:50] <mhall119> I just played the first level, was difficult to navigate the start screens with all the graphical glitches, but I had fun anyway
[15:50] <popey> I suspect its a mir bug
[15:51] <ogra_> just get a properly supported phone :P
[15:51] <popey> make a graphics stack that doesn't depend on the device :p
[15:51] <ogra_> haha
[15:51] <ogra_> you wish
[15:54] <mhall119> popey: mir or SDL's mir backend?
[15:54]  * mhall119 would suspect the latter
[15:54]  * popey shrugs
[15:54] <popey> get a bug filed and let them figure it out
[15:55] <popey> (I have said this 3 times now and nobody seems to have done so)
[15:58] <nik90> popey: hey, is the clock-app on QA's radar? Or do we let them know after OTA-4 instead?
[16:00] <popey> nik90: it's not, but we should, yes. Let me mail them and get it on their trello board. r270 is the one you want, right?
[16:00] <popey> we can choose when to upload to the store of course.
[16:00] <popey> but get it past them.
[16:00] <nik90> yes r270 is the one
[16:01] <popey> ok. and use your manual testing in trunk?
[16:01] <nik90> popey: yes
[16:01] <popey> ok, will do now.
[16:01] <popey> sorry for not doing it before.
[16:01] <nik90> popey: http://pad.ubuntu.com/clock-app-changelog
[16:02] <nik90> popey: it should have all the necessary links and revisions logs
[16:02] <popey> great
[16:02] <nik90> no worries, it just got rdy a day or two ago
[16:07] <popey> mhall119: want me to file the mir bug if you're busy? :)
[16:25] <mhall119> popey: yes please
[16:25] <popey> mhall119: okay ㋛
[16:31] <popey> mhall119: https://bugs.launchpad.net/mir/+bug/1460149
[16:36] <mhall119> popey: +1'd it and added N4 screenshots
[16:36] <mhall119> looks better on mine than yours :)
[16:36] <popey> magic, thanks!
[16:36] <popey> haha
[16:36] <popey> looks better on my arale ㋛
[16:37] <popey> rub rub rub
[16:37] <mhall119> :(
[20:16]  * ahoneybun flashes his newly alive Nexus 4 with Ubuntu
[22:15] <ahoneybun> the terminal is awesome
[22:34] <ahoneybun> how does one make a page/tab flickable?
[22:41] <nik90> ahoneybun: You would need to add a QML component called Flickable{} inside your Page{}. You can find more information about Flickables at http://qt-project.org/doc/qt-5/qml-qtquick-flickable.html
[23:00] <ahoneybun> would that work in the SDK as well? Like can I test without having to push it to a device with a touch screen?
[23:00] <ahoneybun> nik90: ^
[23:01] <ahoneybun> the problem nik90 is that the content overflows the page and there is no way to move down to see the rest, atm I moved the buttons up so they stay on the page
[23:01] <nik90> ahoneybun: Yes you can use it in the SDK as well. It is used pretty much in every app that displays lot of stuff that doesn't fit the dimensions of a phone. And yes you can also test it without a touch screen by simply scrolling.
[23:02] <nik90> ahoneybun: QML Components *generally* work with multiple input methods..so a Flickable works in a touch environment by flicking, scrolling, dragging etc...and also using mouse scrolling on a mouse input device.
[23:03] <ahoneybun> nik90: I never could get the flickable thing to work
[23:03] <nik90> ahoneybun: your use case definitely fits the use case of a Flickable
[23:03] <nik90> ahoneybun: the key thing to getting a flickable to work is the "contentHeight" and "height" property.
[23:04] <ahoneybun> yea...
[23:04] <ahoneybun> how would that work on different devices
[23:04] <nik90> contentHeight refers to the total height that your components inside the flickable would need..where as height is the flickable height that is allowed.
[23:04] <nik90> so for example, height: page.height
[23:04] <ahoneybun> not a big deal really since I have only one device
[23:04] <nik90> while contentHeight: component1.height + component2.height etc...
[23:05] <nik90> if all the components fits on the screen, then the flickable will just not scroll but still work as intended
[23:05] <nik90> s/fits/fit
[23:05] <ahoneybun> where do I put the flickable inside the column?
[23:05] <nik90> ahoneybun: no...usually the Flickable is the direct child of a Page.
[23:06] <nik90> so Page { Flickable{} }
[23:06] <nik90> columns go inside the flickable
[23:06] <nik90> one sec, let me grab you a sample code
[23:06] <ahoneybun> thank you
[23:06] <ahoneybun> I like examples
[23:07] <nik90> ahoneybun: take a look at https://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/utopic-3.0/view/head:/app/clock/ClockPage.qml
[23:07] <nik90> ClockPage.qml is a regular Page{}...in line 170 we use a Flickable
[23:07] <nik90> and put the UI components inside it
[23:08] <ahoneybun> as in buttons
[23:08] <nik90> yes
[23:08] <nik90> well buttons, text, columns, rows etc
[23:08] <nik90> anything UI element
[23:09] <nik90> think of Flickable as this dynamically changing Bag..you don't put a Bag inside other stuf..but rather stuff inside the bag
[23:09] <nik90> sry, I am terrible with analogy :P
[23:09] <ahoneybun> http://bazaar.launchpad.net/~aaronhoneycutt/ubuntu-beginner/2.0/view/head:/components/Home.qml
[23:09] <ahoneybun> this is where I need it
[23:09] <nik90> ah perfect..just put that whole column inside the flickable
[23:10] <ahoneybun> oh
[23:11] <ahoneybun> let me try
[23:11] <nik90> ahoneybun: on the desktop, try reducing the height of your app to simulate small devices and see how the flickable allows the user to scroll through it to see all the buttons and information
[23:11] <ahoneybun> it will not even work right on the Nexus 4 lol
[23:11] <ahoneybun> look right
[23:11] <ahoneybun> I need to fix it badly
[23:13] <ahoneybun> so for my projects it would be contentHeight: omgubuntu.height + webupd8.height and such?
[23:13] <ahoneybun> *project
[23:13] <nik90> for your project it would be contentHeight: column.height
[23:13] <ahoneybun> jus that?
[23:13] <nik90> you need to give the column an id and use that
[23:13] <ahoneybun> *just
[23:13] <nik90> yup
[23:14] <ahoneybun> ok I'll try
[23:14] <nik90> since the column already dynamically adjusts its height to its children
[23:15] <ahoneybun> works but I get a error: QML Flickable: Binding loop detected for property "contentHeight"
[23:17] <ahoneybun> plus it shots you back to the tip
[23:17] <ahoneybun> *top
[23:17] <nik90> ahoneybun: let me try and send you a merge request ;)
[23:18] <ahoneybun> never had one of those
[23:18] <ahoneybun> I might want to upload my current work first lol
[23:18] <ahoneybun> though I cant
[23:18] <ahoneybun> dont think I have access to upload
[23:19] <nik90> what do you mean? Isn't this your own project?
[23:19] <ahoneybun> or knowledge anymore lol
[23:19] <ahoneybun> its been so long
[23:19]  * ahoneybun is learning git anyway
[23:19] <nik90> anyway give me 5 mins to get this sorted..it is really easy either way
[23:20] <ahoneybun> ok
[23:22] <ahoneybun> uploaded my current changes
[23:22] <ahoneybun> 2.0 is the newest
[23:22] <ahoneybun> now anyway
[23:29] <ahoneybun> awesome job on the music player guys
[23:31] <nik90> ahoneybun: http://paste.ubuntu.com/11441359/
[23:32] <nik90> ahoneybun: Since you set anchors.fill:parent to the column and at the same time told flickable to take the column's height it got confused
[23:32] <nik90> its like saying me asking you for an idea, and then you reply with "you give me an idea"
[23:33] <ahoneybun> oh
[23:33] <ahoneybun> so I need to make changes on main.qml as well
[23:34] <nik90> no not really
[23:34] <nik90> I added Flickable{} stuff to main.qml...but you could very well have done it in home.qml instead
[23:34] <nik90> its just personal prefernce
[23:36] <ahoneybun> its broke
[23:36] <ahoneybun> I broke it
[23:37] <ahoneybun> http://pastebin.ubuntu.com/11441477/
[23:41] <ahoneybun> page size if off llol
[23:51] <nik90> ahoneybun: why did you add Flickable {} to both main.qml *and* home.qml ?
[23:51] <nik90> you need it in only one place
[23:52] <nik90> also remove the onFlickStarted signal..you don't need it
[23:56] <ahoneybun> someone is up with the width