[06:31] <mihir_> Good Morning Aall :)
[06:54] <Hargard> for those ubuntu developers out there am in college and ave decided to give it a go
[06:55] <Hargard> how do i go about it  ??
[06:57] <Nimble> Hargard, about what
[06:57] <Nimble> developing for ubuntu?
[07:02] <mihir_> Nimble: Hi, Thank you for interest
[07:02] <mihir_> Nimble: Are you interested in developing?
[07:03] <Nimble> mihir_, yes, a bit
[07:03] <Nimble> originally I came here because the instructions on using the messaging menu in the docs didn't seem to work
[07:03] <mihir_> Nimble: Okay, you can start doing resolving bugs..
[07:04] <Nimble> well, why not
[07:04] <Nimble> I take it I should probably sign up for launchpad
[07:04] <mihir_> you can look visit this link http://developer.ubuntu.com/2013/07/join-the-ubuntu-touch-core-apps-development-team/
[07:04] <mihir_> Yup, you should do that first
[07:04] <Nimble> alright, will do.
[07:07] <mihir_> Nimble:  :)
[07:10] <dholbach> good morning
[07:19] <zsombi> oSoMoN: ping
[07:21] <Nimble> mihir_, will this work with my ubuntu single sign on?
[07:21] <Nimble> and if I have one, will it not allow me to use my email address registered to that?
[07:24] <mihir_> Nimble: yes , you should use one email across the ubuntu :)
[07:24] <Nimble> alright, my single sign on worked
[07:24] <Nimble> so that's good
[07:27] <mihir_> Nimble:  That's great it worked :)
[07:35] <oSoMoN> zsombi: pojng
[07:35] <oSoMoN> pong
[07:36] <zsombi> oSoMoN: jenkins did the job now, you have the deb packages there :)
[07:36] <oSoMoN> zsombi: awesome, I’ll test right away
[07:37] <mihir_> dpm: Good Morning :)
[07:44] <dpm> morning mihir_ and all
[07:46] <mihir_> dpm: Hi , I have proposed two MRs could you please review if you have time
[08:06] <oSoMoN> zsombi: do you know if the uitk’s autopilot tests can be run on devices?
[08:07] <zsombi> bzoltan: ^
[08:07] <bzoltan> oSoMoN: It should be OK
[08:09] <oSoMoN> bzoltan, zsombi: I’m getting the following error when trying to run them on maguro: http://pastebin.ubuntu.com/5954209/
[08:10] <zsombi> oSoMoN: bzoltan: no idea what can this be...
[08:10] <oSoMoN> also getting an error on stdout about gcc not found…
[08:11] <oSoMoN> installed gcc and this error went away, but not the runtime error
[09:20] <nerochiaro> gusch: hi, i think i asked you already, but forgot the answer: can we find out if the currently active camera has light (torch/flash) support ?
[09:20] <nerochiaro> gusch: also, how to find out the number of cameras on the current device
[09:21] <gusch> nerochiaro: for the number of camera, you need to use the same class, that you use to switch cameras
[09:21] <gusch> nerochiaro: http://qt-project.org/doc/qt-5.0/qtmultimedia/qvideodeviceselectorcontrol.html#deviceCount
[09:22] <mihir_> dpm: Ping !!
[09:24] <gusch> nerochiaro: need to check the best way to get the flash information
[09:25] <nerochiaro> gusch: ok. do you only have a galaxy nexus, right ?
[09:25] <gusch> nerochiaro: and the N10
[09:25] <nerochiaro> gusch: ok, but no n7, which apparently has only one camera
[09:27] <nerochiaro> oSoMoN: timp: to store configuration info, are we currently using dconf or something else ?
[09:27] <gusch> nerochiaro: nope
[09:28] <oSoMoN> nerochiaro: dunno
[09:36] <zsombi> nerochiaro: we have an AP in the SDK to provide API for gsettings/dconf, so that will be the one you should use... when it will be ready
[09:37] <gusch> nerochiaro: for the focus you can use this one http://qt-project.org/doc/qt-5.0/qtmultimedia/qml-qtmultimedia5-camerafocus.html#isFocusModeSupported-method
[09:37] <nerochiaro> zsombi: so what should i do now ?
[09:37] <nerochiaro> zsombi: i mean, in the meantime before it's ready ?
[09:37] <zsombi> nerochiaro: yes, I got it :)
[09:38] <zsombi> nerochiaro: well, do something :)
[09:38] <nerochiaro> gusch: don't need it for focus ATM, only num of cameras and flash modes
[09:38] <nerochiaro> gusch: but thanks
[09:38] <nerochiaro> zsombi: ok, use whatever for now then when your stuff is ready use that. fair enough
[09:38] <gusch> nerochiaro: for flash you'll need to use C++, and I'll have to update the plugin to do this: "Some camera devices may not have flash hardware, or may not be configurable. In that case, there will be no  QCameraFlashControl available."
[09:39] <nerochiaro> gusch: that will work fine for me
[09:40] <zsombi> nerochiaro: :) yep... We were trying to find out whether we could put under QSettings and provide QML binding to QSettings, but it ended up that Qt guys are planning something new and don't really want to see any backend added to QSettings anymore :/
[09:43] <zsombi> nerochiaro: does the notes patch work? were you able to test it?
[09:46] <nerochiaro> zsombi: what patch ? missing something here
[09:46] <zsombi> (12:32:26 PM) zsombi: nerochiaro: set propagateComposedEvents: true to the MA which activates the note card, also mouse.accepted = false in onClicked
[09:47] <nerochiaro> zsombi: ah, let me try that
[09:48] <nerochiaro> zsombi: in addition also propagateComposedEvents: true on the IMA, right ?
[09:49] <zsombi> nerochiaro: yes, this is needed as the "inactive" card MA may be higher in the paint order, so that also needs to propagate the composed events
[09:49] <nerochiaro> zsombi: ok, giving it a shot
[09:52] <nerochiaro> zsombi: ok, seems to work. i'll submit an MR
[09:52] <zsombi> nerochiaro: awesome!!! :)
[09:52] <nerochiaro> zsombi: :9
[09:53] <nerochiaro> zsombi: btw, is it normal that on the latest image when i drag the launcher all the way across to reveal the apps lens, the dash is completely transparent and shows the running app underneath ?
[09:53] <nerochiaro> zsombi: it's new in today's image
[09:54] <zsombi> nerochiaro: no idea, don't have my device woken up yet...
[09:56] <nerochiaro> zsombi: zzzzz
[09:57] <zsombi> :)
[09:57] <zsombi> nerochiaro: I've set it on charger, but it is still dead
[09:59] <nerochiaro> zsombi: shut it down before going to bed ;)
[09:59] <zsombi> nerochiaro: I thought that it was, as when I pressed the power button it aint woke up... :)
[10:02] <nerochiaro> zsombi: happens to me all the time
[10:02] <nerochiaro> zsombi: i think we need a more reliable shutdown mechanism
[10:03] <zsombi> nerochiaro: and a safety power-off, which turns off the device when the battery dries down to 3%, so a possible wake-up c an be done afterwards safely
[10:06] <nerochiaro> zsombi: yeah
[10:09] <AskUbuntu> I want to create .dmg file from my source file on ubuntu so that I can distribute it on mac? | http://askubuntu.com/q/329249
[10:13]  * zsombi lunch
[10:43] <Mirv> bzoltan: re: http://pad.lv/1202207 dpm e-mailed about... I remember some past hud discussion with Wellark, what was the end results? I thought it would be compiled in SDK PPA for older Ubuntus or something like that.
[10:43] <ubot2`> Launchpad bug 1202207 in Dropping Letters "12.04 install problems" [Undecided,New]
[10:46] <nerochiaro> zsombi: https://code.launchpad.net/~amanzi-team/notes-app/notes-app-event-propagation/+merge/178714
[10:46] <zsombi> nerochiaro: checking...
[10:46] <nerochiaro> zsombi: haven't run the tests yet, i'll try that now on the device
[10:47] <zsombi> nerochiaro: ok
[11:05] <nik90|Office> mhall119: ping
[11:06] <nik90|Office> seb128: ping
[11:15] <seb128> nik90|Lunch, context less ping = no pong usually (just saying)
[11:16] <nik90|Lunch> seb128: oh
[11:16] <nik90|Lunch> :)
[11:17] <nik90|Lunch> seb128: so I saw that in the system settings app, you guys show the timezone info "Europe/Amsterdam" etc..Is that just a mockup string? Or do you guys actually read the system timezone info?
[11:17] <seb128> nik90|Lunch, having "ping" without context is a trap, sometime you don't have time for a long discussion so you just default to ignore the ping to not be trapped
[11:17] <seb128> nik90|Lunch, we read the tz
[11:17] <nik90|Lunch> seb128: How do you do that? Did you create a custom C++ plugin to read the tzdata file?
[11:20] <nik90|Lunch> seb128: I need that same info for the clock app. However since the clock app is all javascript and qml, I am unable to get the timezone ID info. So before I start writing my own custom C++ plugin to do that, I wanted to know if other apps like the system app did that already to prevent code duplication unnecessarily.
[11:20] <seb128> nik90|Lunch, yes, http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/view/head:/plugins/time-date/timedate.cpp
[11:20] <mihir_> dpm:  ping !!
[11:21] <seb128> nik90|Lunch, that seems like something useful enough, that we should have a sdk api for it imho
[11:22] <nik90|Lunch> seb128: I agree. However I am not really sure when that would be implemented since all sdk devs are quite busy. And I need this info asap :(
[11:22] <seb128> nik90|Lunch, right, you probably better copy what we are doing meanwhile
[11:23] <nik90|Lunch> seb128: yeah. thnx for getting the info for me
[11:23] <seb128> yw!
[11:23] <mihir_> mhall119: Ping !!
[11:24] <seb128> nik90|Lunch, hum, maybe https://github.com/nemomobile/nemo-qml-plugin-time/tree/master/src would be an option as well
[11:27] <seb128> nik90|Lunch, their current backend is for meego though
[11:32] <kalikiana> seb128: be sure to file a bug with the sdk that points at your branch, it might speed up development once it happens ;-)
[11:33] <seb128> kalikiana, what project is the right one for those sort of apis?
[11:33] <nerochiaro> zsombi: tests are also successful on device (on top of jenkins being happy about them). maybe i should add another ap test for this specific case
[11:34] <zsombi> nerochiaro: excellent! an extra test is always welcome
[11:34] <zsombi> nerochiaro alos, the code looks right, so I'll approve from my side, but let's wait till timp approves it
[11:35] <nerochiaro> zsombi: ok
[11:39] <oSoMoN> hey gusch|lunch, when you get back from lunch, could you please review https://code.launchpad.net/~osomon/webbrowser-app/simplify-historydomainlistmodel/+merge/178687 ? I already ran the autopilot tests on maguro, they all pass
[11:41] <gusch> oSoMoN: what a timing ;) - I review ...
[11:41] <oSoMoN> thanks :)
[11:50] <kalikiana> seb128: just file it in the sdk, it's easy to move, and it'd depend on what other api it might relate to. just timezone data won't be its own component
[11:51] <kalikiana> it might also coincide with zsombi's alarm stuff
[11:51] <kalikiana> s/coincide/fit/
[11:57] <gusch> oSoMoN: approved
[11:58] <oSoMoN> gusch: awesome, thanks, I’ve got a couple more MRs in the pipe, waiting to run autopilot tests on device before requesting a review
[11:59] <gusch> oSoMoN: keep them going ;)
[12:00] <zsombi> kalikiana: seb128: hehe, the github branch you've pointed actually connects to timed, the one we were suggesting to port to Ubuntu, as that handles all the time related stuff (including proper NITZ support with all its exceptions) + alarms...
[12:00] <zsombi> but seems we will do a different adaptation and have a different approach for that...
[12:02] <nik90|Office> zsombi: Should I go about writing my own C++ plugin to get system timezone ID or will this come as part of the alarm package?
[12:02] <nik90|Office> zsombi: I need to make a decision depending on when a suitable API might land in the sdk for it
[12:04] <zsombi> nik90|Office this may not come as part of the alarm API as this is more related to time management, but we may create a separate API for Time management. I say may, as currently we don't have any API planned for that. But you could always contribute to the SDK by offering to do such an API ;)
[12:04] <oSoMoN> gusch: next one: https://code.launchpad.net/~osomon/webbrowser-app/blank-thumbnails/+merge/178716
[12:04] <gusch> oSoMoN: ok
[12:06] <nik90|Office> zsombi: I would love to help but I am learning qml/c++ as I go. So what I implement may not have sdk standards and would rather be suited for an app instead.
[12:06] <nik90|Office> That said I will give it a shot and see where it leads me
[12:06] <zsombi> nik90|Office don't be afraid, we can help on that! :)
[12:07] <nik90|Office> zsombi: I will let you know when I have a working branch
[12:08] <zsombi> nik90|Office cool!! thx!
[12:18] <nerochiaro> om26er: is there any way in autopilot tests to wait for an animation to finish ?
[12:18] <nerochiaro> oSoMoN: maybe you know that too ? ^
[12:19] <om26er> nerochiaro, most of the times, object.animating is what you need to assert
[12:19] <nerochiaro> om26er: oSoMoN: the reason i ask is because i need the animation to finish to get the new geometry of the object so that i can click in the right place for my test
[12:19] <nik90|Office> om26er: I reviewed your autopilot branch fix for clock app.
[12:20] <om26er> there are also cases where object.moving is used as well, but that's mostly when the page stack is being moved etc.
[12:20] <nerochiaro> om26er: object.animating does not exist
[12:20] <oSoMoN> nerochiaro: you may need to add an animating property to the object, and wait for it to become false
[12:21] <oSoMoN> nerochiaro: look for example at the SDK’s Panel implementation, it has an 'animating' property
[12:21] <nik90|Office> om26er: I see that we continue to use our own custom toolbar emulator function. Should we convert that to use elopio's emulator function now or in a later commit?
[12:21] <nerochiaro> oSoMoN: adding properties only for the sake of tests does not seem very clean
[12:21] <om26er> nik90|Office, I think doing that in an other branch will be better, also I will fix the problems you highlighted today
[12:22] <oSoMoN> nerochiaro: you asked for a solution, I’m sharing the only solution I know
[12:22] <nik90|Office> om26er: okay
[12:22] <om26er> nerochiaro, which type of object is that ?
[12:22] <nerochiaro> oSoMoN: sure, i wasn't complaining for the sake of complaining, i was trying to get a discussion running. it's an ok workaround if nothing else is available.
[12:23] <oSoMoN> gusch: next MR: https://code.launchpad.net/~osomon/webbrowser-app/cosmetics/+merge/178725
[12:23] <om26er> In cases I have used .animating or .moving and also 'swipeState' depending on the type of object I am interacting with
[12:23] <om26er> nerochiaro, ^
[12:23] <nerochiaro> om26er: it's one of the notes in notes-app. i need to wait for the expanding animation to finish before it settles on a stable geometry
[12:23] <nerochiaro> om26er: so i can continue with the rest of the test
[12:24] <nerochiaro> om26er: oh, but wait, i think i have a property that represents the final height, and i animate towards that. so i can just check if height eventually equals final_height and that should work
[12:24] <oSoMoN> nerochiaro: you could probably write a custom matcher that waits for the height to be stable, i.e. not changing during a certain interval of time, but that sounds way more hackish than the other solution
[12:24] <oSoMoN> nerochiaro: yep, height == final_height looks like the cleanest solution so far
[12:24] <nerochiaro> oSoMoN: ok let's try that
[12:26] <om26er> nerochiaro, you could tests the state of the NoteItem, it has collapsed and expanded
[12:27] <om26er> *test
[12:27] <nerochiaro> om26er: was my first idea, but it doesn't work because the state changes immediately and then the animation is triggered, as far as I can see
[12:28] <om26er> nerochiaro, there is also 'isExpanded'
[12:28] <nerochiaro> om26er: same problem with that
[12:28] <nerochiaro> oSoMoN: om26er: the height test works, i'll use that. thanks for the input
[12:29] <om26er> cool
[12:34] <gusch> oSoMoN: cosmetics approved
[12:40] <gusch> oSoMoN: thumbnails approved as well
[12:47] <oSoMoN> gusch: thanks!
[12:48] <nerochiaro> zsombi: added more autopilot tests to https://code.launchpad.net/~amanzi-team/notes-app/notes-app-event-propagation/+merge/178714
[12:53] <om26er> nerochiaro, gusch if I turn on autopilot tests for camera-app for each merge proposal do you mind ?
[12:53] <om26er> I'll keep fixing if we face any blockers along the way
[12:54] <om26er> *On Maguro and Mako I meant
[12:56] <nerochiaro> om26er: well, what's the current status ? will it fail if you do turn it on ?
[12:56] <om26er> nerochiaro, currently they are passing as seen on daily image testing
[12:56] <gusch> om26er: is it possible to enable the camera-app autopilot tests for the qtubuntu-camera as well?
[12:57] <om26er> gusch, it should be, I can look into that. never tried qtubuntu-camera suite
[12:58] <gusch> om26er: would be cool if you could try to do that at one point (no hurry)
[12:59] <om26er> gusch, sure
[13:03] <seb128> zsombi, great, is there a bug/blueprint/somewhere I can see what's going on about this timed?
[13:12] <nerochiaro> om26er: then go ahead with that ,i have no problem
[13:12] <om26er> nerochiaro, ok, thanks
[13:48] <mihir_> boiko: could help me regarding this bug ?https://bugs.launchpad.net/ubuntu-calculator-app/+bug/1205020
[13:48] <ubot2`> Ubuntu bug 1205020 in Ubuntu UI Toolkit "functionality for copying result in clipboard" [Undecided,Confirmed]
[13:48] <mihir_> Still design team needs to approve it
[13:49] <boiko> mihir_: I think for this one what you need to do right now is to wait for something to be provided by the UI Toolkit team
[13:50] <mihir_> boiko: Okay thank you :)
[14:36] <nerochiaro> zsombi: can we top approve https://code.launchpad.net/~amanzi-team/notes-app/notes-app-event-propagation/+merge/178714 as jenkins likes my new tests and they pass on the device too ?
[14:56] <iBelieve> mhall119, ping
[15:00] <mhall119> iBelieve: pong
[15:00] <iBelieve> mhall119, I've got a question about merge requests for File Manager
[15:02] <iBelieve> mhall119, I was reading the backlog for the last meeting (I wasn't their), and Arto  said he doesn't have much time for development except for responding to emails. I've had a merge request that's been waiting for a long time. Should I have somebody else, like you or popey, review it? Or should I just approve it myself?
[15:05] <mhall119> iBelieve: I'll take a look, can you link me to the MP?
[15:05] <iBelieve> mhall119, I'm going to make a few changes to the old merge request (https://code.launchpad.net/~mdspencer/ubuntu-filemanager-app/advanced-options), but you could take a look at the new one (https://code.launchpad.net/~mdspencer/ubuntu-filemanager-app/sidebar/+merge/178774)
[15:06] <mhall119> iBelieve: I'm in a meeting atm, but I'll look at them after
[15:07] <iBelieve> mhall119, thanks. Also, I just checked on the first merge request that I linked (advanced-options), and that's ready to be reviewed, I'm not going to make any changes.
[15:09] <gusch> nerochiaro: ping
[15:09] <nerochiaro> gusch:
[15:10] <nerochiaro> gusch: hi
[15:10] <gusch> nerochiaro: about detecting flash support
[15:10] <gusch> nerochiaro: you should check it a bit different
[15:11] <gusch> nerochiaro: it's not possible to dynamically add/remove the C++ flashControl object (so that QML detects it)
[15:12] <gusch> nerochiaro: so get in C++ the QCameraFlashControl
[15:12] <gusch> nerochiaro: and there use bool QCameraFlashControl::isFlashModeSupported(QCameraExposure::FlashModes mode)
[15:12] <gusch> nerochiaro: as mode use QCameraExposure::FlashOn - if that is supported, than a flash exists ...
[15:13] <gusch> nerochiaro: is that ok?
[15:14] <nerochiaro> gusch: ok, i guess that doesn't tell me if a torch mode exists, i have to check that separately. other than that it works ok for me
[15:14] <gusch> nerochiaro: yep - that should be checked separately
[15:17] <gusch> nerochiaro: you need to have a running camera to get the correct values btw.
[15:20] <nerochiaro> gusch: running as in initialized properly
[15:20] <gusch> nerochiaro: yep
[15:26] <zsombi> seb128: we don't have blueprint for timed as we didn't do anything from SDK side. All we have is a BP for Alarm API, but that's not really related to the time functionality you have pasted from github
[15:27] <seb128> zsombi, I looked at timed, it doesn't seem to do stuff like system tz handling (or I looked at the wrong place for it)
[15:27] <zsombi> nerochiaro: I'm affraid to top-approve that as may introduce regressions without my MR approved.
[15:28] <zsombi> seb128 it does, it handles alarms and also has NITZ support.
[15:28] <iBelieve> timp, ping
[15:29] <gusch> nerochiaro: can you review this? https://code.launchpad.net/~schwann/qtubuntu-camera/qtcamera-vp-flash/+merge/178784
[15:29] <seb128> zsombi, NITZ is not system timezone though, it wouldn't work on a tablet or desktop
[15:32] <zsombi>  seb128 it does if the tablet has GSM module in it. NITZ however helps you keep the time zone in sync when traveling or when the daylight saving starts/ends. So that one we also need to check, perhaps not in our time backend in SDK, but somewhere in the system. So far I know there is some work done around NITZ somewhere else in the stack...
[15:32] <zsombi> seb128: so whatever is needed right now for the clock, we don't have any BP/API planned. But we definitely need one
[15:32] <seb128> zsombi, right, I'm not saying NITZ it's not useful, it's only a piece of the puzzle though
[15:32] <timp> iBelieve: pong
[15:32] <zsombi> seb128: +1
[15:33] <iBelieve> timp, could you explain the reasoning for marking LP #1202469 as Invalid?
[15:33] <ubot2`> Launchpad bug 1202469 in Ubuntu UI Toolkit "Actions should be hidable " [Undecided,Invalid] https://launchpad.net/bugs/1202469
[15:34] <iBelieve> timp, I'm working on advanced options for File Manager and need a way to make actions hidden.
[15:36] <timp> iBelieve: hold on, let me see
[15:36] <zsombi> seb128: timed is mostly there to handle and schedule alarms, keep those in sync with the system time changes + NITZ changes, and also handles when to play alarm sound (there are quite many exceptions, like when in a call, when multimedia plays, etc)
[15:37] <seb128> zsombi, ok, it seems a bit orthogonal to the set manually time/date/timezone, use ntp features (which are more desktopish)
[15:44] <nerochiaro> zsombi: ping
[15:44] <zsombi> nerochiaro: pong
[15:44] <nerochiaro> zsombi: can we top approve https://code.launchpad.net/~amanzi-team/notes-app/notes-app-event-propagation/+merge/178714 as jenkins likes my new tests and they pass on the device too ?
[15:45] <zsombi> nerochiaro: so it doesn't bother it with the MA event propagation?
[15:46] <nerochiaro> zsombi: what do you mean ?
[15:47] <timp> iBelieve: where do you use the Action? In the toolbar?
[15:47] <zsombi> nerochiaro: these changes you did were because the IMA changes. Do these changes work without any problems with the SDK from archive?
[15:48] <iBelieve> timp, I was planning on having the Actions in an ActionSelectionPopover. For example, I was going to have an "Open in Terminal" action that is only shown when the user has set a setting that shows advanced features.
[15:48] <nerochiaro> zsombi: ah, i don't know. i tested them with the sdk from your branch
[15:48] <nerochiaro> zsombi: but it seems jenkins thinks they are ok with the sdk from archive as well
[15:49] <zsombi> nerochiaro: ok, so let's approve this, then timp can approve IMA MR afterwards
[15:50] <timp> iBelieve: for the toolbar we replaced the Actions by a visual representation of actions (ToolbarButton) that has the visible property now
[15:51] <timp> iBelieve: I don't think we have a visual representation for the actions in the ActionSelectionPopover yet.
[15:51] <timp> zsombi: you wrote the ActionSelectionPopover? Is that still a recommended component to use?
[15:52] <timp> iBelieve: I'm reading the docs for ActionSelectionPopover now, I'm not familiar with it
[15:52] <zsombi> timp: why not? it gets a list of actions and displays them. However can be modified to work better with the new Action stuff
[15:53] <nerochiaro> zsombi: ok cool
[15:53] <nerochiaro> zsombi: thanks
[15:53] <iBelieve> timp, why are you saying that the visible property should be part of the visual representation of an Action (such as a ToolBarButton)? To me, it seems like it should be part of the Action itself.
[15:56] <timp> iBelieve: we don't have our "own" Actions in the SDK any more, but we use them from Unity.Actions. Those actions are integrated with HUD and will be with the launcher
[15:57] <timp> iBelieve: we had some discussions about the "visible" property, and I used to share your opinion.
[15:58] <timp> iBelieve: probably we'll need a visual representation for actions in an actionselectionpopover
[15:59] <iBelieve> timp, so why isn't there a visible property anymore? I'm just curious :)
[16:00] <timp> iBelieve: well, for the HUD, the idea is that it can show the user all the possible available actions
[16:01] <timp> iBelieve: and for other uses (toolbar), we thought that the ActionItem/ToolbarButton would take care of it
[16:02] <timp> iBelieve: your case still needs some thoughts
[16:02] <timp> Wellark: ^ do you have any suggestions for the visibility of actions in an ActionSelectionPopover?
[16:02] <iBelieve> timp, that makes sense, somewhat, though it seems like Actions could still have a visible property and be shown no matter what in the HUD.
[16:03] <iBelieve> timp, anyway, what should I do for an ActionSelectionPopover? Is there a way to do what I want now, or do I need to wait for support in it?
[16:05] <timp> iBelieve: you can specify the delegate of the ActionSelectionPopover, of that you can set the visible property.
[16:05] <timp> iBelieve: if you use action.enabled, you can say visible: action.enabled in the delegate
[16:06] <timp> zsombi: in the docs for ActionSelectionPopover, it says:           text: action.text
[16:06] <timp> zsombi: shouldn't that be text: item.text ?
[16:06] <iBelieve> timp, that might work, I'll try it. Thanks for your explanation of the reasoning behind the bug and for help with a solution
[16:07] <timp> iBelieve: thanks for making me doubt our previous decision to remove visible ;)
[16:07] <iBelieve> timp, :)
[16:08] <zsombi> timp: no, because that delegate is the component which is used to show the action, and the "action" itself is the property from the Standard
[16:09] <timp> zsombi: ah yes, ListItem.Standard has an action property. Then setting the text here does nothing (it is action.text by default)
[16:09] <zsombi> timp: huhh??
[16:10] <Wellark> timp, iBelieve: so, the rationale here is that Action is separated from it's visualization
[16:10] <timp> zsombi: what huh?
[16:10] <zsombi> timp: I was looking after this action property :)
[16:10] <zsombi> timp: but that has been moved to AbstractButton
[16:11] <timp> zsombi: no
[16:11] <timp> zsombi: to ActionItem, the parent of AbstractButton :)
[16:11] <zsombi> timp: actually AbstractButton is derived from ActionItem :)
[16:11] <zsombi> timp: right
[16:11] <timp> zsombi: many of our components are now derived from ActionItem
[16:11] <zsombi> timp: and that's right!
[16:12] <Wellark> Action is an abstract entity describing the functionality the application can do and when it's visualized you always assosiate the action with some form of delegate
[16:15] <Wellark> this allows a single action to be shared or contributed between different UI and shell elements and each delegate has a separate visibility property
[16:15] <Wellark> or optional visibility propertyy if it makes sense
[16:19] <iBelieve> Wellark, timp, so is there an easy way to control the visibility of an Action in an ActionSelectionPopover without a custom delegate? timp suggested visible: action.enabled, but I think that would require a custom delegate?
[16:20] <Wellark> iBelieve: I might be using the term delegate ambiguously
[16:20] <Wellark> I haven't looked in to ActionSelectionPopover yet
[16:20] <timp> iBelieve: does it work if you add "delegate.visible: action.enabled" to set the visible property of the standard delegate?
[16:20] <Wellark> iBelieve: that ^  sounds reasonable
[16:21] <timp> Wellark: ActionSelectionPopover has a property Component delegate which is used in the Repeater that visualizes the Actions
[16:21] <Wellark> if your action is not enabled then it's invisible
[16:21] <iBelieve> Wellark, timp: QML won't let me do sub-properties like that :(
[16:23] <iBelieve> Wellark, timp: maybe it would, but it doesn't show that property since it is a Component, not an Empty
[16:28] <timp> iBelieve: ah yes, I think you're right
[16:28] <iBelieve> timp, I tried using another property like property Empty delegate2: delegate, and then used delegate2.visible, but then QML said Invalid property nesting
[16:30] <timp> iBelieve: actually the delegate is very simple: http://pastebin.ubuntu.com/5955564/
[16:31] <iBelieve> timp, I suppose I'll just copy it if there is no better way, but I never like to duplicate code, especially if the original is in the SDK and subject to change.
[16:32] <timp> iBelieve: I agree, it is better not to copy code. But like this you can continue working on it now
[16:33] <iBelieve> timp, right, that's what I'll do. Thanks for all the help!
[20:32] <akakist> Hi
[20:32] <akakist> I cannot enter payment information into profile while trying to submit app
[21:45] <iBelieve> balloons, ping
[21:46] <balloons> iBelieve, pong.. I wanted to chat with you :-)
[21:46] <iBelieve> balloons, about LP #1208999?
[21:46] <ubot2`> Launchpad bug 1208999 in Ubuntu File Manager App "Cannot paste a file on desktop or device" [Undecided,New] https://launchpad.net/bugs/1208999
[21:46] <balloons> iBelieve, indeed. that and https://bugs.launchpad.net/autopilot-qt/+bug/1209004 are the only failing tests on the device
[21:46] <ubot2`> Ubuntu bug 1209004 in Autopilot Qt Support "Process Manager tries to call Xlib on phablet devices" [Undecided,New]
[21:47] <iBelieve> balloons, so does copying and pasting work on the desktop?
[21:47] <balloons> iBelieve, no.. I can't get it to work at all
[21:47] <balloons> no matter what device I use :-)
[21:48] <iBelieve> balloons, does the Actions popover popup in the center of the app, or does it popup from the Actions button?
[21:48] <balloons> center of app on desktop, causing issues
[21:48] <balloons> from the popover on the device I think..
[21:48] <balloons> it's odd.. it's not the same failure depending on how you do it
[21:49] <iBelieve> balloons, the reason it centers is because of how the popover gets opened in code. I fixed that, but I'm getting errors about the copy and cut functions not existing.
[21:49] <iBelieve> balloons, can you try lp:~mdspencer/ubuntu-filemanager-app/sidebar and see if that works?
[21:50] <iBelieve> balloons, though wait a sec until I push more changes
[21:50] <balloons> iBelieve, no rush, as I'm working on the clock app now and probably won't be back to file manager until tomorrow
[21:51] <balloons> I just wanted to make you aware and see if you knew anything about it. Sounds like you do which is good :-)
[21:53] <iBelieve> balloons, I was already working on fixing the action selection popovers among other things, so thanks for noticing the copying problem. I uploaded the branch if you wanted to take a look at it, but it still isn't working for me.
[22:08] <iBelieve> balloons, I fixed the copying/cutting of files in the UI, but now those tests and others are broken, so I need to fix those.
[22:11] <balloons> iBelieve, heh, always something eh? Good though, I'm glad to hear
[22:11] <balloons> thoughts on fixing the open_file test to not depend on processmanager?
[22:11] <balloons> iBelieve, ^^
[22:13] <iBelieve> balloons, I haven't seen the new tests yet, I'll take a look though
[22:14] <iBelieve> balloons, that's cool how that test works. Is there a reason why it should not depend on ProcessManager?
[22:15] <balloons> iBelieve, https://bugs.launchpad.net/autopilot-qt/+bug/1209004
[22:15] <ubot2`> Ubuntu bug 1209004 in Autopilot Qt Support "Process Manager tries to call Xlib on phablet devices" [Undecided,New]
[22:15] <balloons> it blows up on the device, but it's not your fault.. however, I think it can be done without processmanager..
[22:17] <iBelieve> balloons, ah, that was the other bug you mentioned before. I wasn't the one who wrote that test, elopio did, so I'm not familiar with how it works, but I'll try to think of some way to do it.
[22:18] <iBelieve> balloons, I've got a question on how I should write the autopilot tests for my new changes, if you have time.
[22:19] <balloons> sure, go for it.. and yea, I know you didn't write it. I would leave it for now till we get feedback on whether or not we should be using processmanager for it I'd suspect
[22:22] <iBelieve> balloons, I've added a sidebar (like in Nautilus) that is visible when the app is wide enough (here is the screenshot: http://i.imgur.com/GZOVaLf.jpg). This basically replaces the Places menu in the toolbar. I've also changed the default size to 100 gu, so it looks good on the desktop, assuming the phone will correctly size it to 50 gu.
[22:22]  * balloons wonders what it will look like on my tablet
[22:23] <iBelieve> balloons, now my question is, how should I write the tests for the new layout? There needs to be tests for both the tablet/desktop mode and phone mode. Should these be in one test, or in separate tests?
[22:24] <iBelieve> balloons, and is it possible to change QML properties from autopilot so I can put the app into phone mode to test it?
[22:24] <balloons> iBelieve, ahh yes.. Well you could put it into the same test and detect the proper size then act accordinly
[22:24] <balloons> and yea, forcing a particular size is interesting too
[22:25] <iBelieve> balloons, so should only do one test depending on what device it is running on, or should I force both sizes to test?
[22:25] <balloons> I'm concerned with how a device will respond if you force the size. On the desktop, sure should be fine. On the phone, well it can't fit a tablet size :-)
[22:26] <iBelieve> balloons, good point, I hadn't thought about that. So I guess I'll just write the tests to test for the particular configuration the app is run in?
[22:27] <balloons> yes, I would do that. As to wanting to hack on the different size and test them, I suppose the desktop test could run both..
[22:29] <iBelieve> balloons, for now, I'll just run the tests based on the initial size. Thanks for the help!
[23:04] <iBelieve> balloons, ping
[23:05] <balloons> iBelieve, pong
[23:07] <iBelieve> balloons, so one of the reasons the copy autopilot test fails is that there is no wait for the destiniation directory to be opened. I'd like to be able to incorporate that into the FolderListDelegate emulator, but it seems that assertThat isn't available outside of the test case. Any suggestions?
[23:08] <iBelieve> balloons, here is a snippet of what I'm trying to do: http://paste.ubuntu.com/5956870/. First I tried calling assertthat on self, then on AutopilotTestCase, but AutopilotTestCase requires an instance.
[23:32] <iBelieve> balloons, I need to go, I'll try and see if I can find some way to do it, otherwise I'll ask again later.
[23:33] <balloons> iBelieve, yes, in short, don't use asserts outside of testcases. That said, I'm not sure I get the hangup here
[23:33] <iBelieve> balloons, what do you mean "I'm not sure I get the hangup here"
[23:38] <balloons> I mean I'm knee deep in ubuntu clock, and losing my mind as it's getting late here :-)
[23:38] <balloons> in other words, I can't be of much more help atm ;-p