[15:04] <ubuntu-guy> can we have modules that we can drag and drop to easy start off creating apps?
[15:04] <mhall119> ubuntu-guy: there's going to be a session about that later today
[15:04] <mhall119> ubuntu-guy: http://summit.ubuntu.com/uds-1403/meeting/22136/ubuntu-component-store/
[15:04] <kenvandine> is summit down?
[15:05] <mhall119> if you're interested in helping us work out the details of that, please join
[15:05] <mhall119> kenvandine: not that I know of
[15:05] <mhall119> kenvandine: works here
[15:05] <kenvandine> not loading for me :/
[15:05] <ubuntu-guy> thanks will do
[15:05] <mhall119> kenvandine: no pages load?
[15:05] <kenvandine> none
[15:05] <mhall119> :/
[15:05] <mhall119> kenvandine: other ubuntu pages load for you?
[15:06] <kenvandine> oh... there now it loaded
[15:06] <kenvandine> 10 minutes i couldnt
[15:06] <mhall119> did you forget to use your manners?
[15:06] <mhall119> it's very picky about that
[15:06] <iBobX> where's the hangout link?
[15:06] <kenvandine> mhall119, i guess :)
[15:06] <kyleN> http://summit.ubuntu.com/uds-1403/meeting/22164/appdev-1403-releasing/
[15:07] <mhall119> if youwant to join the hangout, and have something to add, you can join at https://plus.google.com/hangouts/_/hoaevent/AP36tYeyOMZOQu5nuv4KbFTaNK5B5BhUlzky8d1Ql-Yu8jQVjCY38w?authuser=1&hl=en
[15:07] <mhall119> please mute yourself when you're not speaking though
[15:07] <ubuntu-guy> I would say release them when they are ready
[15:07] <iBobX> Thanks!
[15:11] <ChrisGagnon> did you try using qmltestrunner for ui testing of the sdk, when autopilot did not work?
[15:11] <kyleN> bzoltan, QUESTION: can you speak a little more about the idea of separating the tools (QtC and etc) from the UI Toolkit stuff? How was it organized? how will it be organized?
[15:12] <mhall119> kyleN: do you want to join the hangout?
[15:13] <bzoltan> ChrisGagnon: not yet, but soon we will investigate other options
[15:13] <t1mp> did the video start yet? I don't see it
[15:14] <mhall119> t1mp: it has
[15:15] <pmcgowan> Kaleo, yes that made sense
[15:15] <kyleN> yes
[15:15] <kyleN> can you mention frameworks specifically with APIs
[15:15] <Kaleo> kyleN, can you elaborate?
[15:16] <t1mp> I still don't see video on http://summit.ubuntu.com/uds-1403/meeting/22165/appdev-1403-uitk/ anyone else?
[15:16] <t1mp> argh
[15:16] <kyleN> the concepts of frameworks remains somewhat vague. yet devs need to state it in their manifest. how does stating it in the manifest relate to API selection at runtime and etc
[15:16] <t1mp> wrong session page. that's tomorrow :)
[15:18] <kyleN> good, that is the explanation I was looking for
[15:19] <pmcgowan> current framework is there with some exceptions, apis that need services or hardware thats no available
[15:19] <sergiusens> that would work only if there's some api validator to see if nothing outside of the framework is used
[15:19] <Kaleo> you should join the hangout ;)
[15:21] <mhall119> sergiusens: that would be done in the SDK, it would have to have separate API definitions that it uses to validate code
[15:21] <sergiusens> mhall119, so if I build my c++ plugin and that uses stuff outside of the framework; would that be checked against as well?
[15:22] <kyleN> QUESTION: can you discuss the separation of DEV ppa from RELEASED ppa and perhaps mention testing and other steps that may be taken to ensure RELEASED PPA quality
[15:24] <kyleN> and will code completion work for HTML5/JS apps too?
[15:25] <sergiusens> jono_, bzoltan that depends on a Qt5 for x86 built with gles
[15:25] <mhall119> sergiusens: stuff outside the framework should be in your project root, so yes it should
[15:26] <sergiusens> hack arounds :-)
[15:27] <mhall119> pad: http://pad.ubuntu.com/uds-1403-appdev-1403-releasing
[15:28] <sergiusens> jono_, that's being worked on; we need to multibuild qt5
[15:28] <sergiusens> too much code has armhf == gles and !armhf = gl
[15:29] <mhall119> ew
[15:29] <mhall119> sergiusens: and that's in upstream qt?
[15:30] <kyleN> QUESTION: will code completion in QtC work with HTML5/JS apps?
[15:30] <mhall119> heh, my phone has working alarms now....evidently I'll be getting a notice before all my calendar events :)
[15:32] <sergiusens> mhall119, packaging and almost anything tht compiles and links against qt5 that we use
[15:33] <sergiusens> mhall119, these: https://launchpad.net/~rsalveti/+archive/qt-gles-test
[15:33] <bzoltan> jono_: https://blueprints.launchpad.net/ubuntu/+spec/appdev-1403-releasing
[15:37] <bzoltan> kyleN: there will be a session 16:00 - 16:55 UTC  HTML5 SDK Roadmap ( App Development ) I would ask that from alex-abreu
[15:38] <kyleN> bzoltan, ok. it seems to span both domains: SDK and HTML5 runtime
[15:39] <kyleN> is the X86 emulator a DESKTOP or a phone or a tablet?
[15:39] <astronfestmon> i think so
[15:39] <iBobX> oops, server error...
[15:40] <lool> is raring still supported at all?!
[15:40] <jono_> weird I got kicked out
[15:40] <jono_> and cant rejoin
[15:40] <sergiusens> lool, raring shouldn't be supported
[15:40] <lool> raring is not supported anymore; quantal is still up for a couple of months
[15:41] <mhall119> jono_: try rejoining using your own account instead of UbuntuOnAir?
[15:41] <sergiusens> you can't even dput to raring anymore
[15:41] <Kaleo> did  I get kicked out?
[15:41] <lool> bzoltan: well let's not screw them but let's not spend time supporting them, the support path for them is to upgrade IMO
[15:41] <sergiusens> Kaleo, seems you have
[15:41] <lool> anyway, completely off topic, sorry  :-)
[15:41] <sergiusens> lool, but raring is EOL, you can't dput to it
[15:42] <lool> sergiusens: well exactly
[15:42] <jono_> mhall119, tried, I can't get in
[15:42] <sergiusens> lool, so it's impossible to support for real :-)
[15:42] <mhall119> jono_: huh, I can't even eject your frozen connection
[15:42] <jono_> odd
[15:42] <lool> I'm surprized launchpad still accepts raring uploads to PPAs
[15:42] <mhall119> jono_: can you watch the video at least?
[15:43] <sergiusens> mhall119, the stream only shows pmcgowan bzoltan and yourself
[15:43] <sergiusens> lool, it doesn't; well I couldn't
[15:44] <kyleN> QUESTION: now that we separate Qtc and tools fomr API, can we stop using "SDK" to include runtime stuff?
[15:44] <kyleN> SDK should be QtC and tools, I think
[15:44] <kyleN> D=Development, not runtime
[15:44] <pmcgowan> SDK includes the emulator images in my view
[15:44] <pmcgowan> which are test targets
[15:45] <pmcgowan> but the sdk runtime is in the images only as you say
[15:45] <jono_> mhall119, its ok, I think I got most of what I want out of the session
[15:45] <kyleN> ok, food for thought anyway
[15:45] <jono_> sounds like bzoltan has got it well handled
[16:00] <dholbach> dbarth, do you need help setting up the event?
[16:00] <alex-abreu> dholbach, whats the hg ?
[16:01] <dholbach> alex-abreu, mhall119 said he had asked dbarth if he could run it - so I asked dbarth now :)
[16:01] <dholbach> alex-abreu, I'm happy to set it up
[16:02] <dholbach> ok, doing it now - just a sec
[16:02] <dholbach> https://plus.google.com/hangouts/_/hoaevent/AP36tYfdCLyIpbF9imaNkUmbmkfITWHBxtfOqmxvAPxHhZlCIY8NIw
[16:03] <dholbach> ok, summit is updated
[16:03] <dholbach> alex-abreu, dbarth, kyleN: ^
[16:04] <aquarius> and we are live
[16:04] <dbarth> dholbach: ok
[16:04] <dbarth> dholbach: just arrriving, hang on
[16:04] <dbarth> dholbach: ant, kylen i guess
[16:05] <antdillon> I'm here and listening guys
[16:05] <dholbach> antdillon, cool
[16:05] <alex-abreu> antdillon, great
[16:05] <alex-abreu> antdillon, hopin if you want
[16:06] <dholbach> does anyone else want to join in ?
[16:06] <dholbach> blueprint is available here: https://blueprints.launchpad.net/ubuntu/+spec/appdev-1403-html5-sdk
[16:06] <dholbach> notes are going to be taken here: http://pad.ubuntu.com/uds-1403-appdev-1403-html5-sdk
[16:08] <dbarth> dholbach: https://docs.google.com/a/canonical.com/presentation/d/1cxdhwBJwaTikDQ_qFFCSLDllFG1u6_LOkq9PiLO5INg/edit#slide=id.g1d034350e_00
[16:14] <dholbach> any questions? any feedback? anyone who wants to join the session?
[16:18] <dholbach> is anyone taking notes?
[16:18] <hatch> QUESTON: what frameworks are you considering for responsive layouts? Pure? Bootstrap? etc...
[16:18] <astronfestmon> there's no any question.
[16:19] <aquarius> kyleN, responsive isn't really about portrait vs landscape; it's about screen sizes. A screen isn't landscape; it's just X px wide vs x/3 px tall :)
[16:19] <aquarius> media queries work fine -- don't invent a new responsive thing. Anyone developing HTML stuff should already know about this stuff ;)
[16:19] <dbarth> i'm taking notes here: http://pad.ubuntu.com/uds-1403-appdev-1403-html5-sdk
[16:20] <astronfestmon> QUESTION: with cordova framework can we do wrappers to detect any device pixel format?
[16:20] <astronfestmon> more spcific
[16:20] <astronfestmon> specific
[16:21] <astronfestmon> when we have a touch or laptop can we detect it
[16:22] <aquarius> kyleN, the sidestage doesn't matter. Your app should say "hey, I am in a window which is of size X by Y"
[16:23] <aquarius> ya, respond to the amount of real estate that you have
[16:23] <aquarius> totally right :)
[16:24] <aquarius> Making a bootstrap theme, and making sure that bootstrap works really well, would be ideal
[16:25] <daker> i am here
[16:25] <daker> o/
[16:25] <astronfestmon> hi. okay
[16:26] <dbarth> astronfestmon: just coming to your question next
[16:26] <astronfestmon> okay. thanks
[16:26] <dbarth> aquarius: up for it?
[16:26] <dbarth> daker: hey
[16:26] <aquarius> heh, daker and I were discussing translations the other day; the Moz b2g stuff, and jsgettext
[16:27] <aquarius> dbarth, up for what?
[16:27] <dbarth> bootstrap
[16:27] <dbarth> ?
[16:27] <aquarius> dbarth, I don't want to promise tht I'll have time for anything :(
[16:28] <dholbach> QUESTION: can we review the work items from last time (https://blueprints.launchpad.net/ubuntu/+spec/appdev-1311-html5-sdk) and see if there's still work to be done or stuff to be landed?
[16:28] <dholbach> QUESTION: feedback from another session: "Update Cordova template to be more Ubuntu-like (e.g replace the Cordova icon, make it do something useful, can be very simple though)" - can we make this a work item too or should it be a bug report?
[16:29] <dholbach> can you all help taking notes? http://pad.ubuntu.com/uds-1403-appdev-1403-html5-sdk - thanks!
[16:29] <dbarth> aquarius: nw
[16:29] <aquarius> I don't understand why compatibility with the rest of the Ubuntu project is useful, for gettext. App developers are not likely to use Launchpad and rosetta
[16:30] <astronfestmon> it's api
[16:30] <antdillon> If we are talking about DPI we can use media queries to get that
[16:30] <alex-abreu> astronfestmon, are you talking about DPR?
[16:30] <astronfestmon> yes i am
[16:30] <dholbach> aquarius, on the other hand, using Launchpad for translations is VERY nice and is where translators (loco teams) look at
[16:31] <alex-abreu> astronfestmon, not atm ... but this is something that we could include, there will be a runtime js binding
[16:31] <aquarius> dholbach, yeah, but we are not exactly encouraging app developers to use launchpad these days
[16:31] <dholbach> well we could do that in our docs
[16:31] <antdillon> I dont think m,y mic is working
[16:31] <dholbach> I was just bringing it up as a side-point :)
[16:31] <aquarius> antdillon, we need to be very sure that all devices accurately report their details to the platform so that the platform can correctly do media queries, mind
[16:32] <astronfestmon> if we use media queries it's assynchronous right
[16:33] <dbarth> astronfestmon: yes, like pretty much everything in the JS engine i guess
[16:33] <astronfestmon> okay. thanks
[16:33] <dbarth> astronfestmon: you have concerns about that?
[16:33] <astronfestmon> yes a little
[16:34] <astronfestmon> because the media queries are not my strength inside an app
[16:34] <antdillon> aquarius, Sure, I agree it all system settings accessible via the api would be great
[16:34] <antdillon> aquarius, But for layout and styling media queries would work
[16:35] <dbarth> antdillon: but should we use dpi/media queries, or rather rely on the grid unit system preferably?
[16:35] <aquarius> On code completion, etc, building in jshint and htmllint would be great, because that will pick up on lots of thnigs
[16:35] <dbarth> ie, dpi is low-level and maybe important for fullscreen apps / games
[16:36] <dbarth> but for regular UIs, shouldn't GU be prefered?
[16:36] <hatch> the issue with DPI's is that you need it to know what resolution of static images to use
[16:37] <hatch> that's why you need some representation of dpi
[16:37] <astronfestmon> QUESTION: if we use dpi for games WEBGL is better than a  UI stylish for it. Or Canvas?
[16:37] <antdillon> dbarth, A use case for dpi media queries is for responsive images
[16:37] <aquarius> man, seriously, half of what you're describing on the hangout is handled by jshint :)
[16:39] <dbarth> antdillon: ok
[16:39] <dbarth> aquarius: jshint, nice
[16:40] <aquarius> fine, it doesn't offer type tracking, but that's because YOU DON't NEED TYPE TRACKING because this isn't C ;-)
[16:40] <antdillon> It would be good to run this on submit at least
[16:41] <alex-abreu> aquarius, we need to validate the API calls & stuff like that
[16:41] <alex-abreu> aquarius, and have completion
[16:41] <alex-abreu> that's the gist of any completion tool
[16:41] <aquarius> alex-abreu, no, no we don't. Nobody else does ;)
[16:41] <alex-abreu> either dynamic eval & stuff
[16:41] <alex-abreu> or somesort of type hiints
[16:41] <aquarius> code completion is fine -- that's what TAGS files are for and so on, right?
[16:41] <alex-abreu> aquarius, wrong :) ... check out e.g. codemirror
[16:41]  * aquarius laughs
[16:42] <aquarius> I like Sublime Text, myself :)
[16:42] <alex-abreu> aquarius, I am not sure that etags is something that I'd like to see again :)
[16:42] <alex-abreu> no tags ! :)
[16:42] <antdillon> Are we not going to use grid units for HTML5?
[16:42] <aquarius> I honestly don't think that we need intellisense
[16:42] <hatch> I'm with aquarius :)
[16:42] <alex-abreu> aquarius, thats the thing ... no intellisense, but at least something interesting
[16:42] <aquarius> I can't see how we can use grid units for HTML5, becuase the CSS parser doesn't know about them
[16:42] <antdillon> I think the grisd is important
[16:42] <alex-abreu> aquarius, as much as we can get :)
[16:42] <antdillon> grid*
[16:43] <aquarius> unless we *insist* that all the CSS is actually SASS
[16:43] <antdillon> Do we have an example app packaged?
[16:43] <astronfestmon> yes i think that about SASS
[16:43] <aquarius> alex-abreu, I see your point about not using etags, etc, yeah; I just don't want someone to spend a million years trying to write a type inferencer for JavaScript :P
[16:44] <hatch> if you need/want a type inference system for js there are tools for that already - TypeScript for example
[16:44] <antdillon> I agree with not using grid units (as this would need "inventing") but % grid are common to html developers
[16:45] <antdillon> We can use a simple % grid
[16:45] <astronfestmon> in qml can we develop grids with no html tags right?
[16:45] <aquarius> antdillon, yeah, certainly, using a grid is a common idea. Bootstrap, 960 grid, etc
[16:45] <aquarius> but that doesn't need to be part of the SDK
[16:45] <aquarius> If I want to use bootstrap, I can.
[16:45] <hatch> right
[16:45] <astronfestmon> ok
[16:45] <antdillon> I would like to use the same naming as bootstrap to help developers
[16:45] <aquarius> If we want to use grid units in CSS, we need to wait for var() support. :) https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_variables
[16:46] <antdillon> I think the grid should be part of the SDK as we want to bring a common grid layout to apps
[16:47] <alex-abreu> aquarius, yes this is something that is not standardized I think
[16:47] <aquarius> antdillon, if the grid is named for bootstrap then I think it should *be* bootstrap.
[16:47] <antdillon> At least as a best use case
[16:47] <astronfestmon> I think that so.
[16:47] <hatch> You don't want to lock people into any grid system, grids will not work for all applications
[16:47] <hatch> people need to be able to customize them
[16:47] <aquarius> wow. Totally disagree with all of you. If you want to insist that people use Ubuntu-specific technologies in an HTML app, then it's not HTML any more. It's just an Ubuntu-specific layouit language which looks a lot like HTML.
[16:47] <aquarius> agreed with hatch
[16:48] <antdillon> aquarius, Yes happy to use that I just dont want the devleopers to have to learn a new naming convention for the grid
[16:48] <dbarth> aquarius: the point here is to not have html5 developers behind, when it comes to having a native Ubuntu look
[16:48] <dbarth> i for one want to develop an app with the nice layout, without (hopefully) to dive into a load of css for that
[16:49] <dbarth> but then, we don't want to make that a pre-requisite for runninng your app in the container
[16:49] <antdillon> aquarius, I dont mean force them to use it but have it in the SDK to use if the developer doesnt mind which grid they use
[16:49] <aquarius> Sadly, you do have to support plenty of web browsers. Because if anyone wants to write an Ubuntu ONLY app, they're going to use QML for it. If they're usnig HTML5 to write an app for Ubuntu, they'll likely be using that app on multiple platforms,
[16:50] <antdillon> Good question aquarius, what browsers do we support?
[16:50] <aquarius> antdillon, yeah. It's not about browsers you suport -- you support the Ubuntu browser, that's it.
[16:51] <aquarius> It's that app developers who are using the Ubuntu engine to deliver apps will likely also be delivering that app on other platforms, so they will not want to add Ubuntu-specific things like grid units to it, because those won't work elsewhere.
[16:51] <antdillon> aquarius, I imagined as long as it worked on the latest release of blink its good to use
[16:51] <aquarius> (Ubuntu stuff which is *added*, like the Apple meta tags, are fine)
[16:52] <antdillon> dbarth, Have you guys worthed on the video player widget?
[16:53] <aquarius> The reason for wanting the Media service and the Download service is not so you feel like an Ubuntu app; it's so you can do things in the background :)
[16:53] <antdillon> dbarth, I say that because the web team here have just developed a played skinned to match the phones
[16:53] <aquarius> why does URL dispatcher need to be accessible to HTML5? Why can't I just do "location.href='someurl://whatever'"? :)
[16:54] <hatch> aquarius that's kind of the hulk smash approach, if it's within your own app you want to use pushstate
[16:54] <aquarius> hatch, the url dispatcher is for talking between apps
[16:54] <antdillon> Everyone loves a todo app!
[16:55] <aquarius> hatch, agreed on pushstate for my UI urls :)
[16:55] <hatch> ohh ok, sorry carryon :)
[16:55] <antdillon> Angry birds ... done
[16:55] <antdillon> :)
[16:55] <aquarius> the most important thing that you guys could do is make Oxide happen. :)
[16:56] <aquarius> then things like XHR work properly :P
[16:56] <aquarius> You can't build a U1 app without Content Hub and the Download API
[16:56] <aquarius> Trust me on this.
[16:56] <aquarius> Speaking as the world expert on building U1 apps ;)
[16:57] <antdillon> Example app?
[16:57] <alex-abreu> aquarius, we have the contenthub & we will have the download manager
[16:57] <aquarius> Once those things exist, it's reasonably easy -- I know this because I've done it about eight times :P
[16:57] <aquarius> alex-abreu, yep!
[16:57] <aquarius> alex-abreu, do you have the *new* content hub stuff?
[16:57] <alex-abreu> aquarius, not yet, in the works ... :)
[16:57] <alex-abreu> we have the old
[16:57] <aquarius> I could probably be talked into writing a U1 HTML5 app.
[16:57]  * dholbach notes down a work item for aquarius
[16:57] <aquarius> since I have done it before about three times :P
[16:59] <aquarius> dholbach, go for it
[16:59] <antdillon> Im happy with that
[16:59] <antdillon> Great thanks guys!
[16:59] <antdillon> Ill get my mic working!
[16:59] <astronfestmon> me too
[16:59] <hatch> great chat everyone, thanks!
[16:59] <alex-abreu> thx guys !
[16:59] <aquarius> thank you, chaps
[17:00] <alex-abreu> great input
[17:00] <alex-abreu> inputs
[17:00] <astronfestmon> thank you all
[17:00] <hatch> QUESTION: How do people get more involved in this?
[17:00] <daker> bye
[17:00] <dbarth> aquarius: just noticing your message about u1; can we talkabout that next?
[17:00] <aquarius> hatch, hang out with daker and alex-abreu and look for stuff to do :)
[17:00] <alex-abreu> hatch, you can reach us in #ubuntu-webapps
[17:00] <aquarius> dbarth, certainly -- happy to talk about it
[17:00] <dbarth> see how we can share work here
[17:01] <alex-abreu> hatch, talk to me or yeah daker
[17:01] <dbarth> hatch: bzr branch
[17:01] <dbarth> hatch: standard ubuntu way
[17:01] <alex-abreu> hatch, we would love to have extra help / inputs
[17:01] <dbarth> hatch: you can email us on the webapps list as well, and see on irc #ubuntu-webapps as well
[17:01] <aquarius> dbarth, what would you like to know?
[17:02] <dbarth> aquarius: review the scope of what it should do
[17:02] <dbarth> aquarius: knowing where the dragons live
[17:02] <dbarth> that kind of things
[17:02] <hatch> thanks joined the channel
[17:02] <dbarth> hatch: see you there
[17:02] <hatch> I'm on the Juju UI team btw
[17:03] <dbarth> hatch: ah nice
[17:03] <dbarth> this UI is brilliant
[17:03] <alex-abreu> hatch, oh tremendous!
[17:03] <hatch> :-)
[17:04] <aquarius> dbarth, log in to U1 to get an oauth token; cache the token; hit the API to retrieve your list of files and folders; cache that data; provide a pagestack to navigate down into folders; refresh button to refresh the cache; (stage 1) allow downloading a file from U1; when you elect to download a file, calculate a signed URL for it and hand that to the contenthub and download daemon.
[17:04] <aquarius> dbarth, stage 2: allow sharing files via public url; allow uploads to U1
[17:04] <dbarth> aquarius: sounds like a plan ;)
[17:04] <aquarius> but stage 1 would get a lot of people up and running :P
[17:04] <dbarth> the first part i remember from previous use of u1db
[17:04] <aquarius> dbarth, I wrote a QML U1 app in a day a couple of weeks ago, but I put it on hold until the download and content APIs are available ;)
[17:05] <aquarius> so I can do the same with HTML.
[17:05] <dbarth> oh i see
[17:05] <aquarius> you need those, because it is useless to have the U1 app download files for itself.
[17:05] <aquarius> you only ever want to download files in order to give them to some other app :)
[17:06] <aquarius> I spent a bunch of time talking to kenvandine about this use case for the content hub api :)
[17:06] <alex-abreu> aquarius, the download manager is def something that I want to hev quickly now that it has reached a stable/usabel state, the rest you have already pretty much
[17:06] <aquarius> it needs the New Content Hub Stuff, but that's hopefully coming soon
[17:06] <aquarius> alex-abreu, yeah
[17:16] <kenvandine> alex-abreu, in my content-hub roadmap session, i assigned a work item for you for the bindings update :)
[17:16] <alex-abreu> kenvandine, oh you did :)
[17:16]  * aquarius laughs
[17:16] <aquarius> drive-by work item assignment :P
[17:16] <alex-abreu> kenvandine, when was the session ? during the html5 one ?
[17:17] <alex-abreu> :)
[17:17] <kenvandine> yes
[17:17] <kenvandine> aquarius, quiet or i'll assign one to you :)
[17:17] <dbarth> great minds
[17:17] <aquarius> kenvandine, hey, I was not concentrating and now I have to write a U1 app in HTML5. Which needs the content hub ;)
[17:17] <kenvandine> alex-abreu, your task is the biggest blocker for our landing... no pressure
[17:18] <kenvandine> aquarius, woot!
[17:18] <dbarth> aquarius: ok, so if you've got most of the u1 app, the simplest way to share is to identify what you miss and we can provide
[17:18] <dbarth> aquarius: like content hub
[17:18] <dbarth> aquarius: download manager i guess
[17:18] <dbarth> aquarius: and you say you don't need grid units
[17:18] <kenvandine> dbarth, i've already added features to the hub for aquarius
[17:18] <aquarius> dbarth, content hub and download API are the critical ones. Non-critical: some way to get the U1 credentials from the system; some way to securely store a token.
[17:19] <alex-abreu> aquarius, we have an OA binding
[17:19] <dbarth> aquarius: but i will challenge you to have a layout that is the same as it would on qml
[17:19] <alex-abreu> already
[17:19] <dbarth> aquarius: ;) so what would that take?
[17:19] <aquarius> dbarth, I can't *have* grid units. I do layout in CSS, because That's What You Are Supposed To Do, and CSS can't do grid units.
[17:19] <kenvandine> alex-abreu, in an html5 is there a way to control the keyboard?  i'm playing with an html5 app that as a text input, but the keyboard covers it
[17:19] <aquarius> alex-abreu, yeah, but U1 credentials aren't in OA, I don't believe.
[17:19] <kenvandine> in qml we can control where it binds
[17:19] <dbarth> aquarius: what's missing in the OA api for that?
[17:19] <aquarius> dbarth, what's missing is that the U1 credentialsa ren't stored in OA
[17:20] <kenvandine> aquarius, they aren't ?
[17:20] <aquarius> dbarth, but I don't know where SSO credentials *are* stored
[17:20] <pmcgowan> aquarius, yes they are
[17:20] <kenvandine> i thought they were
[17:20] <aquarius> pmcgowan, rly?
[17:20] <dbarth> you shouldn't know really
[17:20] <kenvandine> yes!
[17:20] <aquarius> pmcgowan, I can ask OA for my U1 username and password and get it?
[17:20] <pmcgowan> or do I misunderstand
[17:20] <kenvandine> aquarius, we needed that for the click store
[17:20] <dbarth> aquarius: which part of the creds do you need?
[17:20]  * aquarius looks astounded
[17:21] <kenvandine> look at your u1 account in system-settings, it should display your username
[17:21] <dbarth> aquarius: the identity token, should be there
[17:21] <hatch> kenvandine you may be able to listen for the focus event on the input then preventDefault() on the event object
[17:21] <aquarius> there they are, in System Settings > accounts
[17:21] <aquarius> ah
[17:21] <dbarth> aquarius: the app tokens, should not, should be in your app
[17:21] <aquarius> now I need to see whether I can use the app token!
[17:21] <aquarius> rock and roll.
[17:21] <dbarth> aquarius: and here we have the example of the reminders.app which is using the new api key approach
[17:22] <dbarth> aquarius: where apps provide their own app keys to OA for the initial auth. phase
[17:23] <aquarius> OK, am now looking into the OA bindings :)
[17:23] <aquarius> I wish the HTML console was reflected into the QML console so I could see console.log debugging from inside the SDK rather than having to spin up an inspector!
[17:23] <alex-abreu> kenvandine, not atm (keyboard), but I could add a binding ... just ask & file a bug :)
[17:23] <kenvandine> hatch, i want the keyboard to show, but i want to ensure the UI isn't covered
[17:24] <kenvandine> will do
[17:24] <alex-abreu> aquarius, thats the idea behind the qtc integration that we plan to work on
[17:24] <kenvandine> i want it to do what the qml does in our sdk
[17:24] <hatch> kenvandine ohh yeah that's a bug, it should scroll into view
[17:24] <dbarth> aquarius: that inspector window is next on my list
[17:24] <aquarius> wicked
[17:24] <dbarth> aquarius: weirdly i couldn't get it to work last time i hacked on qtc-plugin
[17:24] <dbarth> but qtwebkit should be able to run that i'm told
[17:25] <kenvandine> hatch, it could just be something about the app, i just modified an existing html5 app
[17:25] <aquarius> bah!
[17:25] <dbarth> aquarius: we'll talk about that with kyleN in the next session i guess
[17:25] <aquarius> what event do I have to wait for, for window.external to become available?
[17:25] <kenvandine> not sure if i can change something in the html to make the platform dtrt
[17:25] <hatch> kenvandine well typically (on other platforms) when the keyboard opens, the focused element is scrolled into view above the keyboard
[17:26] <hatch> if there is a 'keyboard-open' event you could animate the scroll I suppose :)
[17:26] <aquarius> erm.
[17:26] <aquarius> I can say "run html5 application on device"
[17:26] <aquarius> how do I *stop* it?
[17:26] <kenvandine> aquarius, upstart-app-stop ?
[17:26] <kenvandine> :-D
[17:26] <aquarius> close application on device is greyed out
[17:26] <alex-abreu> aquarius, 'ubuntu-webapps-api-ready' is the evnt name
[17:27] <kyleN> aquarius, a running app on device displays on the Applications page
[17:27] <kenvandine> hatch, so maybe in this app the element i care about isn't really focused?
[17:27] <aquarius> alex-abreu, fired on window? document?
[17:27] <alex-abreu> aquarius, document
[17:27] <kyleN> long press on it causes an 'X' in top left corner
[17:27] <alex-abreu> aquarius, this is abug then (if stops works for qml apps)
[17:27] <aquarius> kyleN, yeah, but I should be able to kill it from Ubuntu SDK :(
[17:27] <kyleN> yes :)
[17:27] <aquarius> alex-abreu, yeah, stop works for qml apps
[17:27] <hatch> kenvandine I'm not sure, it's entirely possible it is a bug
[17:28] <aquarius> if I run-on-device from Ubuntu SDK, then it lets me run-on-device again, which suggests that Ubuntu SDK isn't registering corectly that the app *is* running
[17:28] <alex-abreu> aquarius, its a bug then, you can file one in qtcreator-plugin-ubuntu LP
[17:28] <dbarth> aquarius: file a bug, i monitor those daily
[17:29] <dbarth> uh, what alex-abreu said
[17:32] <aquarius> will file a bug shortly
[17:34] <aquarius> holly sheet.
[17:34] <aquarius> there's my U1 account.
[17:34] <aquarius> Nice.
[17:34] <aquarius> How do I get the token from it?
[17:34] <aquarius> http://developer.ubuntu.com/api/html5/sdk-14.04/OnlineAccounts.Account/ is... not the most detailed piece of documentation I have ever seen ;)
[17:37] <aquarius> https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1290965 filed, dbarth
[17:37] <udsbotu> Launchpad bug 1290965 in qtcreator-plugin-ubuntu ""Run on device" for HTML5 apps not working right; app cannot be stopped" [Undecided,New]
[17:42] <aquarius> YEAAAH I have u1 credentials. Rock and roll.
[17:42] <aquarius> man, that's excellent.
[17:43] <aquarius> OK, I can write a U1 app. Don't need to do sign in. SUperb.
[17:48] <alex-abreu> aquarius, yeah ! :)
[17:50] <mhall119> aquarius: https://plus.google.com/hangouts/_/hoaevent/AP36tYdvimJo9VVSLE5Moms6GheyPZT-mtRfIhxxVZq1DOHz-1bXKQ?authuser=1&hl=en
[17:52] <aquarius> ?
[17:52] <aquarius> omg is it my session?
[17:52] <aquarius> ok :)
[17:55] <nik90> aquarius: yes indeed
[17:56] <mhall119> if anybody wants to be on the hangout: https://plus.google.com/hangouts/_/hoaevent/AP36tYdvimJo9VVSLE5Moms6GheyPZT-mtRfIhxxVZq1DOHz-1bXKQ?authuser=1&hl=en
[17:56] <mhall119> we'll be starting in a few minutes
[18:01] <dbarth> aquarius: ok
[18:03] <iBelieve> I can't join the video session, but I've very interested in an idea like this. I wrote very basic component manager last year called Code Units and I use it all the time on my projects to pull in other code I want to use
[18:03] <cwayne> i think choosing an online-account to log into is a good example too
[18:03] <dobey> what about licensing?
[18:04] <mhall119> use the pad guys
[18:04] <mhall119> http://pad.ubuntu.com/uds-1403-ubuntu-component-store
[18:04] <nik90> iBelieve: pls provide link to code units
[18:05] <nik90> iBelieve: also append it to the pad
[18:05] <iBelieve> nik90: https://github.com/iBeliever/devutils, it's the code command
[18:07] <nik90> mhall119: ^^
[18:14] <CheeseBurg> I agree with mhall
[18:14] <dobey> aquarius: but what if i *want* to write malicious apps using malicious components?!
[18:15] <dobey> mhall119, aquarius: the "gatekeeper" doesn't have to be human
[18:15] <mhall119> dobey: what could it be?
[18:15] <dobey> a bunch of scripts
[18:15] <dobey> it's not like humans can read compiled binaries anyway
[18:16] <dobey> well, the click store has scripts that does certain checks
[18:17] <CheeseBurg> Can we not test the components before putting in the component store?
[18:17] <CheeseBurg> automated?
[18:18] <ssweeny> what about a rating system similar to apps, where if someone finds a problem with a component they can give it 1-star and mention that it's spyware or whatever
[18:20] <dobey> aquarius: you don't need a web UI for ratings/reviews
[18:22] <dobey> ucs rate 1 'this thing is rubbish'
[18:23] <dobey> it wouldn't be difficult to build in python
[18:23] <dobey> that's rubbish
[18:23] <kenvandine> it would bundle it in your source right?
[18:24] <dobey> it needs a central store, and has to be delivered over a secure protocol like HTTPS
[18:24] <dobey> especially if it's going to accept binaries
[18:25] <kenvandine> they shouldn't pull directly from soruce branches... make them download an archive with a particular structure
[18:25] <kenvandine> s/soruce/source/
[18:25] <dobey> yeah
[18:25] <kenvandine> so released archives
[18:25] <kenvandine> would be preferable
[18:25] <dobey> you don't want people shoving binaries into VCS all the time
[18:25] <kenvandine> yeah... and i want to be able to specify the version of the component
[18:25] <kenvandine> not tip
[18:25] <kenvandine> aquarius, ^^
[18:26] <dobey> aquarius, mhall119: yes, you can grab a tarball off launchpad
[18:26] <dobey> without manually having to upload one
[18:26] <kenvandine> dobey, sweet
[18:26] <kenvandine> but i still want reliably versions... real declared stable releases
[18:26] <kenvandine> so if i pull dobey's component and know version 1.0 works
[18:27] <kenvandine> i don't want to get a newer version of 1.0
[18:27] <dobey> aquarius: bzr export lp:foo blah.tar.gz
[18:27] <ssweeny> LP let's you download a tarball of a bzr rev
[18:27] <dobey> yes, you can download a tarball of any rev
[18:27] <kenvandine> aquarius, but i want to know the downloaded file will be the same if i download 1.0 next week
[18:28] <CheeseBurg> So is there any type of quality control from Canonical or just from the community?
[18:28] <kenvandine> dobey, are you volunteering to implement that in LP ?
[18:28] <ssweeny> aquarius, https://bazaar.launchpad.net/~unity-team/unity-scope-mediascanner/trunk/revision/67?start_revid=67 look for "download tarball"
[18:28] <kenvandine> true
[18:28] <asomething> LP tarball links look like: https://bazaar.launchpad.net/~andrewsomething/typecatcher/trunk/tarball/178
[18:29] <kenvandine> so we trust the maintainer
[18:29] <dobey> yeah, taht
[18:29] <kenvandine> basically i'm saying i want you to provide a link to a versioned archive
[18:29] <kenvandine> and that's what the store has
[18:29] <kenvandine> and each new version has a different url
[18:29] <kenvandine> but no smarts built into the store, just a link :)
[18:29] <kenvandine> in the manifest or something
[18:30] <kenvandine> aquarius, i think we're saying the same thing
[18:30] <kenvandine> so who cares if it comes from github or LP
[18:30] <dobey> i do.
[18:30] <kenvandine> dobey, you're special :)
[18:30] <asomething> you can even link just to the tip of trunk https://bazaar.launchpad.net/~andrewsomething/typecatcher/trunk/tarball
[18:31] <CheeseBurg> I think this is a extremely good idea. Think how easy it will be to get new developers or wannabe developers.
[18:31] <dobey> kenvandine: i just don't want it to be arbitrary URLs, because it means people will use insecure URLs
[18:31] <kenvandine> so you want to enforce https
[18:31] <kenvandine> oh, we should include an sha1sum or something in the manifest
[18:31] <dobey> valid https, yes
[18:32] <dobey> because the original component might not be malicious, but if someone MITMs your download and sends you malicious code instead, well :)
[18:33] <kenvandine> i really don't care if archive downloads happen over https... there isn't sensitive data, but we need to be able to verify the downloaded archive
[18:33] <kenvandine> dobey, then verification fails
[18:33] <dobey> kenvandine: how would it verify it?
[18:33] <kenvandine> sha1sum
[18:33] <kenvandine> oh... i guess that would be up to the developer
[18:33] <dobey> kenvandine: but where is that delivered from?
[18:33] <kenvandine> unless we had a wrapper tool that did the download
[18:34] <kenvandine> the manifest when the component is submitted to the store would include a url to the archive and the sha1sum
[18:34] <kenvandine> not a url to a sha1sum
[18:34] <kenvandine> so we can reliably verify the downloaded archive matches what was submitted to the store
[18:35] <kenvandine> and if the archive changes at the same url, it fails
[18:35] <dobey> well, i'd do sha256 or something (since sha1 is broken), but as long as it's coming from a secure stream, it's acceptable
[18:35] <kenvandine> sure... anything like that
[18:38] <dobey> aquarius: ucs could provide a CMake module and just be an integrated part of the build process
[18:39] <netcurli> if you don't verify whether the component changes, then you should include them in the source
[18:39] <dobey> aquarius: so just have the components.json and ucs pulls them when you build
[18:39] <aquarius> woah! http://bazaar.launchpad.net/~sil/+junk/ucs-demo-app/tarball/2 works.
[18:40] <aquarius> Thank you dobey, ssweeny, asomething for correcting me :)
[18:40] <dobey> told you :)
[18:41] <ssweeny> :)
[18:45] <dobey> mhall119: solr would probably be fitting
[18:46] <dobey> aquarius: is that black brick next to you the new art piece?
[18:47] <dobey> to your left in front
[18:47] <dobey> there's a cube
[18:48] <nik90> aquarius is too excited at the moment!
[18:48] <dobey> yes
[18:48] <nik90> you asked him about his computer!
[18:48] <nik90> lol
[18:48] <dobey> it looks pretty black
[18:52] <dobey> aquarius: you can write it in c++!
[18:56] <dobey> time is up
[19:00] <dbarth> balloons: ping? can you ping us the hangout link when ready?
[19:00] <balloons> dbarth, https://plus.google.com/hangouts/_/hoaevent/AP36tYec1w53epatZ3C8nZ_FapqL0EQVY0KX0Ef223gpehp6sIemEQ?authuser=0&hl=en
[19:01] <mhall119> dobey: want to jointhe API website discussion?
[19:02] <dpm> https://plus.google.com/hangouts/_/hoaevent/AP36tYd0F4PHPAhxJ3WVvkHEiV5W9xHctARZHR937CY7NulnlfFDcg
[19:02] <nik90> balloons: is this the core apps review session?
[19:02] <dpm> for anyone wanting to join the core apps review session ^
[19:02] <dpm> nik90,
[19:02] <dpm> yes
[19:02] <dobey> mhall119: i wasn't planning to, but i can
[19:04] <nik90> core apps devs you guys here?
[19:04] <nik90> m-b-o1:  ^^
[19:04] <dpm> http://pad.ubuntu.com/uds-1403-core-apps-review
[19:06] <rpadovani> dpm, nik90, sorry, dinner in ~15 minutes here :/
[19:07] <dpm> rpadovani, no worries :)
[19:38] <nik90> iBelieve: anythings to mention for the file manager
[19:38] <nik90> iBelieve: that's next on list
[19:39] <iBelieve> nik90: thanks, I'll add a couple important items for File Manager that we're currently working on
[19:40] <iBelieve> nik90: or is just dam adding stuff to the pad?
[19:40] <iBelieve> nik90: **dpm
[19:40] <nik90> iBelieve: you can go ahead
[19:40] <iBelieve> nik90: ok
[19:41] <dpm> iBelieve, that'd be excellent, thanks!
[19:43] <iBelieve> dpm: done
[19:44] <dpm> iBelieve, awesome, thanks!
[19:44] <nik90> iBelieve: Are you guys planning to add keyboard shortcuts?
[19:44] <iBelieve> nik90: some work, (such as Ctrl+L), but yeah, that is important
[19:46] <iBelieve> dpm: also just added a link to our team's Trello board
[19:56] <dpm> iBelieve, perfect, I mentioned it on the hangout too. Looking great!
[19:57] <iBelieve> dpm: thanks for mentioning it
[19:59] <dpm> np :)
[20:00] <dpm> thanks everyone, a very successful start to UDS! \o/