[00:00] <zmaj> oh yeah,and the whole thing does apparently work with oxide
[02:06] <penk_> karni: did you make a merge like 10 minutes ago..
[02:07] <karni> penk_: hi :D
[02:07] <penk_> karni: what time is it over there :D
[02:07] <karni> it's 3:07 AM :D
[02:07] <karni> haha
[02:07] <penk_> haha classic karni
[02:08] <karni> haha. was about to leave :) have a good day, penk_ o/
[02:08] <penk_> karni: sleep tight
[02:08] <karni> tnx!
[09:16] <JamesTait> Good morning all; happy International Anti-corruption Day! :-D
[11:39] <popey> balloons: any luck with tests for https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/NewDayView-Final/+merge/242346 ?
[11:39] <popey> be great to get that landed
[13:29] <karni> bzoltan: hey, I'm seeing this log line. this hasn't been fixed since, I understand? https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1260793
[13:38] <rpadovani> hey popey, any luck to provide infrastructure and autopilot to calculator reboot?
[13:39] <popey> hey rpadovani
[13:39]  * popey needs to check with balloons and fginther 
[13:40] <popey> when they wake, will do and get back to you
[13:40] <balloons> eh?
[13:40] <rpadovani> thanks :-)
[13:41] <popey> balloons: we talked a week or more ago about autopilot tests for the new calculator reboot
[13:44] <balloons> so rpadovani what do you need exactly? Just the initial test setup?
[13:45] <rpadovani> balloons, well, could be a start, yes. popey said during the vUDS that someone from QA team will work with us on doing tests, but if no one is available i think we can do on our own, after the setup
[13:46] <popey> rpadovani: we should have bugs for each test that needs writing.
[13:46] <popey> (unless you want to track them elsewhere)
[13:47] <rpadovani> popey, ok, will do
[13:51] <viejotren> Hi guys, is there any online workshop right now? from the video I just have the workshop from yesterday, is that right?
[13:51] <viejotren> YearEnd hack days continue today right?
[13:51] <balloons> rpadovani, ahh, well I'm  trying to stir up some more interest this week so hopefully a few more folks step forward to help out. And yes, please file bugs so I can point folks at them :-)
[13:52] <rpadovani> balloons, cool, thanks :-) I'll start to do that
[13:52] <balloons> we'll get you some help one way or another
[14:32] <dholbach> balloons, doing a test-build of https://code.launchpad.net/~flscogna/ubuntu-weather-app/reorganization-and-native-launcher/+merge/241351 now
[14:32] <rpadovani> Saviq, implemented restart button in 100balls, thanks for the feedback!
[14:33] <balloons> swordfish90, I asked dholbach to take a look at the weather MP that wasn't building ^^
[14:33] <balloons> rpadovani, if you could also use the 'needs-autopilot-test' tag when you open them that would be great
[14:33] <rpadovani> balloons, ok :-)
[14:33] <dholbach> dh_install: qtdeclarative5-ubuntuweather-timezone-plugin1.0 missing files (usr/lib/*/qt5/), aborting
[14:34] <swordfish90> balloons, dholbach Ok thanks. There is probably an issue with the timezone plugin.
[14:34] <dholbach> looks like stuff gets installed into:
[14:34] <dholbach> /tmp/buildd/ubuntu-weather-app-1.8.3ubuntu1/debian/tmp/usr/lib/x86_64-linux-gnu/TimeZone/*
[14:34] <dholbach> so qt5 <-> TimeZone
[14:34] <dholbach> that's the mismatch
[14:35] <dholbach> I don't know where you want things installed
[14:35] <dholbach> either you need to change things in CMakeLists.txt
[14:35] <dholbach> or in debian/*.install
[14:35] <dholbach> I would suggest to have a look at where other app store their plugins
[14:35] <dholbach> so it's nice and consistent
[14:37] <swordfish90> dholbach, I actually took everything from the terminal app where everything is working fine. Thank you dholbach ...
[14:37] <dholbach> swordfish90, so files get installed into usr/lib/*/TimeZone right now
[14:37] <dholbach> swordfish90, but the packaging assumes that they're in usr/lib/*/qt5/
[14:38] <dholbach> you only need to decide which of the two paths you actually want
[14:38] <dholbach> :)
[14:41] <swordfish90> dholbach, Yesterday I tried that but maybe I got the folder name wrong... I'll just check right now if it's that fast... :D
[14:42] <dholbach> swordfish90, it's src/plugins/CMakeLists.txt: and debian/qtdeclarative5-ubuntuweather-timezone-plugin1.0.install AFAICS
[14:44] <Saviq> rpadovani, sure!
[14:51] <swordfish90> dholbach, And that's a step forward. It builds, It's still not working when installed on the desktop though, investigating that.
[14:53] <dholbach> swordfish90, ok cool - let me know if you need more help
[14:53] <swordfish90> dholbach, ok, thanks..
[15:07] <xavigarcia> mhall119: OK, I see the problem, I will add my changes in a plain text file then.
[15:07] <xavigarcia> mhall119: thanks again
[15:08] <mhall119> xavigarcia: no problem
[15:14] <karni> Hey folks. Anyone had an issue with URLs/links that are properly linkified, but do not pop open a browser?
[15:31] <swordfish90> dholbach, Ok another step forward. We are still missing the qml files on the desktop. Basically the application looks inside "/usr/share/weather/" instead of "/usr/share/ubuntu-weather-app/". Do you know how qt and cmake manage this?
[15:33] <dholbach> it should all be in CMakeLists.txt somewhere
[15:33] <dholbach> if there's a place where you define the dir or app name, and there's just "weather" and not "ubuntu-weather-app", try adjusting that
[15:36] <viejotren> Hello, how may I enter to Year End Hack Days activities?
[15:38] <dholbach> popey: ^ :)
[15:38] <popey> hey viejotren !
[15:38] <popey> viejotren: sure can. Any app in particular take your interest?
[15:39]  * popey gets coffee
[15:40] <balloons> howdy viejotren!
[15:40]  * balloons subtly encourages viejotren to consider helping by writing some tests :-)
[15:43] <popey> hehe
[15:43] <viejotren> thanks popey and balloons, I would to help in any task related, I don't know if there are some scheduled tasks for these Hack days or if there are any availables, so please guide me and let me know how may I enter
[15:43] <popey> viejotren: also, what's your main area of skill... python, c++ and qml are all useful talents.
[15:43] <viejotren> popey: c++ and python, with qml I'm beginner
[15:44] <popey> so I think balloons might be very interested in your python skills
[15:44] <popey> balloons: can you help viejotren get bootstrapped with tests maybe while dholbach and I do the hangout?
[15:45] <balloons> popey, ohh, why sure, thanks for doing the q and a
[15:45] <popey> np
[15:45] <popey> \o/
[15:45] <popey> I love it when a plan comes together
[15:46] <balloons> viejotren, so we make an effort to test all of the core apps. There's lower level tests which are written in qml. But in addition to those, we have a set of acceptance tests which are written in python using a tool called autopilot. These tests are intended to mimic the end user and make sure the apps work as expected
[15:48] <viejotren> balloons: ok, so would you like if I run the tests of the core apps?
[15:50] <balloons> viejotren, if writing some automated tests sounds interesting to you, you could use your python skills. the python is pretty simple, and I can teach you about how to use the tool
[15:51] <balloons> I'll leave you some links for reading later for reference. For now, let's dive in on a test shall we?
[15:52] <viejotren> balloons, sounds great, I'll wait for the links, thnks
[15:52] <balloons> Here's the API links for autopilot and the sdk helpers as they are called: http://developer.ubuntu.com/apps/platform/apis/. The autopilot docs have a tutorial in them
[15:53] <balloons> and here's our philosophy on writing tests: http://developer.ubuntu.com/apps/platform/guides/acceptance-testing-using-the-page-object-model/
[15:54] <balloons> viejotren, so let's get you started by showing you how to run some existing tests. You'll need to install autopilot
[15:55] <balloons> what version of ubuntu do you have?
[15:55] <viejotren> I have 14.10 installed, is that ok?
[15:57] <balloons> viejotren, yep that should work great. So install python3-autopilot python3-autopilot-vis ubuntu-ui-toolkit-autopilot
[15:58] <viejotren> balloons, cool, give me a minutes
[16:01] <viejotren> balloons, got them
[16:02] <viejotren> I got the urls as well
[16:02] <balloons> excellent. So let's pull a core app branch and show you how to run the tests, then take a peek at them
[16:03] <viejotren> balloons: cool
[16:03]  * balloons thinks of which app
[16:04] <akiva-thinkpad> oh the hack already started >_<
[16:04] <balloons> viejotren, why don't you branch lp:ubuntu-calculator-app
[16:04] <akiva-thinkpad> someone tell me where we are
[16:04] <balloons> hey akiva-thinkpad!
[16:04] <akiva-thinkpad> balloons, o/
[16:04] <balloons> viejotren, so bzr branch lp:ubuntu-calculator-app
[16:05] <balloons> once you get it you'll have the code for the calculator app. It's a pure qml app and so you can run without compiling anything via qmlscene. Anyways, inside you'll find the tests folder, and inside that an autopilot folder
[16:05] <balloons> cd to the folder..
[16:05] <balloons> something like ubuntu-calculator-app/tests/autopilot
[16:06] <balloons> akiva-thinkpad, thinking of trying to finish off some old mp's, work on something new or ?
[16:06] <balloons> viejotren, from there we can list the tests and run an individual test or the entire test suite.
[16:07] <akiva-thinkpad> Just whatever is being worked on at the moment.
[16:08] <viejotren> balloons: ok, just give me a minutes to branch it, honestly I don't have all clear how to do it but I'll catch it, wait some minutes plz
[16:08] <balloons> akiva-thinkpad, today is file manager and calendar day, but folks are working on many things :-)
[16:08] <balloons> viejotren, sure thing, ask questions as we go, I'm here to help :)
[16:08] <balloons> howdy topwobble
[16:09] <akiva-thinkpad> Ah in that case i should probably fix my mp in the calendar :~   Those tests are so unintuitive to run.
[16:09] <topwobble> heyo balloons
[16:10] <akiva-thinkpad> mmmm
[16:13] <balloons> akiva-thinkpad, let me know if I can help
[16:20] <akiva-thinkpad> balloons, I will; I am going to see if I can build a gui for autopilot3, although I am wondering if I want to use qml or qt. If I use QML; I want it to be usable with the HUD; do you know how to make sure actions appear in Unity7's hud with qml?
[16:21] <balloons> akiva-thinkpad, what do you mean a gui?
[16:21] <balloons> on the unity7 + hud + qml, tedg is the person to ask
[16:21] <akiva-thinkpad> QUESTION: Basically I want to have a list populated by autopilot3 list
[16:21] <viejotren> balloons: I'm ready, I got ubuntu-calculator-app, right now I'm on tests/autopilot directory, next?
[16:22] <akiva-thinkpad> and then use that data to make them "click to run"
[16:23] <balloons> viejotren, so "autopilot3 list ubuntu_calculator_app" will list the tests for the calculator app
[16:23] <akiva-thinkpad> Mystery companies!
[16:23] <akiva-thinkpad> wow interesting!
[16:23] <akiva-thinkpad> errm wc
[16:23] <balloons> akiva-thinkpad, the autopilot guys would love to hear your thoughts and could certainly give you feedback
[16:24] <viejotren> 33 total tests
[16:24] <viejotren> balloons: got 33 total tests
[16:25] <balloons> viejotren, awesome. Ok, so let's run one so you can see
[16:25] <akiva-thinkpad> balloons, well I wanted to make it a plugin, but I can't figure out how to get plugins to build a QWidget. QApplication requires a main.cpp and I am a bit clueless how to find it.
[16:25] <balloons> viejotren, autopilot3 run -v ubuntu_calculator_app.tests.test_simple_page.TestSimplePage.test_two_negative_numbers_multiplication
[16:25] <balloons> that will run that specific test. When you start it, it will launch the app, move your mouse and interact with the application
[16:26] <balloons> you could also choose to run all the tests by passing just the module name (ubuntu_calculator_app), like so autopilot3 run -v ubuntu_calculator_app.
[16:27] <balloons> You probably won't want to do that on your desktop session directly, else you have to wait for it to run before you get control of your mouse again :-)
[16:27] <viejotren> balloons: cool, it works, it's like a demo of the calc app, in fact it is an example of a multiplication
[16:28] <balloons> viejotren, yep exactly. So let's take a look at the python behind it all ok?
[16:29] <balloons> let's look at the test we just ran to start
[16:29] <balloons> open ubuntu_calculator_app/tests/test_page_simple.py
[16:29] <viejotren> balloons: I'll run another ones
[16:30] <viejotren> balloons: ok, I'll open it
[16:30] <balloons> viejotren, if you want to run them without loosing control of your mouse, autopilot ships with a useful script called autopilot3-sandbox-run. It will run the app and tests inside an Xfvb environment
[16:30] <balloons> if you pass -X to that script it will also display them to you in a window
[16:31] <balloons> so autopilot3-sandbox-run -X ubuntu_calculator_app.tests.test_simple_page.TestSimplePage.test_two_negative_numbers_multiplication
[16:32] <viejotren> balloons: I opened test_page_simple.py
[16:32] <balloons> ok, so inside the python script you can see the testcase defined as a method
[16:33] <balloons> def test_two_negative_numbers_multiplication(self):
[16:33] <balloons> each method starting with test_ will run individually as a test
[16:34] <balloons> before each test run, the setUp method will be called
[16:34] <balloons> and after each run the tearDown method will be called. In most cases, the tearDown method isn't explicitly defined as we don't need to modify the default
[16:34] <popey> ahayzen: jouni has some questions for you
[16:35] <ahayzen> popey, i'm all ears :)
[16:35]  * popey casts a spell
[16:35] <balloons> viejotren, the class you can see inherits CalculatorAppTestCase, which is a custom class we created. We'll look at it in a second
[16:35] <ahayzen> hehe
[16:36] <balloons> viejotren, you can also see we are using some helper methods that are coming from from ubuntu_calculator_app.tests import CalculatorAppTestCase
[16:36] <viejotren> balloons: got it, I found the methods and I'm reading the entire class
[16:36] <balloons> this keeps the actual testcase simple and easy to read. Awesome ;-)
[16:37] <balloons> you will want to check out both __init__.py files. One contains the helper methods, and the other performs the setup and application launch
[16:37] <viejotren> balloons: ok
[16:39] <balloons> The class CalculatorBaseTestCase describes the setup and launch of the application. This is pretty standard across all the core apps
[16:39] <balloons> you can more or less assume it works and does what you need for now. It handles launching on the phone and desktop
[16:39] <viejotren> balloons: got  that class (CalcTestCase)
[16:40] <viejotren> balloons: cool
[16:40] <balloons> so right, the testcase files inherit from CalculatorAppTestCase, which inherits from the setup we just talked about.
[16:41] <balloons> cool, so let's talk a little about the actual helpers in the other __init__.py file
[16:41] <balloons> Autopilot itself works via introspection. It reads an applications dbus
[16:42] <balloons> that's why the setup and launch is needed to ensure we hook into this while running
[16:42] <balloons> to show you what I mean, let's use the autopilot3 vis tool to let you see how autopilot launches the app, and what it can see
[16:43] <viejotren> balloons: cool
[16:43] <balloons> inside the root of the branch you'll find ubuntu-calculator-app.qml. This is of course the main qml file for the app
[16:43] <balloons> you can run it via qmlscene, ala qmlscene ../../ubuntu-calculator-app.qml
[16:44] <balloons> this should start the application
[16:45] <viejotren> balloons: yes, now that app is running
[16:45] <balloons> Excellent. Go ahead and close it again. Now, let's have autopilot launch the application so we can visually examine it.
[16:46] <balloons> run this to launch the application again, but with the autopilot hook
[16:46] <balloons> autopilot launch -i Qt qmlscene ../../ubuntu-calculator-app.qml
[16:46] <balloons> you should see something like Testability driver loaded. Wire protocol version is "1.4".
[16:46] <balloons> finally, use the vis tool with autopilot to connect to the application and visual the dbus tree (just like autopilot). Do this by running autopilot3 vis
[16:48] <viejotren> yes, Testability driver is loaded correctly
[16:49] <viejotren> balloons: just a question: how to connect vis tool with autopilot and visual dbus tree?
[16:49] <balloons> viejotren, after the application is launched with the testability hook, you can simply launch autopilot3 vis and connect to it
[16:49] <balloons> after you launch autopilot3 vis you should see a dropdown box in the upper left
[16:50] <balloons> select comubuntucalcultor as the connection and you will see the tree
[16:50] <viejotren> balloons: ok, give me a minutes
[16:51] <balloons> viejotren, sure. Hopefully that all makes sense ;-)
[16:56] <viejotren> balloons, got it I can see the tree now
[16:59] <balloons> viejotren, excellent. So if you look under mainview, orientationhelper, appheader, etc you can get down into the details of the app
[16:59] <balloons> for instance you can see the simplepage object, etc
[17:00] <balloons> calckeyboard object, the screen and button objects
[17:00] <balloons> so at this point, you can learn a little about qml at least. The stuff in the tree is an object and on the right vis is showing the properties of the object selected
[17:00] <viejotren> balloons, I have access to the entire tree
[17:01] <viejotren> balloons, cool, so Autopilot Vis is like a code inspector, I'm checking it
[17:03] <balloons> viejotren, indeed. So excellent. Now when we write tests we can select objects you see in the tree
[17:04] <balloons> So for instance if we want to grab the SimplePage object we would issue a query like this. select_single('SimplePage').
[17:05] <balloons> viejotren, now we may want / need to be specific in the objects we grab. For instance, each button is the same objecttype in qml. They are all KeyboardButton. So to say get the '1' button, we need to select_single('KeyboardButton', objectName=oneButton)
[17:06] <balloons> you will notice select_single allows us to filter based on any property, so we could also get a button that is a certain color, or has a certain state
[17:07] <balloons> select_single also has a counterpart called select_many that does as expected; allows us to select more than one objecttype if we wish
[17:07] <balloons> this info is found here: http://developer.ubuntu.com/api/devel/ubuntu-14.10/python/autopilot/api/autopilot.introspection.html#autopilot.introspection.ProxyBase.select_single
[17:08] <viejotren> balloons: got it
[17:08] <balloons> viejotren, does that all make sense?
[17:09] <viejotren> balloons: almost, I would like to review the last part, but in general make sense
[17:09] <balloons> viejotren, excellent. So in general, we select the objects we want, then interact with them, and finally make assertions about those interactions to assure what we expected to happen actually did happen
[17:10] <balloons> like our multiplication test. We press the buttons to enter the calculation, then ensure the result is what we expect
[17:10] <viejotren> so the idea is to test object by object and document the results
[17:10] <viejotren> right?
[17:13] <balloons> viejotren, right. Our test cases generally align with user stories and features. But we organize things into what we call the Page-Object model (it's the same as what selenium does). So the calculator has this one page, SimplePage, and it's filled with objects. test_simple_page.py attempts to test all the user stories on that page
[17:14] <balloons> Anyways, I think you have enough info now to get your hands dirty and try writing / modifying a test. What do you think?
[17:14] <viejotren> balloons: absolutely, I would like to do it
[17:14] <balloons> rpadovani, you about?
[17:15] <viejotren> balloons: just a question: do you have some script/check list or something or may I write my own test as I want"
[17:15] <balloons> viejotren, we try and write tests to cover regressions, or add new features
[17:15] <balloons> since I chose calculator, I have something in mind for you :-)
[17:15] <balloons> viejotren, check out https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1392918
[17:17] <viejotren> balloons: great, I'll check it, here is what I will do: I will read again the last part you explained me (after autopilot vis) then the last to urls and then I'll start, agree?
[17:17] <balloons> viejotren, but yes you are also free to add tests that might be missing to any project. Sometimes you just see a missing test and add it
[17:18] <balloons> viejotren, I wouldn't worry about reading the full API docs or other links I gave you just yet. I would read at least the first part of http://developer.ubuntu.com/api/devel/ubuntu-14.10/python/autopilot/tutorial/tutorial.html, and plan to read the rest later
[17:19] <balloons> but of course, diving in and asking questions is good :-) I like to learn by doing
[17:19] <viejotren> balloons: great, I have available time, for me it's almost noon so I have the entire rest of the day to learn and work on it, if I have a question I'll let you know guys, ok?
[17:20] <viejotren> balloons: cool, I got the last url to start from it
[17:20] <balloons> viejotren, yes indeed. Don't be afraid to ask questions, I'm excitied to help get you started. Testing is fun :-)
[17:21] <viejotren> balloons: cool, thanks for all your help
[17:21] <balloons> you are most welcome!
[17:26] <akiva-thinkpad> https://www.youtube.com/watch?v=BlcTDz9ogug
[17:35] <ogra_> :D
[17:56] <rpadovani> balloons, sorry for late ping
[17:56] <rpadovani> Do you still need?
[17:58] <rpadovani> So, seems we have a new package format - snap. There is a plan to merge it with click or we will have two different packages for phone and cloud?
[18:12] <balloons> rpadovani, i was just wanting to ask about the calc reboot
[18:13] <rpadovani> balloons, it is doing great :D
[18:14] <balloons> rpadovani, well we had viejotren come by with some python skills, so I gave him a quick tutorial in autopilot and pointed him at calculator
[18:14] <rpadovani> balloons, oh, cool! But there is to setup infrastucture for the reboot, there is nothing about autopilot
[18:15] <balloons> well which branch should I check out?
[18:15] <rpadovani> balloons, https://code.launchpad.net/~ubuntu-calculator-dev/ubuntu-calculator-app/reboot
[18:16] <balloons> rpadovani, ack, thank you.
[18:16] <rpadovani> thanks to you
[18:16] <balloons> rpadovani, so for instance what will you do with old bugs like this? https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1392918
[18:16] <balloons> rpadovani, also, have you managed to file needed bugs yet?
[18:17] <rpadovani> balloons, I dunno tbh, we don't have yet change sign in the new calculator
[18:17] <rpadovani> balloons, no, I didn't open any bug yet
[18:17] <balloons> rpadovani, kk
[18:17] <balloons> I'd like to use the calculator to demo I think
[18:18] <balloons> so it would be nice to have some bugs to point out. I'll do the setup for the reboot branch as part of it
[18:33] <taiebot> Was wondering if anyone manage to reproduce joey's Chan App start up time improvement?  https://plus.google.com/communities/111350780270925540549
[18:35] <balloons> taiebot, not to my knowledge. did you check it out?>
[18:36] <taiebot> **taiebot's hide he is not a developper.
[18:38] <rpadovani> balloons, something like this one? https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1400828
[18:38] <rpadovani> mhh, title doesn't make much sense
[18:58] <sverzegnassi> hey akiva-thinkpad, +1 for the autopilot3-gui project!
[18:58] <akiva-thinkpad> sverzegnassi, thanks :P
[18:59] <akiva-thinkpad> sverzegnassi, do you know how to make items in QML be accessible via Unity7's hud?
[18:59]  * akiva-thinkpad will probably just stick with qt
[19:00] <sverzegnassi> sadly, no
[19:00] <akiva-thinkpad> ;_;
[19:00] <sverzegnassi> i just found something about ubuntu global menu on askubuntu that could be related, perhaps
[19:02] <sverzegnassi> http://stackoverflow.com/questions/21925052/qt5-2-qml-support-for-ubuntu-global-menu
[19:02] <sverzegnassi> akiva-thinkpad: maybe it could help you ^^
[19:02] <akiva-thinkpad> sverzegnassi, +1
[19:24] <balloons> rpadovani, that's a good start
[19:25] <balloons> rpadovani, do you otherwise want the current suite replicated? if so, a bug for that :-)
[20:12] <rpadovani> balloons, mhh, not really, only for calculator engine tests, not the UI thinks (like scroll up to save a calc)
[20:13] <rpadovani> I could open a bug for things I want to duplicate :-)
[20:14] <balloons> rpadovani, yep, that would be most excellent
[20:15] <rpadovani> balloons, great, do I report only a bug with a list of tests? Or one for every test?
[20:16] <balloons> rpadovani, ideally you would match up tests that you want with bugs in a one to one manner. However if you want to group them a little, go for it. Try not to make just one bug report for everything as that cannot be easily divided up or accomplished in one merge
[20:16] <rpadovani> gotcha thanks!
[20:40] <sverzegnassi> balloons: ping
[20:42] <balloons> sverzegnassi, pong
[20:43] <sverzegnassi> I was looking for this bug: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1188764
[20:43] <sverzegnassi> Since I join the docviewer team in October, I'm still not sure if the report is still valid or not.
[20:44] <balloons> sverzegnassi, yes I think the docviewer tests need a little love to bring them up to speed
[20:45] <balloons> it's possible the bug is no longer relevant.. I know I can scroll through a pdf, but last I checked there were no buttons to do so
[20:45] <sverzegnassi> yep, so should I marked it as "won't fix"?
[20:48] <balloons> sverzegnassi, um, actually invalid is probably better
[20:48] <balloons> but yes, please do
[20:49] <balloons> sverzegnassi, while we are at it, we could review to make sure there's bugs for needed tests
[20:49] <sverzegnassi> balloons: I was starting to do that right now :D
[20:50] <balloons> sverzegnassi, awesome!
[20:50]  * balloons high fives sverzegnassi 
[20:50] <sverzegnassi> At the moment, we're surely missing a test for the "go to page" dialog
[20:51] <sverzegnassi> I've also open this report: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1188764
[20:52] <balloons> sverzegnassi, if you do tag new tests, please do add the 'needs-autopilot-test' tag so it's tracked easier
[20:54] <sverzegnassi> balloons: Ok, I'll do it! This is just a fix-request, should I use it the 'needs-autopilot-test' anyway?
[20:55] <balloons> sverzegnassi, yea, anything autopilot related. It helps make sure it shows up on the master list, which I search for by that tag
[20:57] <sverzegnassi> balloons: Great! Thank you for you help!
[21:01] <alci> hi here. I have a question about ubuntu-sdk. On 14.10, is apt-get install ubuntu-sdk sufficient to get up and running?
[21:01] <timp> alci: yes
[21:01] <alci> doc on developer.ubuntu.com say install a ppa, but this is for 14.04, no mention of 14.10...
[21:02] <timp> alci: you don't need the ppa on 14.10
[21:03] <alci> thanks timp.
[21:03] <balloons> alci, I can open a bug / fix developer.u.c. Where does it fail to mention 14.10?
[21:03] <balloons> that way no one else will be confused :-)
[21:04] <alci> here: http://developer.ubuntu.com/start/ubuntu-sdk/installing-the-sdk/
[21:08] <alci> Ok, now here is my problem: I create a test project from scratch using 'App with simple UI and localization'
[21:09] <alci> but when trying to build (click on hammer in bottom left corner), I get: No targets specified and makefile found. Stop.
[21:10] <ahayzen> alci, did you configure the project to include kits?
[21:11] <balloons> alci, I updated that page, hopefully it is now clear. Thanks!
[21:11] <alci> yes, I clicked on the three of them. But I might have a problem with that, as using ubuntu-emulator create outside of qtcreator fails...
[21:12] <ahayzen> hmm but the desktop one should work?
[21:12] <alci> you're right, the desktop one works.
[21:13] <alci> but, can I make a click package with desktop target and upload that on the store (for devices ?) ?
[21:15] <alci> Just tried, I obviously can't (option to create a click package is greyed out when choosing desktop kit)
[21:20] <rpadovani> kalikiana, ping about u1db :-)
[21:21] <balloons> sounds weird alci. go maintain the kits and see what you have
[21:23] <sverzegnassi> alci: could you check if "intltool" package is installed in your development kit?
[21:24] <sverzegnassi> If I remember well, I had a similar issue with it
[21:25] <sverzegnassi> Open Tools >> Options... >> Ubuntu
[21:25] <sverzegnassi> Click on "Maintain" the kit, and then type "apt-get install intltool"
[21:29] <rpadovani> balloons, I'll add others in next days
[21:29] <rpadovani> https://bugs.launchpad.net/ubuntu-calculator-app/+bugs?field.tag=needs-autopilot-test
[21:29]  * balloons looks
[21:29] <alci> sverzegnassi: ok. intltool was not installed indeed.
[21:30] <balloons> woot, ty rpadovani
[21:30] <sverzegnassi> alci: Awesome! We have probably found the issue!
[21:30] <rpadovani> balloons, thanks to you if you find someone that implement them, as you know I don't like to play with autopilot :P
[21:31] <sverzegnassi> Install it, then close and re-open ubuntu-sdk, just to be sure the project is correctly opened
[21:31] <balloons> rpadovani, there was someone interested today, so I hope they return :-)
[21:31]  * ahayzen pretends he hasn't been enjoying autopilot lately 
[21:32] <alci> sverzegnassi: yes, it now works ! thanks a lot.
[21:32] <sverzegnassi> alci: You're welcome!
[21:34] <rpadovani> sweet!
[21:35] <alci> bye. thanks.
[21:35] <rpadovani> Sooo, I have a very strange problem with U1DB - when I do a query on index it returns index in a strange order, like 10 100 101 11 111 112 12
[21:35] <rpadovani> See this screenshot
[21:35] <rpadovani> http://people.ubuntu.com/~rpadovani/docId.png
[21:35] <rpadovani> results of the calcs are ID of the documents
[21:36] <sverzegnassi> rpadovani: are you using SortFilterModel?
[21:36] <rpadovani> sverzegnassi, yap
[21:36] <sverzegnassi> rpadovani: It does not sort U1DB queries at the moment
[21:37] <rpadovani> sverzegnassi, ok thanks, do you have a bug about this - or a workaround?
[21:38] <sverzegnassi> I know there is a bug report around launchpad, just a moment that I look for it
[21:38] <sverzegnassi> (no workaround anyway - unless you fill a ListModel with your queries)
[21:39] <sverzegnassi> An autopilot testcase is needed to test PDF zooming
[21:39] <sverzegnassi> sorry Ctrl+C sometimes fails :P
[21:39] <sverzegnassi> https://bugs.launchpad.net/u1db-qt/+bug/1266529
[21:40] <sverzegnassi> rpadovani ^^
[21:40] <rpadovani> sverzegnassi, thanks