[09:05] <danialbehzadi> Hi. When I click on the "Run" button in Qt creator, it just says "No executable specified.", But I can run the qml file with "$ qmlscene Main.qml" in terminal. What's the problem?
[09:15] <greyback> danialbehzadi: you need to specify what gets run - go to the Project pane in QtC and explore the "Run" tab
[09:17] <danialbehzadi> greyback: It may sound stupid, but where is this QtC located?
[09:17] <greyback> danialbehzadi: QtC = QtCreator
[09:17] <greyback> sorry, was lazy in typing
[09:19] <danialbehzadi> greyback: In tools > Options?
[09:20] <greyback> danialbehzadi: no. Have you a project open?
[09:20] <danialbehzadi> greyback: yes
[09:21] <greyback> danialbehzadi: then look at the pane on the left of the QtC window - there should be a Projects button there
[09:21] <danialbehzadi> greyback: Yeah. I found it
[12:42] <chesedo> on the js scope api's page it says that the `get` method of `results` returns a string, number or object. Is an object also returned when the attribute is an array?
[14:14] <peter-bittner> oSoMoN: jdstrand mentioned you may be able to help me with issues related web apps and camera permissions. I've got a web app which refuses to allow access to the camera. The trust-store dialog doesn't pop up even though policy_groups are in the .apparmour file and the service works in a plain oxide browser. I've explained it in detail on the mailing list. https://lists.launchpad.net/ubuntu-phone/msg18658.html
[14:16] <peter-bittner> This is the first critical problem. As soon as this is fixed I need to be able to tell the web view which camera to use. By default the rear camera is used, but this is impractical with the app which does video conferencing. The user won't be able to use the browsers Settings screen because I hide the address bar.
[14:30] <oSoMoN> peter-bittner, yes, I’ve seen both e-mails on the mailing list, will answer today, sorry for the delay
[16:05] <chesedo> davidcalle: maybe you can help me with the above ^^ about the api
[16:41] <vvein> hi
[16:41] <vvein> can someone help me with recompiling firefox?
[16:41] <vvein> I can't figure it out, how to add some flags to CFLAGS and CXXFLAGS
[16:42] <vvein> I tried APPEND in /etc/dpk/buildflags.conf; export CFLAGS in bash; settings DEB_CFLAGS_MAINT_APPEND in debian/rules
[16:43] <vvein> still can't see anything during compilation
[16:43] <vvein> anything = any of my additional flags
[17:35] <popey> renatu: / bfiller want me to upload latest calendar including renatu's branch to the store, or should I wait for further fixes?
[17:36] <bfiller> popey: we need to wait
[17:36] <popey> ok
[17:36] <bfiller> popey: QA needs to test still and it requires some backend changes in silo 22
[17:36] <popey> ok
[17:36] <bfiller> popey: shooting for inclusion in ota10
[17:36] <bfiller> in the image
[17:36] <popey> awesome.
[17:36] <popey> including UI updates?
[17:37] <bfiller> popey: you mean the stuff nik90 working on?
[17:37] <popey> yes
[17:37] <bfiller> popey: if there is time, but don't think we'll block on that
[17:37] <popey> okay. thanks. that's what I expected
[17:48] <nik90> renatu, Hey, I just noticed that I cannot open "Repeats" or "Reminder" page from within the "NewEvent" page. I get the error that file:///opt/click.ubuntu.com/com.ubuntu.calendar/0.4.latest/NewEvent.qml:720: TypeError: Cannot call method 'push' of null
[17:49] <nik90> renatu, I see that defined as pageStack.push(Qt.resolvedUrl("EventRepetition.qml"),{"eventRoot": root,"isEdit":isEdit}); ... not sure why it cannot find pageStack
[17:49] <nik90> any thoughts?
[17:55] <renatu> nik90, fix on the way
[17:55] <nik90> renatu, thnx
[18:00] <renatu> nik90, could you review it? https://code.launchpad.net/~renatofilho/ubuntu-calendar-app/fix-event-creation/+merge/288326
[18:04] <nik90> renatu, on it
[18:12] <nik90> renatu, What's the need for this stack variable? I tried just using bottomEdgePageStack and it works when I open the NewEvent Page using the bottom edge, long-pressing on the week view to create an event etc.
[18:12] <nik90> renatu, http://paste.ubuntu.com/15322416/
[18:12] <nik90> or in other words, I cannot find any scenario, where using just bottomEdgePageStack wouldn't work
[18:13] <renatu> nik90, editing a event does not set bottomEdgePageStack
[18:14] <renatu> nik90, editing a event uses the default pagestack variable
[18:15] <nik90> ah yes, you're right
[18:17] <nik90> renatu, top-approved.
[18:18] <nik90> renatu, btw in the new design spec, we still use Tabs. I also want to migrate to the new PageHeader as well. I talked to tim about bug 1539759 for another app and his suggestion was to define a tabs list of actions and then use that in leadingActionbar
[18:18] <nik90> with numberofactions set to 0. This will ensure that the hamburger (tabs) icon is always shown. The user will not notice any visual change
[18:19] <nik90> s/tim/t1mp
[18:20] <suebt> Hey, got one question about Oxide: Can you explain to me why one *has* to create a new WebView for a new view request directly in the onNewViewRequested handler? Or is there another way to handle this? If not, will this change in the future?
[18:20] <renatu> nik90, yes I am already doing that
[18:21] <nik90> ah ok
[18:21] <ahayzen> nik90, i talked to you about how we are setting the leadingActionBar.actions for the tabbar right?
[18:22] <ahayzen> think that was the same conversation with Tim :-)
[18:23] <nik90> ahayzen, I think so
[18:24] <nik90> ahayzen, although I remember t1mp distinctly saying that the leadingactionbar icon defaults to the hamburger icon
[18:24] <ahayzen> it does, if you provide it more than 1  ? IIRC
[18:24] <nik90> yup
[19:49] <ahayzen> t1mp, o/ Have you ever heard any issues about the PageHeader disappearing when changing head sections and the flickable property changing at the same time ? Also is there a way to do the old header.show() in the new header ?
[20:26] <peter-bittner> oSoMoN: I've added bug 1554202 for the webapp-container issue, https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1554202
[23:10] <t1mp> renatu: right, for the 'tabs' navigation, use the leadingActionBar. I replied on https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1539759