[13:57] <mhall119> fishbowl link: https://plus.google.com/hangouts/_/1e6bd7ba84c1db299f1c272888a0b862b08cec8f?authuser=1&hl=en
[13:58] <mhall119> popey: dpm: ^^
[13:58] <popey> thanks
[13:58] <popey> be there in a mo
[13:59] <dpm> yep, coming!
[14:03] <rickspencer3> I can hear you guys :)
[14:03] <wellsb> It's playing
[14:04] <timp> mhall119: video is playing for me
[14:04] <timp> hello zoltan
[14:05] <rickspencer3> I was enjoying the banter!
[14:05] <popey> ☻
[14:05] <popey> I am being watched by my mother in law's owls
[14:06] <timp> popey: real owls like this http://img.thesun.co.uk/aidemitlum/archive/01495/Owl-ucinating_532_1495434a.jpg or does "owls" mean something else?
[14:07] <popey> timp: no, lots of pictures and models of owls
[14:07] <popey> like _loads_ of them
[14:08] <popey> Any questions at all?
[14:08] <popey> Anything we need to discuss?
[14:09] <alex-abreu> mhall119, bzoltan arg!
[14:10] <mhall119> alex-abreu: is that a yes arg or a no arg?
[14:11] <mhall119> balloons: ping
[14:11] <alex-abreu> mhall119, if it is convenient for you then go for it, ... :)
[14:14] <kunal_> dpm: here is screen shot http://design.canonical.com/wp-content/uploads/02_month2-copy.jpg
[14:14] <dpm> thanks kunal_!
[14:14] <dpm> bzoltan, http://design.canonical.com/wp-content/uploads/02_month2-copy.jpg
[14:16] <timp> I wonder whether the BubbleShape component in the Ambience theme could be useful for that.
[14:16] <timp> it is meant to be used by the Popover
[14:17] <timp> for a custom "hack" in the calendar app, the calendar developers can have a look at BubbleShape.qml
[14:17] <mhall119> kunal_: ^^
[14:18] <popey> https://bugs.launchpad.net/ubuntu-ux/+bugs?orderby=status&start=0
[14:18] <kunal_> any link for BubbleShape.qml ?
[14:18] <dpm> timp, ^
[14:20] <mhall119> alex-abreu: ok, we're moving the HTML5 session then, sorry about that
[14:20] <alex-abreu> mhall119, next hour?
[14:20] <mhall119> yes
[14:21] <timp> kunal_: here you can see how it is used: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/Themes/Ambiance/PopoverForegroundStyle.qml
[14:21] <timp> kunal_: and here is the source http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/Themes/Ambiance/BubbleShape.qml
[14:21] <kunal_> timp, thanks
[14:21] <timp> kunal_: it was meant for Popover, and has some stuff (like the arrow/pointer) that you don't need. But maybe there's some useful code in there
[14:22] <timp> kunal_: bubbleshape is "only" part of the theme, and not part of the UITK public API, so don't rely on it being always there
[14:23] <bzoltan> I have read this : http://pad.ubuntu.com/uds-1308-appdev-1308-app-developer-mode
[14:23] <bzoltan> mhall119 ^
[14:23] <kunal_> ok, will check out the code, how i can use it
[14:26] <timp> QUESTION: do you think that everything (all packages) needed to build your software (including cpp) on the device in the default images? It is a developer preview after all
[14:26] <timp> now I have to install all the packages after an upgrade
[14:27] <timp> ^+"should be included" (in the the default images)
[14:28] <popey> https://bugreports.qt-project.org/browse/QTBUG-32225
[14:28] <popey> dpm: ^
[14:28] <dpm> thanks popey ;)
[14:30] <timp> mhall119: ok, thanks
[14:31] <popey> np
[14:31] <CheeseBurg> Has there been a discussion on desktop app development with the SDK? Same the desktop app design guides?
[14:31] <timp> bzoltan: compiling on the device is not too bad for me. Devices are fast nowadays :)
[14:32] <bzoltan> timp: the issue is not the performance. The showstopper is the RO image what does not like apt-get installing the build deps
[14:33] <aquarius> QUESTION which I think has likely been asked already, but I'm not sure. If I write an app for the App Showdown, should I look at distributing it *as* a click package? This question has two components: will the click package stuff be available in time, and can people on a desktop install a click package?
[14:34] <cjwatson> I don't expect converged click packages to be working by 13.10
[14:34] <timp> CheeseBurg: it is possible already to develop desktop apps with the SDK, although the user interface components are more optimized for touch
[14:34] <aquarius> cjwatson, that's what I thought...
[14:34] <cjwatson> You can do it but it requires some hacking
[14:34] <aquarius> which leads to another QUESTION, which is: how should App Showdown apps *be* given to people? debs? bzr branches? :)
[14:35] <CheeseBurg> timp: I know but I was wondering more about the desktop specific focus. I just wanted a timeline.
[14:35] <cjwatson> (to clarify: there aren't *that* many blockers, but there's only one of me ...)
[14:35] <popey> aquarius: deb for desktop, click for touch?
[14:35] <popey> (qtcreator can create both)
[14:35] <aquarius> popey, I am worried about making a click package when I don't *have* a Touch implementation to test it on, you see
[14:35] <popey> aquarius: i hereby volunteer to test your app
[14:36] <popey> or come to my house and test it here
[14:36] <popey> you pay mileage
[14:36] <aquarius> well, once I win the competition I'll have a nexus 4, of course. ;-)
[14:36] <popey> get you
[14:36] <aquarius> (not all that likely tbh :))
[14:36] <popey> of course not, I'm going to win with my as-yet unwritten app
[14:37] <aquarius> mhall119, my app's pure QML. No C++ for me. Ever. :)
[14:37] <bzoltan>  aquarius:  that is the way to go
[14:37] <wellsb> At what point should we ask for this extra help developing click packages for compiled packages?
[14:38] <aquarius> ooh, mhall119 says that the command line click tools will work on the desktop. cjwatson, if that's not the case you might wanna mention it ;)
[14:38] <cjwatson> wellsb: the next two sessions will be relevant
[14:38] <cjwatson> aquarius: that is correct
[14:38] <aquarius> cjwatson, oh! cool. So I can just distribute as a click package and say "to install on desktop Ubuntu, do: apt-get install clickthings; click install app.click"?
[14:39] <wellsb> Excellent
[14:39] <popey> aquarius: send me a usb stick wrapped in a £50 note and I'll test the app for you
[14:39] <cjwatson> aquarius: Well, no.  "click build" is fine; but blockers for installing include (a) living in a different packagekit vs. aptdaemon world (b) the application lifecycle stuff almost certainly isn't in place to start the app properly
[14:40] <cjwatson> aquarius: You can certainly hack things up to install it, but I suspect it will not quite run properly
[14:40] <cjwatson> aquarius: It'll be *nearly* there, and it's worth somebody having a go, sure
[14:40] <dpm> wellsb, you can find us on #ubuntu-app-devel and ask there once you're app is ready to be packaged
[14:41] <aquarius> that sounds rather like if I want to enter a showdown app I need to distribute it twice? Once as click for phones, and once some other way so desktop people can use it? (I'm fine with this being the case, I just want to know if it's the case :))
[14:41] <cjwatson> wellsb: (by which I mean http://summit.ubuntu.com/uds-1308/meeting/21954/community-1308-qml-extensions/ and http://summit.ubuntu.com/uds-1308/meeting/21908/foundations-1308-arch-specific-click-pkgs/)
[14:41] <aquarius> I am trying to avoid debs because I don't properly understand them :)
[14:41] <cjwatson> I think for 13.10 you should assume that that is the case; if we can do better, bonus
[14:41] <cjwatson> But I suspect convergence will not be quite there enough to do much better for 13.10
[14:42] <aquarius> ok, cool. dpm, mhall119, it might be a good idea to write a blog post or something about how to distribute your app showdown app so that desktop people can play it?
[14:42] <CheeseBurg> Will there be an app showdown in the future (far or near) where developers can submit closed source stuff for a price. I know this showdown is for testing new app uploading features but what about future ones.
[14:42] <aquarius> (as well as "submit a click package to the app store", of course.)
[14:44] <aquarius> click packages should support you bundling a binary, surely? (It's just the same as bundling a library.)
[14:44] <justforkicks> David the next time you get a good idea can you get a person to turn on that light above your head j/k ?  it would be funny
[14:45] <cjwatson> aquarius: Yes, modulo layout of fat packages
[14:45] <cjwatson> aquarius: But worst case a script at the top level that detects architecture and dispatches to the right one
[14:45] <aquarius> cjwatson, yeah, I'm handwaving architecture stuff, but yeah
[14:45] <dpm> justforkicks, lol, absolutely! :)
[14:46] <CheeseBurg> Will the minimum price for apps be decreased in the store, just curious? Also there should be session at the next UDS for app store stuff specifically.
[14:46] <aquarius> potential apparmor problem: apparmor is working on the name of the executable, right? So if my apparmor profile is for "qmlscene /opt/click/mypkg/whatever.qml" and that QML file execs /opt/click/mypkg/somebinary, will somebinary be restricted by apparmor?
[14:47] <jdstrand> aquarius: apparmor can work in that manner, but that is not how we are performing attachment
[14:47] <aquarius> also I am not sure how the whole "suspend this app" stuff works if you exec another binary.
[14:47] <aquarius> jdstrand, oh, cool, I didn't realise you were here ;) Clearly you already understand this stuff :)
[14:47] <jdstrand> aquarius: we are creating a named profile, and then changing profile using either upstart apparmor integratin or aa-exec
[14:48] <jdstrand> aquarius: it is a technique similar to what we've don't with libvirt and qemu for years
[14:48] <jdstrand> aquarius: fork, change profile, exec (essentially)
[14:48] <jdstrand> aquarius: I am ubiquitous :)
[14:48] <aquarius> jdstrand, so if an apparmored executable execs another binary, that other binary is still confined by the same profile? (i.e., it is confined, and it has the same allowances as the parent rather than having no profile and thus being completely confined with no permissions)?
[14:49] <CheeseBurg> What about subscription purchases?
[14:49] <CheeseBurg> Like magazines on Android
[14:50] <jdstrand> aquarius: apps are generally not allowed to execute other applications. they are allowed to exec code in there install directory and XDG_DATA_HOME/<app dir>. we use 'ix' permissions in apparmor which means the child will inherit th epermissions set of the parent
[14:50] <jdstrand> s/in there/in their/
[14:51] <aquarius> jdstrand, ah, that's cool. This question is in the context of a click package shipping a QML app which execs another binary that's shipped inside the click pacakge, not about a package execing something random from elsewhere, so what you're describing is perfect.
[14:51] <jdstrand> eg, so an app can ship a helper and execute it with the same permissions as the parent
[14:51] <aquarius> perfect, that's precisely what popey was asking about :)
[14:51] <jdstrand> right, yes, that is allowed
[14:51] <jdstrand> hey, I thought popey asked me that the other day and I answered :P
[14:51] <popey> ☻
[14:52] <popey> so my qml app can call my c++ wrapper to call cowsay?
[14:52] <aquarius> I'd still like to hear what happens in the app suspender for chlid processes; does it suspend a whole process group?
[14:52] <jdstrand> popey: your question was certainly for the benefit of the group :)
[14:52] <CheeseBurg> You guys need App Store discussions badly lol.
[14:52] <popey> and I ship 3 binary versions of cowsay for x86, x86_64 and armhf
[14:52] <popey> ?
[14:52] <jdstrand> aquarius: that is a good question that I brought up on a mailing list recent (ubuntu-phone?)
[14:52] <aquarius> popey, I suspect that instead of a C++ wrapper, you'd write a C++ QML plugin which just execs any named binary -- that way, it can be reused by everyone.
[14:52] <wellsb> Is pure qml somehow preferred over c++/qt/qml?  Performance-wise or otherwise.  My app has just one small component that is c++, but I could probably work around to get that in pure qml.  I just wanted to have the c++ backend to potentially extend functionality in the future.
[14:53] <aquarius> popey, actually, that sounds like the sort of thing that bzoltan could usefully add to the SDK -- a simple QML plugin that shells out.
[14:53] <popey> I agree
[14:53] <popey> I want to make a gui frontend to a cli app
[14:53] <aquarius> bzoltan, suggestion for you ^^ ;-)
[14:53] <bzoltan>  aquarius:  +1
[14:53] <popey> and it seems needlessly complex
[14:54] <dpm> any more questions on IRC?
[14:54] <aquarius> dpm, wellsb had a question about using pure QML apps and whether it's the best idea (which it is :))
[14:55] <wellsb> mhall119: see above
[14:55] <popey> thanks mhall119 dpm bzoltan
[14:55] <dpm> \o/
[14:55] <bzoltan> thanks guys
[14:55] <dpm> thanks popey
[14:55] <dpm> and everyone on IRC
[14:55] <bzoltan> we miss you aquarius
[14:56] <aquarius> thank you, chaps
[14:56] <aquarius> bzoltan, I'm still sort of around :)
[14:56] <bzoltan> aquarius: as we see :)
[14:56] <aquarius> bzoltan, hey, I'm community now, I'm allowed to ask challenging questions ;)
[14:56] <CheeseBurg> later
[14:56] <bzoltan> aquarius: not as if you were afraid before :D
[14:56] <aquarius> CheeseBurg, interesting set of questions about the app store
[14:57] <wellsb> So there's no appreciable performance or resource hit by using c++?  It's just easier to package qml?  I just think having the c++ backend opens doors for future development
[14:57] <aquarius> bzoltan, true enough :)
[14:58] <aquarius> wellsb, c++ will likely be faster than doing processing in pure QML, although QML is highly optimised for the stuff it's good at (moving stuff around on the screen, particle systems, being declarative). However, C++ stuff is quite a lot more annoying to package, compile, and distribute.
[14:58] <wellsb> Or is the recommendation to use pure qml if possible, and if extended functionality is needed, add the c++ backend and worry about multi-arch compilation at that point
[14:59] <aquarius> I would say that the recommendation is to use pure QML, and if you find something that either cannot be done from QML or you notice serious performance problems (which I never have), then look at writing a minimal QML plugin in C++ to do that bit of work in C++ and then expose it to QML.
[15:00] <aquarius> hey! isn't this meant to be HTML% stuff?
[15:00] <aquarius> html5
[15:00] <popey> yes
[15:01] <bzoltan> the udsbot was missing the reorg
[15:01] <popey> silly bot needs to press F5
[15:02] <alex-abreu> popey, must be lost in the backlog ... :)
[15:03] <karni> Will this be "HTML5 Developer Offering"? (possible channel topic mismatch)
[15:03] <karni> It looks to me like the HTML5 session has been moved to this slot.
[15:03] <alex-abreu> karni, yes
[15:04] <karni> alex-abreu: Hi! And thanks
[15:04] <alex-abreu> karni, and you are welcome to join :)
[15:04] <karni> alex-abreu: Thank you. I'll join once I have something interesting to say :)
[15:04] <alex-abreu> karni, you probably do from the user's perspective
[15:05] <karni> alex-abreu: I've mostly provided the feedback in written form. I'm also aware Qt has a number of fixes in place, but had little time verifying that. But I'm here, looking forward to the session :)
[15:06] <karni> (also, some bugs filed, as you may have seen)
[15:06] <alex-abreu> url for the hg https://plus.google.com/hangouts/_/26872982614b8314797a2178ae49b1f49232d30f?authuser=1&hl=en
[15:06] <karni> thank you
[15:09] <aquarius> cool, now the bot knows, clearly :0
[15:09] <karni> :)
[15:09] <aquarius> video not started yet?
[15:09] <karni> not here yet ("Starting soon")
[15:10] <aquarius> aha, video starts
[15:10] <karni> You're live
[15:10] <aquarius> ya, we can see you mhall119
[15:10] <karni> aquarius: That's the lag :)
[15:10] <karni> It's not Live® ;D
[15:11] <pmcgowan> yes
[15:11] <mhall119> daker is our awesome community dev :)
[15:11] <karni> Minor echo audible
[15:12] <karni> Sounds good now
[15:12] <daker> there is some seconds of lag
[15:17] <KeanuTheOne> The Grid Unit in Cordova Ubuntu is possible? Via new Cordova plugin?
[15:17] <karni> Re: tabs, you can flesh it out with a few lines of JS until it's fully implemented. Other components looked pretty good to me.
[15:18] <karni> (by flesh out I mean, you need to change active tab style and tab content manually)
[15:19] <karni> Non-Ubuntu specific cordova spec, for those interested http://cordova.apache.org/docs/en/2.8.0/index.html
[15:19] <karni> I mean API docs :)
[15:20] <aquarius> that's a really good question, KeanuTheOne -- alex-abreu, making window.Unity.units.gu() available would be nice. :) Better still would be being able to use units.gu in CSS, but vw/vh/vmin should cover that well enough, I think.
[15:21] <alex-abreu> aquarius, KeanuTheOne it will be discussed later
[15:21] <aquarius> my QUESTION: we not only need documentation of the Ubuntu-specific APIs, but also what the web engine supports. MDN shows how much documentation you need for a browser; I don't think the Ubuntu Browser (and the webapp container) is not documented like that at all, so we don't know which web things it supports. (Does it do vw/vh? WebGL? WebRT? CSS 3 transitions? 3d transitions? :))
[15:22] <aquarius> working with caniuse.com would be a brilliant way to do this
[15:22] <aquarius> it'd help expose the Ubuntu Touch browser to more people, and caniuse documents almost everything you might want to check, and fyrd who runs it is a good guy who would probably love to get a bit paid for helping :)
[15:26] <pmcgowan> qtwebkit capabilities should be documented at qt-project.org
[15:26] <pmcgowan> not that I can find them right now
[15:26] <aquarius> pmcgowan, they should be, but they are not. :)
[15:27] <aquarius> pmcgowan, not in any sensible way. Look at MDN, at the Chrome docs, at the IE docs, at Apple's docs. That's the level of documentation needed for a browser...
[15:28] <pmcgowan> aquarius, agree, just wishing to leverage our upstream more
[15:28] <pmcgowan> may be better with Oxide
[15:28] <aquarius> pmcgowan, yeah. They presumably don't have the resources.
[15:28] <aquarius> I thought Oxide was only for Canonical-supported webapps? I didn't think third-party apps got to use it?
[15:28] <daker> aquarius: i don't think so
[15:28] <KeanuTheOne> (1) Few comments about Cordova&Grid Unit ---> http://www.jonobacon.org/2013/08/22/ubuntu-in-a-nutshell-the-ubuntu-sdk-and-developer-story
[15:30] <KeanuTheOne> (2) [Ubuntu HTML5 Theme] Why the "Ubuntu Shape" is based on images, not on CSS3?
[15:30] <mhall119> KeanuTheOne: is (1) a question?
[15:31] <KeanuTheOne> On Jono page I find few interesting comments.
[15:31] <aquarius> KeanuTheOne, the Ubuntu shape isn't supported by CSS3 -- its curve is unique to Ubuntu and can't be done in CSS with border-radius, I don't believe. It could, I suppose, be done with border-image, but that's still images.
[15:31] <daker> KeanuTheOne: the Ubuntu Shape is somehow "impossible" to do in CSS3 AFAIK, but if you can do it that would be awesome
[15:32] <daker> mhall119: i was thinking about that, i'll do that
[15:32] <aquarius> As a data point, the reason I have not given any decent feedback on web apps stuff (other than that which I've sent to mhall119 etc) is that there is so little documentation that I don't know where to get started :( Google links to developer.ubuntu.com/webapps/ which doesn't even exist any more :( The webapps example on the page explains how to write a webapps script but doesn't explain what to do with
[15:32] <aquarius> that script once you've written it.
[15:32] <karni> lp:~karni/+junk/todo-html5 lp:~karni/+junk/todo-qt
[15:32] <aquarius> I did speak to alex-abreu a while back about how I'm happy to write blog posts about how to write a web app script and install it in my home folder once he tells me how to do that ;-)
[15:33]  * karni occasionally loses G+ stream
[15:34] <karni> alex-abreu: ah thanks
[15:34] <karni> I provided an example of HTML5 (ant Qt counterpart) for anyone interested. Really simple app, just to explore the SDK.
[15:35] <aquarius> This is going to be an unpopular opinion, but I think that documenting the existing HTML app story really well is more important than doing further development on it. :(
[15:37] <aquarius> mhall119, vw and vh will probably be fine instead of grid units, at least initially.
[15:37] <karni> aquarius: I feel you. One of crucial points of my feedback was just that, we need more docs, to help people ramp up on how to do it.
[15:37] <pmcgowan> karni, aquarius happy to get contributions
[15:38] <aquarius> pmcgowan, I've already offered to write stuff up, but I don't actually know what's done yet, and alex-abreu doesn't have time to chat to me about it :)
[15:39] <karni> pmcgowan: I know we're all swamped. In my case, sadly I've been reassigned to a very different project as soon as I provided the feedback. But I do hope my feedback (two e-mails, a number of bugs filed) will help the SDK team in general to prioritise tasks with end user in mind.
[15:39] <pmcgowan> karni, much appreciated
[15:40] <karni> pmcgowan: Always happy to help!
[15:40] <aquarius> pmcgowan, so I can't document things because I don't know where to get started! chicken, egg, egg, chicken. :)
[15:41] <karni> aquarius: I found looking at ubuntu-html5-theme helpful (although I know "documentation by code" might not be ideal), it gave me a start point.
[15:41] <daker> mhall119: sure
[15:41] <mhall119> thanks daker
[15:42] <aquarius> pmcgowan, if I have certain basic knowledge (how do I install a webapp script without being root; which unity web apis are available on 13.04, 13.10; where's the best place to get the latest code; how much of the CSS and JavaScript will be bundled with the platform and how much shoudl I include in my project; how do I test my web app on an Ubuntu desktop (loading it in the Ubuntu Browser)), then I am happy
[15:42] <aquarius>  to write a series of blog posts on building an HTML5 web app for Ubuntu Touch.
[15:43] <daker> aquarius: ping me later then i'll show you how to do that
[15:44] <aquarius> daker, ah, cool, you know how? sweet.
[15:44] <karni> me? ;)
[15:44] <karni> the a)b)c) yeah
[15:44] <sethj> karni, might want to name yourself on the pad ;)
[15:44] <karni> sorry
[15:45] <sethj> I mean, name your color
[15:45] <karni> done
[15:45] <aquarius> karni, where's the html5 theme these days?
[15:45] <daker> aquarius: yes
[15:45] <karni> aquarius: /usr/share/ubuntu-html5-theme
[15:45] <aquarius> karni, !! are there examples of how to use it?
[15:46] <karni> aquarius: only QR Code scanner and the dead simple todo that I posted are. No, not there.
[15:46] <alex-abreu> aquarius, there is a ubuntu-html5-theme-examples package
[15:46] <karni> aquarius: I just found it useful to know what is available, and know what I should write in plain HTML/JS VS using a theme component
[15:46] <karni> alex-abreu: uh! oh! \o/
[15:47] <aquarius> woah examples.
[15:47] <alex-abreu> aquarius, yeah ! :)
[15:47]  * aquarius installs the examples package. Nice one alex-abreu ;)
[15:47]  * karni shoots himself in the knee for not knowing that!
[15:48] <karni> alex-abreu: Not sure I know where the examples package would install :'(
[15:48] <karni> ah! /use/share/ubuntu-html5-theme/0.1/examples
[15:48] <aquarius> that's what dpkg --listfiles ubuntu-html5-theme-examples is for ;)
[15:48] <karni> aquarius: That's why you were my mentor haha ;D
[15:48] <KeanuTheOne> When will WebGL be supported on Cordova Ubuntu? Ubuntu Touch 13.10 (QtWebkit/Qt5.1)?
[15:50] <karni> aquarius: I'm embarassed I didn't know that command ;)
[15:50] <aquarius> mhall119, I don't want to be offensive here, but "a cat and mouse game of chasing every API out there" is what you signed up for when you decided to write a custom browser. ;-)
[15:51] <pmcgowan> not sure, need to check on webgl
[15:51] <pmcgowan> yes WebM will come with new video stack I am told
[15:53] <alex-abreu> pmcgowan, thx for the precisions
[15:54] <alex-abreu> karni, in /usr/share/ubuntu-html5-theme/examples ...
[15:54] <alex-abreu> karni, we need some desktop files for it
[15:54] <alex-abreu> for them
[15:54] <karni> alex-abreu: Good idea :)
[15:54] <alex-abreu> yeah
[15:56] <daker> or PhantomJS/SlimerJS
[15:58] <karni> Thank you guys
[15:59] <alex-abreu> thanks!
[15:59] <pmcgowan> thanks
[15:59] <daker> o/
[15:59] <aquarius> thank you, chaps
[15:59] <rvr> Thanks everyone for attending
[16:03] <balloons_uds> whomever wants to be in video discussion; https://plus.google.com/hangouts/_/1c7b1dc222f0af7298b58381248e92af19007788?authuser=1&hl=en
[16:13] <Letozaf_> balloons, I think videos are best :)
[16:14] <veebers> balloons_uds: will the results of the tutorials be available after the fact? i.e. videos or results in a blog post?
[16:14] <balloons_uds> http://developer.ubuntu.com/resources/tutorials/quality/how-to-write-autopilot-tests/
[16:15] <veebers> i.e. if someone can't make the tutorial at the time
[16:16] <veebers> balloons_uds: ah nice, cheers
[16:18] <fcole90---> Hello everybody =)
[16:18] <balloons_uds> hello :-)
[16:29] <mzanetti> balloons_uds: http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/qmltests/utils/Unity/Test/tst_UnityTest.qml
[16:30] <mzanetti> balloons_uds: sorry.. messed up
[16:30] <mzanetti> balloons_uds: this is actually the tests for that helpers
[16:30] <balloons_uds> ahh
[16:30] <mzanetti> http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/utils/modules/Unity/Test/UnityTestCase.qml
[16:31] <mzanetti> balloons_uds: ^
[16:40] <veebers> What sort of functionality would be available in the Base testcase?
[16:42] <veebers> elopio: sure, sounds good. Just getting an idea of what's expected :-)
[16:48] <veebers> elopio: that sounds like logging required from the QML level?
[16:50] <veebers> elopio: sure, how would the emulator for instance tell if the thing opened as expected?
[16:50] <veebers> elopio: other than having to introspect further etc.
[16:50] <veebers> elopio: perhaps I miss-understood the logging requirements
[16:52] <veebers> elopio: sure makes sense
[16:55] <balloons_uds> ty everyone
[18:02] <mhall119> bzoltan: QtCreator session hangout: https://plus.google.com/hangouts/_/eba45da2e2c7eb637c963e77cdff104e033812c8?authuser=1&hl=en
[18:02] <mhall119> ^^ anybody else who wants to talk about the QtCreator welcome screen and plugins can join too
[18:05] <zyga> hi
[18:05] <zyga> there's a pretty big delay I think
[18:05] <zyga> but it's live
[18:05] <zyga> and it works
[18:05] <zyga> so get rolling
[18:05] <mhall119> https://plus.google.com/hangouts/_/eba45da2e2c7eb637c963e77cdff104e033812c8?authuser=1&hl=en
[18:06] <zyga> I cannot join, I have some background noise over here
[18:06] <zyga> but I'm interested in seeing how one can jump into app development on ubuntu with html5
[18:12] <daker> zyga: i guess the html5 was 3 hours ago
[18:12] <daker> session*
[18:13] <zyga> huh?
[18:13] <zyga> ohhhh
[18:13] <zyga> yeah
[18:13] <mhall119> zyga: yeah sorry, we had to move stuff around
[18:13] <zyga> schedule was out of date
[18:13] <daker> zyga: :)
[18:14] <daker> zyga: you can find the record here http://summit.ubuntu.com/uds-1308/meeting/21965/appdev-1308-html5-offering/
[18:18] <zyga> thanks!
[18:20] <CheeseBurg> Is JuJu development in Qt Creator as well?
[18:34] <CheeseBurg> The tools section under resources on developer.ubuntu.com needs to be updated, it still shows Quickly
[18:43] <bzoltan> https://launchpad.net/qtcreator-plugin-ubuntu
[18:51] <CheeseBurg> When you talk about openGL template, are you expecting game development to happen in Qt Creator?
[18:53] <CheeseBurg> Just curious
[19:13] <wonderfulWidgets> because it is all qwidgets ->declaritive (just the welcomescreen) is a good idea to have TabStacks ? -> WebViews  ?
[19:13] <wonderfulWidgets> like have the mainwidget then have tabs and in the tab's have homepage and irc and core apps ect
[19:13] <wonderfulWidgets> like a metatab
[19:14] <wonderfulWidgets> or is the idea to have a bunch of buttons on the left ?