[09:44] <nik90> timp, How do I show the tab navigation drawer action in the leadingActionBar?
[09:45] <nik90> I couldn't find that in the UITK Gallery example
[10:16] <timp> nik90: if you have more actions than numberOfSlots, you automatically get an overflow
[10:16] <timp> nik90: so in case of the leadingActionBar, you get an overflow when you have more than 1 action in it
[10:19] <chesedo> hello, i have a question about js scopes...
[10:19] <davidcalle> chesedo: sure :)
[10:19] <chesedo> is it possible to declare an object in a seperate file and then to import it?
[10:20] <chesedo> the object might be quite long as it will be used to handle data easier
[10:20] <chesedo> ... so do not want it in the main file
[10:24] <davidcalle> chesedo: sure, it's possible, you need to put your extra file in src/node_modules and do it this way: http://stackoverflow.com/questions/3922994/share-variables-between-files-in-node-js
[10:24] <davidcalle> chesedo: well, you don't "need" to, but it's cleanrer this way, all js imports are in the same place :)
[10:24] <davidcalle> cleaner*
[10:25] <chesedo> ok, let me try
[10:31] <chesedo> great that worked. ty davidcalle
[10:31] <davidcalle> chesedo: cool, yw
[11:03] <nik90> timp, in Podbird we have 4 tabs which we can access using the tab switcher button (3 lines). When I switch over to PageHeader, I didnt declare any leadingActions thereby hiding that tab switcher which is essentially for us.
[11:04] <nik90> timp, I tried leadingActionBar: navigationActions but that didnt work either
[11:04] <nik90> How do I show the tab switcher?
[11:07] <timp> nik90: oh, right, you don't get a list from the Tabs automatically any more. We don't have designs (yet?) for tabs working with convergence
[11:08] <timp> the basic idea was for apps to use the AdaptivePageLayout, so they can support convergence
[11:09] <nik90> timp, while we can use AdaptivePageLayout, on the phone it shouldn't matter much..tabs should be tabs on phones, while on desktops we can show additional columns
[11:09] <timp> that means, to get a list like the old tab overflow panel, you'd have to add actions to leadingActionBar like [ Action { onTriggered: apl.addPageToNextColumn(myTab } ]
[11:09] <nik90> so we do something like Dekko and create a custom sliding menu from where we can launch other pages?
[11:10] <timp> better support for a custom sliding menu like that should be added to the toolkit eventually, but we didn't start to work on that yet, and we don't have the requirements yet
[11:11] <timp> nik90: but yes, a sliding menu like that is an option. Adding a list of actions to the leadingActionBar would be less work though, I imagine
[11:12] <nik90> timp, I suppose adding a list of actions would be less work, but then it would show the overflow button (3 vertical dots) which might look out of place :/
[11:19] <timp> nik90: the leading action bar has this by default:
[11:19] <timp>         StyleHints {
[11:19] <timp>             overflowIconName: "navigation-menu"
[11:19] <timp>         }
[11:19] <timp> so it shows the "tabs" button
[11:20] <timp> if it doesn't, let me know because that is a bug
[11:20] <nik90> oh nice, will try it out.
[11:21] <timp> nik90: if there are any more questions, don't hesitate to ask :) I'll work on a blog post about the new header stuff and it is good to know which things are not obvious :)
[11:21] <nik90> timp, will do
[12:48] <nik90> timp, anyway of making a generic list of actions and using that in different pages to avoid code duplication? I tried creating a ActionList with common actions, and then settings that to the leadingActionBar.actions but didnt work.
[12:55] <ahayzen> nik90, can you not just have a property list<Action> myActions ? and set the myActions to .actions ? or are you wanting it as a component ?
[12:56] <nik90> ahayzen, I want to implement it as a component and push it into own file and use it in several places
[12:57] <ahayzen> hmm, i think we have been using states for that
[12:58] <ahayzen> nik90, something like this? http://bazaar.launchpad.net/~ahayzen/music-app/convergence-tabs-with-sidebar-01/view/head:/app/components/HeadState/PlaylistsHeadState.qml
[12:58] <nik90> ahayzen, ah ... but I am transitioning from PageHeadState to PageHeader :)
[12:59] <ahayzen> same :-)
[12:59] <nik90> ahayzen, turns out that the new PageHeader doesn't display the list of tabs anymore automatically
[12:59] <ahayzen> nik90, note at the bottom of that the PropertyChanges
[12:59] <ahayzen> oh i had that as well
[12:59] <ahayzen> let me find what i did...
[13:00] <ahayzen> nik90, http://bazaar.launchpad.net/~ahayzen/music-app/convergence-tabs-with-sidebar-01/view/head:/app/components/MusicPage.qml#L46
[13:00] <ahayzen> nik90, set the leadingActionBar.actions to a list of the tab actions
[13:01] <ahayzen> currently that is a fixed list, but hopefully gonna improve that a bit
[13:01] <nik90> ahayzen, yup that's what I am trying to do, however I want to turn that list of tab actions into a component so that I can use it in other tab pages.
[13:01] <nik90> I could try instead creating a generic page component instead
[13:02] <ahayzen> i just put it in the main under the Tabs {}
[13:02] <ahayzen> then i could access pretty much anywhere with tabs.tabActions
[13:02] <nik90> ah...think I will do that as well
[13:02] <ahayzen> http://bazaar.launchpad.net/~ahayzen/music-app/convergence-tabs-with-sidebar-01/view/head:/app/music-app.qml#L640
[13:02] <ahayzen> nik90, ^^ like that
[13:03] <nik90> ahayzen, yup that's it..perfect! thnx
[13:03] <ahayzen> \o/ no problem
[13:03] <ahayzen> i want to move all of the tabs and actions to be generated from a repeater eventually :-)
[13:04] <nik90> I/SDK Team don't know what will become of tabs in the convergent future...they don't have a design for it.
[13:04] <nik90> which is a tiny bit worrying considering there are so many apps out there using tabs
[13:05] <ahayzen> yeah, i had fun getting the tabs to work in our 'converged' scenario
[13:05] <nik90> ;)
[13:05] <nik90> ahayzen, so does switching tabs does the same thing in desktop mode in the music app with the only difference being the sidebar showing the now playing song and playlist?
[13:06] <nik90> s/does/do
[13:06] <ahayzen> yup
[13:06] <ahayzen> and it displays on a 10" tablet
[13:06] <ahayzen> in landscape
[13:06] <nik90> ah ok...we were exploring this for podbird as well. but we have other work to get done before we can think of convergence
[13:07] <ahayzen> :-) if you look below the Tabs you can see how we've done the sidebar http://bazaar.launchpad.net/~ahayzen/music-app/convergence-tabs-with-sidebar-01/view/head:/app/music-app.qml#L891
[13:07] <ahayzen> note this hasn't been reviewed yet, it was just created for demoing at MWC
[13:08] <nik90> ok..
[13:08] <ahayzen> but it is looking much closer than previous attempts :-)
[13:08] <ahayzen> only 1 or 2 issues left IIRC
[13:08] <nik90> looking forward to see MWC demoes of the music app :)
[13:09] <ahayzen> hah :-) or just push lp:~ahayzen/music-app/convergence-tabs-with-sidebar-01 to a tablet :-)
[13:09] <ahayzen> or tweak the wideAspect value so you can play with it on a mako like i do :')
[13:09] <nik90> I think music app and Dekko are the best forerunners of showing convergence of real-world desktop apps
[13:09] <nik90> well I don't own a tablet nor a desktop with 16.04 to try it out :P
[13:10] <nik90> this is why I need the god-sent desktop-kit to work ;)
[13:10] <ahayzen> yeah, same hence me having to develop on a mako :-)
[13:10] <ahayzen> but i have a slimport adaptor so can play on a 'big screen' :-)
[13:10] <timp> nik90: hmm, why that doesn't work?
[13:10] <nik90> hmm I should get that too since I have a mako
[13:11] <timp> nik90: you can define the actions like Action { id: action1 }; Action { id: action2 }; and then define leadingActionBar.actions: [action1, action2]
[13:11] <nik90> timp, I want to have that Action { id: action1} and Action { id: action2} together in a separate file.
[13:11] <nik90> I tried it with http://paste.ubuntu.com/15179770/
[13:12] <nik90> on referencing TabsList{} or an instance of it, I got error that an object cannot be used in place of a list.
[13:13] <ahayzen> could you not do ... QtObject { property list<Action> actions: [ ... ] } ... MyObject { id: myObject } ... leadingActionBar.actions = myObject.actions ? or is that super hacky ;-)
[13:13] <timp> nik90: leadingActionBar.actions: TabsList.actions ?
[13:13] <ahayzen> or that :-)
[13:14]  * nik90 tries
[13:14] <timp> in TabsList.qml you could even put the Actions as children of the ActionsList. It has:     default property alias children: list.actions
[13:14] <nik90> ok
[13:15] <nik90> yup that works
[13:16] <nik90> thnx
[13:16] <timp> maybe you want to add property int currentTab to the TabsList, and something like Action { id: add; visible: tabsList.currentTab != 2 }
[13:17] <timp> so you can hide the current tab from the tab list
[13:24] <nik90> yes :)
[16:04] <karni> zsombi: hiya, question :) is it possible apl.removePages(apl.primaryPage) is async? if so, do I have quarantee pages will be removed, but not the one I push to the stack in the next line?
[16:04] <karni> zsombi: I either have a bug in QML (highly probable in this case), or a page that is added *after* that call, is also being removed
[17:13] <dpm> balloons, on your coreapps tests document, what does "Templates in place for all tests" refer to?
[17:13] <balloons> dpm, I should move that over or remove it. I was originally tracking how the tests were laid out within the projects
[17:14] <balloons> but it's more or less an answered question -- if there's qml and autopilot and manual tests, then it has everything we want
[17:15] <dpm> balloons, ok, gotcha. I think one thing to address will be also the fact that unit tests are not run on build by default from what I see on column F
[17:15] <balloons> yes, I was just noticing it no longer seems to be the case for anything. Not sure what changed, but I'm thinking of just forcing it on the jenkins side instead of relying on the cmake build
[17:16] <balloons> so that way it can't be shut off as easily :-)
[17:20] <dpm> balloons, ok. Also I'm surprised to see that only 3 apps have manual tests. I thought we had gone through most of the core apps and wrote tests when we were prepping things up for Pilot
[17:20] <balloons> we have them, they just aren't in the source tree
[17:20] <balloons> we wrote and used 4 fully vetted testsuites in checkbox format
[17:21] <balloons> I'm not sure what happened to the 4th one -- those are what is in the source tree. I'd like the other suites to get added in the same way I think
[17:22] <dpm> oh, if they're not in the source tree, where are they currently?
[17:24] <balloons> popey would know more, and could answer better than I. However, they are in pads / wikis from what I remember in creating the original 4
[17:25] <balloons> very similar to the other system apps. There manual tests are strewn about
[17:25] <balloons> so it seems to me at least
[17:29] <chesedo> for a js scope, where should images (emblems) be stored and how will their uri be?
[17:42] <MBach> hello
[17:44] <MBach> I'm have trouble to build my software because I rely on an "external" ppa
[17:44] <MBach> when I submit my package to launchpad
[17:46] <MBach> what should I do to have my build successful?
[18:47] <branau> Hello everyone!
[18:49] <branau> I'd like to take up the task of creating a WhatsApp client for Ubuntu Touch, but I just wanted to check to see if there was a reason no one has done this already?
[19:00] <branau> I posted about it on the forums as well, because a team of people got it running for FirefoxOS: http://ubuntuforums.org/showthread.php?t=2314659
[19:36] <dobey> branau: main reason is that WhatsApp actively break third party clients, and ban users they catch using them
[19:37] <dobey> also, without support from the whatsapp server side, it will have pretty limited functionality on ubuntu phones
[19:48] <faenil> not sure about the lack of functionality, but the terms of service are definitely an issue
[19:59] <branau> dobey, that makes sense, thanks
[19:59] <branau> Might be time to start boycotting whatsapp
[23:18] <ahoneybun> ahayzen, ever get the error: unable to assign AppHeader_QMLTYPE_28_QML_34 to AppHeader_QMLTYPE_84
[23:18] <ahayzen> ahoneybun, don't think so, what you trying todo?
[23:19] <ahoneybun> seems to be related to a move from 1.2 to 1.3 components
[23:19] <ahoneybun> with PageStacks
[23:20] <ahayzen> are all the imports updated to 1.3?
[23:20] <ahoneybun> nope, that worked
[23:21] <ahoneybun> looks so much better with 1.3 over 1.2
[23:21] <ahoneybun> with the header alone
[23:22] <ahoneybun> well then
[23:22] <ahayzen> ahoneybun, does it tell you a line number and file where the issue was?
[23:22] <ahoneybun> ahayzen, I fixed it after I checked all the version numbers
[23:22] <ahayzen> ah :-)
[23:22] <ahayzen> \o/
[23:23] <ahoneybun> now to look at mhall119's code how he uses pages in pages with PageStack
[23:23] <ahayzen> ...pages in pages... ?
[23:23] <ahoneybun> under the Contribute page I want to have subpages of the different flavor
[23:23] <ahoneybun> *s
[23:23] <ahoneybun> if possible
[23:23] <ahayzen> like sections ?
[23:23] <ahoneybun> that might work better
[23:23] <ahoneybun> make it flickable
[23:24] <ahayzen> like what Contacts has "All" | "Favourites"
[23:24] <ahoneybun> on thouse
[23:24] <ahoneybun> I could never get those to work or figure them out
[23:24] <ahoneybun> or both
[23:24] <ahoneybun> XD
[23:24] <ahayzen> let me find the docs
[23:24] <ahayzen> they are super simple
[23:24] <ahoneybun> I saw them
[23:25] <ahoneybun> or from the reddit app
[23:25] <ahayzen> ...once you know how :-)
[23:25] <ahoneybun> well that appiles to a lot
[23:25] <ahoneybun> *applies
[23:25] <ahoneybun> like spelling
[23:25] <ahoneybun> I just got head.actions to work lol
[23:25] <ahayzen> ahoneybun, look at the example here https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.PageHeadSections/#model-prop
[23:26] <ahayzen> ahoneybun, then all you do is visible: page.head.sections.selectedIndex [23:26] <ahoneybun> visible?
[23:27] <ahayzen> yeah so if you have MyFirstItem { visible: page.head.sections.selectedIndex [23:27] <ahayzen> etc
[23:28] <ahayzen> will make MyFirstItem be shown when the first section is selected and the MySecondItem on the second
[23:28] <ahoneybun> you said sections so I went here: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.Sections/
[23:28] <ahayzen> yeah that as well :-)
[23:29] <ahoneybun> how different are thouse?
[23:29] <ahoneybun> those?
[23:29] <ahayzen> they are the same thing
[23:29] <ahayzen> just the page.head.sections is already in the Page for you
[23:31] <ahoneybun> now how do I add things to each?
[23:34] <ahoneybun> there are move then 2-3 flavors though...
[23:34] <ahoneybun> the docs recommend not using more then that