[00:51] <doomlord> Whats the status of ubuntu on tablets
[00:52] <holstein> !tablet | doomlord
[00:52] <holstein> doomlord: ignore the part about "#ubuntu is for support only"
[00:53] <holstein> i juse wanted to get the names correct...
[00:53] <doomlord> ok great
[00:53] <holstein> just*
[01:03] <mainerror> wow, the SDK is pretty amazing.
[01:04] <mainerror> I mean Qt is pretty amazing.
[01:05] <bkc_> Qt is actually not that amazing, it's overcomplicated :P
[01:05] <mainerror> Coming from the Android development world it feels like nothing compared to that. Especially working with lists.
[01:05] <bkc_> sure, Java is a completely different mess :P
[01:06] <mainerror> I prefer the JSON-like object declaration of QML
[01:06] <mainerror> Oh, and that I can use JavaScript functions in QML :)
[01:07] <mainerror> I'm sure Qt has it's ugly parts as well, just as every language/framework has but for now, as much as I've seen it looks very good.
[01:14] <doomlord> QML looks more elegant than full json
[01:15] <doomlord> much better not having keys quoted
[01:18] <bobweaver> one can use json in qml2
[01:20] <bkc_> json-keys aren't qouted? :/
[02:57] <doomlord> json-keys are all quoted
[03:10] <bkc_> they are?'
[03:10] <bkc_> so that would be { "somekey"=1.0f } then? :/
[03:10] <bkc_> because { somekey=1.0 } works just fine
[03:11] <bkc_> (nvm the 'f' on the first one, old habit :P)
[03:12] <bkc_> baah, I need some sleep, cya
[03:24] <bobweaver>  \
[03:25] <bobweaver> JSON.parse()
[03:25] <bobweaver> JSON.stringify()
[03:40] <doomlord> {somekey=1.0}  - this is not legal JSON. true JSON is always quoted. maybe everyone who writes a jSON parser agress with me and thinks its crazy and accepts unquoted keys :)  but real JSON is always quoted
[03:41] <bkc_> huuh, well fuck me on a dead horse...
[03:42] <bkc_> uhm... ops... might be the wrong channel for such proclamations :P
[03:43] <doomlord> i mean personally if i wrote a JSON parser i would definitely accept unquote
[03:43] <bkc_> likewise
[03:43] <bkc_> my json-files actually "depends" on it... easy fix though :)
[03:43] <doomlord> the format is so much better distinguishing between symbols,strings,ints and floats..
[03:44] <bkc_> indeed
[03:45] <doomlord> i liked the way clojure did its literals.. very similar.
[03:46] <doomlord> so ubuntu phone is imminent..
[03:46] <doomlord> tommorrow,right?
[03:47] <bkc_> well, fo me it's about 19h15m until midnight wednesday->thursday so :)
[03:51] <doomlord> i wonder if other linux distros will do similar
[03:52] <doomlord> presumably the canonical code just goes out into the community the same as all other linux source
[03:52] <bkc_> preferably :)
[03:52] <bkc_> but some other distros don't have a fixed set of applications
[03:52] <bkc_> like archlinux for instance :)
[03:53] <doomlord> i would like to know if there's any attempt to run regular gnu-linux desktop apps in tablet mode
[03:53] <bkc_> yes
[03:53] <doomlord> they wouldnt be as slick thats for sure, but its not impossible to tweak ui for touchscreen
[03:53] <bkc_> native apps are available
[03:54] <doomlord> as far as i can tell. a phone/tablet UI simply means, making buttons taller. (and to make it a GOOD ui, fill that extra space with something useful)
[03:54] <bkc_> they'll probably just map to a mouse-pointer, scroll-wheel and perhaps zooming just like any other touchpad :)
[03:54] <doomlord> an avoid right--click menus of course
[03:55] <bkc_> right-click is just a long press ;)
[03:55] <doomlord> scroll wheel = 2fingers right
[03:55] <bkc_> right
[03:55] <bkc_> the hard thing is with hovering/draging :/
[03:55] <bkc_> hovering vs dragging*
[03:56] <doomlord> yeah. dragging is terrible
[03:56] <doomlord> the next big step forward will be when screens can detect fingers are near.. or differentiate the size of contact patch (light press vs heavy press)
[03:56] <bkc_> some actally "fix" that with a simple patch
[03:57] <bkc_> 1finger = hover, 2fingers = click/drag, 3finger=scroll, pinch=zoom
[03:57] <bkc_> and then the 4finger-smash for scroll-click :P
[03:58] <bkc_> the force of the press can already be measured by most touchscreens :)
[03:58] <bkc_> there are lots of apps that make use of this
[03:58] <doomlord> which OS's / devices can read that
[03:58] <doomlord> is it force or contact area
[03:59] <bkc_> IIRC force, but it might be contact-area too
[04:00] <doomlord> would be nice if multitouch could resize windows :)
[04:01] <doomlord> 3 finger drag but also 3finger pinch :)
[04:01] <doomlord> then you could get rid of the titlebars
[04:01] <doomlord> and a lot of the window decoration
[04:02] <doomlord> globalmenu should be permanently visible too
[04:02] <bkc_> that's a nice idea :)
[04:03] <doomlord> and 4 fingers for expo/scale (swipes etc)
[04:03] <bkc_> :P
[04:03] <bkc_> well, the 4finger app-switch would be awesome :)
[04:04] <doomlord> expo would be perfect on a touchscreen, i'm surprised the others dont already do it
[04:05] <bkc_> there's a hack for iPhone to do that ;)
[04:05] <doomlord> zoom out to view 2x2 grid.. and scroll in that view for 2x3,2x4.. as you add more open screens
[04:05] <doomlord> ok not seen it
[04:05] <doomlord> the best desktop was Mac OSX snow leapoard with expose+spaces and multitouch all working really well..
[04:06] <doomlord> there would be the potential for ubuntu on a tablet to exceed that
[04:06] <doomlord> if people start tweaking it like that
[04:06] <bkc_> indeed
[04:06] <bkc_> http://gizmodo.com/5619612/how-to-get-expose+style-multitasking-on-your-iphone-or-ipad
[04:09] <doomlord> can i be arsed going back to my android source now heh
[04:13] <doomlord> heh just need ubuntu table now
[04:15] <bkc_> you mean like M$ Surface?
[04:15] <doomlord> yes :)
[04:17] <bkc_> can't you install ubuntu on a Surface them? :/
[04:17] <bkc_> then*
[04:18] <doomlord> i guess you can
[04:20] <bkc_> then doet! :D
[07:32] <dholbach> good morning
[07:33] <codealot> morning to you dholbach
[07:34] <dholbach> hi codealot
[07:37] <codealot> dholbach: what part of the project are you working on
[07:39] <dholbach> codealot, I work with the ubuntu development community in general
[07:53] <codealot> dholbach, cool. I'm on the terminal team
[07:54] <dholbach> excellent :-D
[07:57] <xsacha> codealot: are you taking inspiration from the n9 terminal?
[07:58] <codealot> haven't had a close look at it
[07:58] <codealot> let me check it out
[07:59] <codealot> xsacha: thanks for the hint
[08:49] <dpm> good morning all!
[08:50] <dpm> any core apps developers around?
[09:13] <codealot> dpm: I'm around
[09:29] <dpm> hi codealot
[09:30] <dpm> we're setting the CI infrastructure and wanted to talk to someone from the teams to test it first on a particular app project
[09:31] <dpm> but it seems the setup is pretty straightforward, so we'll enable it for all apps at once
[09:31] <dpm> I'll post an update to the list with an overview and the new workflow later on today
[09:32] <codealot> ok
[13:00] <void__> test
[13:00] <void__> hello
[13:40] <Darkwing> a couple of questions with the phone image. Will there be more than just the GSM Galaxy Nexus image and will the source be released?
[13:41] <smartboyhw> Darkwing, There will be a Nexus 4 image and there will be source code so you can port
[13:42] <Darkwing> I know about he Nexus 4... So, is it not being released for the Galaxy Nexus as well?
[13:43] <Darkwing> I've been doing Android ROM development for a while now... I figured that the porting I have done there would come in handy to get the CDMA/4GLTE GNex up and running at some point.
[13:44] <smartboyhw> Darkwing, as well
[13:45] <wastrel> both gnex and nex4
[13:45] <Darkwing> :D I'm one os those users who is on Verizon Wirelesss in the US. So, I'm stuck with CDMA for a few more months... I'll be changing soon but, I know a TON of people in the Android community that are looking forward to this... The number of emails I'm getting is stunning.
[13:45] <wastrel> but not <random every other phone people ask about>
[13:46] <Darkwing> wastrel: gnex maguro only or, will there be images for toro and toro plus?
[13:48] <wastrel> gsm only i heard
[13:48] <wastrel> but i am a bystander not affiliated etc etc
[13:48] <Darkwing> Yeah I know... :/
[13:49] <wastrel> basically all i know comes from reading what people type in this channel
[13:49] <Darkwing> Okay.
[13:49] <Darkwing> Well, I guess tomorrow will be filled with code hacking to get toro and toro plus included.
[13:49] <wastrel> speaking of which i have yet to watch the tablet intro video
[13:49] <Darkwing> Its a good video.
[13:50] <wastrel> i was v. busy yesterday
[13:51] <wastrel> my new earbuds are much louder than the ones that came with my gnex
[13:51] <Darkwing> I'm just waiting for my Tax return and I'm picking up a nexus 4.
[13:51] <wastrel> i certainly hope it's easy to change the default colors :]
[13:53] <wastrel> sitestage is cool
[13:53] <wastrel> hopefully can flip it to the left for left-handers
[14:01] <wastrel> it's a cute video
[14:01] <Denommus> hi
[14:02] <Denommus> I'm trying to use the Ubuntu SDK, but it gives me the error 'module "QmlProject" is not installed'
[14:02] <Denommus> what does this mean?
[14:21] <nOStahl> tomorrow; everyone excited?
[14:22] <Darkwing> a bit
[14:26] <codealot> wish I had a nexus :(
[14:26] <codealot> but hey lets see how tomorrow goes
[14:27] <nOStahl> any word on what carriers are supported?
[14:28] <darthmuffins> carrier support is not related to the OS...
[14:28] <darthmuffins> if you run it on a VZ Galaxy Nexus... it will be VZ
[14:29] <nOStahl> ah I'd imagine they have to have kernel support for gsm vs cdma hardware
[14:29] <darthmuffins> yeah, but the android kernel has support for both, and I'd assume the modules aren't that hard to get to...
[14:29] <darthmuffins> idk for sure, but it makes sense
[14:29] <nOStahl> aye
[14:31] <nOStahl> I wonder if it will be centralized knowledge base for running it on different various hardware
[14:31] <nOStahl> or if things will get split off to separate websites dedicated to a certain phone hardware
[14:32] <darthmuffins> idk, but it is a community effort, we can make it happen if we want a centralized location
[14:33] <codealot> Denommus did you install qt5 as instructed on the ubuntu page?
[14:34] <Darkwing> Actually... It's more than just kerney support for radios. At least in the Android world it is.
[14:34] <Darkwing> *Kernel
[14:35] <Darkwing> I'm assuming that Verizon will not be support out of the box because GSm is more widespread. But, as a Verizon person, I'll be instantly working on porting it as I have this week off from uni
[14:35] <ajalkane> bzoltan: about yesterday's talk about C++ plugins for QML...
[14:36] <Denommus> codealot: yes
[14:37] <codealot> Denommus: what ubuntu version are you on?
[14:37] <Denommus> I'm not really on Ubuntu. I'm on Arch
[14:37] <Denommus> I installed qt5 and the sdk through AUR
[14:39] <Denommus> so it's a problem with my qt5 installation? I'll check the #archlinux channel, then
[14:39] <codealot> Denommus: just a sec I try figure out something
[14:40] <codealot> Denommus: I'm not good at Arch but I believe it just a matter of the path exports
[14:40] <Denommus> I exported QT_INSTALL_BINS="/usr/lib/qt5/bin"
[14:41] <Denommus> and put it on PATH
[14:42] <codealot> and you get the error from QtCreator?
[14:44] <Denommus> are there any other environment variables that I should be aware of?
[14:51] <Denommus> my connection dropped
[14:51] <Denommus> anyone answered my questions?
[14:51] <smartboyhw> Denommus, no:P
[14:52] <Denommus> ok
[14:53] <dlan^> is that possible to repack ubuntu-mobile stack for other distribution, say fedora/debian?
[14:56] <codealot> Denommus: trying to check the environment variables and see if I have an answer for you
[14:56] <Andy80> hi
[14:58] <Denommus> ... the error solved itself
[14:58] <Denommus> no, wait
[14:59] <Denommus> it didn't
[15:00] <codealot> :) :(
[15:01] <Andy80> bzoltan, I still can't compile QtCreator, I keep getting this error: Project ERROR: Unknown module(s) in QT: declarative - I've installed any *declarative* package I've found available.
[15:02] <bzoltan> Andy80:  What qtcreator do you try to build?
[15:03] <Andy80> bzoltan, latest available sources from gitorious (I' git pulled yesterday, but I can git pull again right now...)
[15:03] <bzoltan> Andy80:  is it the 2.7 branch?
[15:03] <Andy80> it's the "master" branch I think
[15:03] <ajalkane> bzoltan: about yesterday's talk about C++ plugins for QML... any new development about it?
[15:04] <Andy80> yes, I'm in the "master"
[15:04] <Denommus> codealot: do you know how do I install new modules?
[15:04] <bzoltan> ajalkane:  geez :) I did not have time to poopoo today...
[15:05] <ajalkane> lol... if poopoing is all that'd be needed, I'd have 10 plugins already today
[15:06] <bzoltan> Andy80:  is th amaster the 2.7
[15:07] <Andy80> bzoltan, I've created a qtcreator-build subfolder, following the instructions, I enter that folder and I execute "qmake -r ../" and after few lines of message I get that error...
[15:09] <codealot_> Denommus: I'd recommend you compile from source
[15:09] <bzoltan> Andy80: I do not know... for some time I only build the one in the qt5-beta-proper
[15:10] <Denommus> codealot: AUR compiles from source already. I'll check #archlinux for help
[15:11] <Andy80> damn I need to fix this asap or I really can't test jp plugin :\ my previous env was working, but it was qt-creator 2.6.1 built with Qt 4.8.x. if it's the same I can use that one... but I remember you told me I had to use 2.7.x because of some QtQuick2 support that the plugin i using...
[15:11] <codealot> I know it compiles from source but I meant you do it the "…make…make install" way
[15:12] <codealot> so that you can set some variables yourself
[15:12] <codealot> and also point the install path so that its easier to add modules
[15:13] <codealot> either by just copying the modules folder into place
[15:13] <codealot> or "ln"
[15:21] <Denommus> codealot: funny thing: Ctrl+R works
[15:22] <Denommus> codealot: I think I understood how this works. Thank you for your help and time
[15:23] <codealot> Denommus: you're welcome
[15:23] <codealot> Denommus maybe you can publish that on some wiki for other Arch users to checkout
[15:26] <Denommus> codealot: what I understood is that when you use qmlscene, it expects to run a qml file, not a qmlproject file. But Ctrl+R parses the qmlproject correctly, which opens the mainFile
[15:31] <codealot> ok
[15:31] <codealot> great
[16:30] <DamianGalletini> Hi
[17:09] <doomlord> willl ubuntu phone run with mhl cabe, or will you need a dock with extra usb ports
[17:09] <doomlord> mhl cable^
[17:30] <acematrix> Cannot wait till tomorrow
[17:31] <acematrix> My poor Kindle Fire and HTC Explorer have no chance of Ubuntu running...
[17:32] <ajalkane> I am stuck with plugins. I'm trying to use my compiled plugin with "qmlscene -I path/to/compiled/plugin myqml.qml" but I get "module "blabla" is not installed". Do I understand the -I option to qmlscene correctly, or should I install the qml plugin into the system wide search path?
[17:34] <frankencode> ajalkane: there are environment variables to make the declarative engine output debug messages on what it is doing
[17:34] <frankencode> i have to google it...
[17:36] <frankencode> http://www.developer.nokia.com/Community/Wiki/How_to_enable_QML_Import_Traces
[17:36] <frankencode> i'm not sure if it is still valid for qt5
[17:38] <Corden> hello guys... just a quick Q.
[17:39] <Corden> can we use python+gtk on ubuntu phone?
[17:39] <KevinWright> hello are the Facebook client app developers in the channel? Sorry for being late...bad internet connection
[17:39] <ajalkane> frankencode: I've tried QML_IMPORT_TRACE=1 but it did not shed any light to the issue
[17:39] <ajalkane> also strace did not reveal anything to me
[17:40] <barbarrica> Kevin: Hi, I'm on the Facebook team
[17:40] <KevinWright> barbarrica: Hello!
[17:41] <KevinWright> barbarrica: Let's see if anyone else from the team is here...or we can have a quick chat on our own
[17:43] <KevinWright> barbarrica: maybe it is just the two of us
[17:43] <KevinWright> barbarrica: let's have a quick chat to get started.
[17:44] <KevinWright> barbarrica: thanks for joining today
[17:44] <barbarrica> Kevin: Thank you
[17:44] <KevinWright> barbarrica: I'm looking forward to working together on this project
[17:44] <KevinWright> barbarrica: did you have a chance to install qt5 and the ubuntu components?
[17:45] <barbarrica> kevin:yes, I've had some problems becausei tried it on 12.04, but I got it working now
[17:45] <KevinWright> barbarrica: great. glad you finally were able to get things working
[17:46] <barbarrica> kevin: QtCreator 2.6.1 is also working
[17:46] <KevinWright> barbarrica: OK great. I sent a bunch of emails over the past few days Hope it wasn't too much alll at once.
[17:46] <KevinWright> barbarrica: Did you have a chance to read through most of the info?
[17:47] <barbarrica> kevin: I've seen the initial blueprint and I proposed myself to begin working in the auth functionality
[17:48] <KevinWright> barbarrica: Great! Thanks for that
[17:48] <KevinWright> barbarrica: Are there any questions I can help to answer at this time?
[17:48] <barbarrica> Kevin: my idea is to use a WebView to do the oauth
[17:49] <KevinWright> barbarrica: Would that mean the rest of the application would need to be in a WebView?
[17:50] <KevinWright> barbarrica: btw, I might have problems with my internet connection during this discussion, so if I am unresponsive at some point you'll know why
[17:51] <barbarrica> kevin: no, only the authentication page will, after the user authenticates we can save the auth token for subsquent access
[17:51] <KevinWright> barbarrica: ok cool
[17:51] <barbarrica> kevin: i guess the Tweeter team will have the same issue
[17:51] <KevinWright> barbarrica: it sounds like that won't take long to implement. is that correct?
[17:52] <KevinWright> barbarrica: yes probably
[17:52] <barbarrica> kevin: Yes, it's a simple thing...
[17:52] <KevinWright> barbarrica: OK great
[17:53] <KevinWright> barbarrica: So at this time is there anything I can do to help you out? Or any questions you need answered?
[17:54] <KevinWright> barbarrica: The developer guide might be of some assistance, but I am always available by email and of course here on IRC
[17:54] <KevinWright> barbarrica: (this week I am not on IRC as much as usual though -- next week I will be around more often)
[17:54] <barbarrica> kevin: I'm new to launchpad, and I'm trying to get around in it
[17:54] <barbarrica> kevin: how do the code commits work ?
[17:55] <KevinWright> barbarrica: mhall119 can also provide you some help
[17:55] <KevinWright> barbarrica: the developer guide has some information about that
[17:55] <KevinWright> barbarrica: do you have the link?
[17:55] <barbarrica> kevin: no
[17:55] <KevinWright> barbarrica: one moment
[17:56] <KevinWright> barbarrica: https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[17:56] <barbarrica> kevin: thanks I'll look into that
[17:57] <ajalkane> Anyone know where is UbuntuComponents plugin source code?
[17:57] <mhall119> hey KevinWright, is there a meeting going on?
[17:57] <frals> ajalkane: https://launchpad.net/ubuntu-ui-toolkit, i think
[17:57] <KevinWright> mhall119: A two person meeting
[17:58] <frals> getting 503 when trying to browse it though, not tried bzr checkout
[17:58] <ajalkane> same for me
[17:58] <frals> ah, now the browse works
[17:58] <KevinWright> mhall119: meet barbarrica grom the Facebook team
[17:58] <frankencode> ajalkane: yes, bzr branch lp:ubuntu-ui.toolkit
[17:58] <mhall119> hi barbarrica
[17:58] <ajalkane> alright cool
[17:58] <KevinWright> grom == from
[17:58] <mhall119> KevinWright: is it too late to start the meeting bot?
[17:58] <barbarrica> kevin: Are there any testing guidelines available ? I've some people talking about an automated test tool...
[17:59] <KevinWright> mhall119: probably not necessary at this time ... did not know you needed to do that sorry
[17:59] <KevinWright> barbarrica: let me dig something up for you and send by email
[18:00] <KevinWright> barbarrica: I know we started about 5+ minutes late for the talk, but I think I might get cutoff in a moment
[18:00] <mhall119> KevinWright: anybody can use it, it's nice because it produces the well formated minutes that I put on the wiki for the RSS Reader yesterday
[18:00] <KevinWright> barbarrica: before I do is there any final question I can answer? mhall119 can also help you too
[18:01] <KevinWright> mhall119: cool
[18:01] <KevinWright> mhall119: can you send me some details about that by email?
[18:01] <mhall119> KevinWright: https://wiki.ubuntu.com/meetingology has everything you need
[18:02] <KevinWright> mhall119: thanks for that
[18:02] <barbarrica> kevin: I've also looked at some of the wireframes, and they are starting to look good
[18:03] <KevinWright> Good. I didn't get a chance to look at them in great detail yet myself, but I will be doing so during the coming days.
[18:03] <KevinWright> barbarrica: Sorry to have to go now. Thans
[18:03] <wastrel> what wireframes ?
[18:03] <KevinWright> barbarrica: Thanks for joining today
[18:03] <KevinWright> barbarrica: I'm looking forward to working together
[18:03] <barbarrica> kevin: ok, see you soon.
[18:04] <KevinWright> barbarrica: Talk to you soon
[18:05] <mhall119> barbarrica: FYI, I've just heard that there is a QML plugin coming soon to access Ubuntu Online Accounts credentials, so the facebook app can request an auth token from that instead of having to implement an oauth step itself
[18:08] <fmunozs> hello
[18:08] <barbarrica> mhall119: That will be great ! I was thinking about a central auth service like that, should be available
[18:08] <fmunozs> did the twitter meeting begin already? :)
[18:09] <mhall119> barbarrica: it already exists on the desktop, it just needed to be exposed to QML
[18:11] <wastrel> fmunozs: assuming the meeting that just happened was the twitter meeting, it is already over
[18:12] <fmunozs> :C
[18:12] <wastrel> tho it seems like it may have been the facebook meeting i'm only paying half attention
[18:12] <wastrel> (or less)
[18:13] <barbarrica> mhall119: thanks, I'll search for it
[18:17] <mhall119> barbarrica: it's not available yet, package is being build now, it should get published later today
[18:25] <KevinWright> mhall119: ping
[18:25] <mhall119> KevinWright: pong
[18:26] <KevinWright> mhall119: There is another meeting for Twitter client in about 5 min.
[18:26] <KevinWright> mhall119: I didn't have a chance to read about the meeting bot
[18:26] <KevinWright> mhall119: Do you have a 2 minute crash course?
[18:27] <mhall119> KevinWright: I can just run the bot for you this session and you can watch
[18:27] <KevinWright> mhall119: OK
[18:27] <mhall119> let me know when to start
[18:28] <KevinWright> mhall119: OK I will (it will be in about 2 to 3 minutes)
[18:28] <fmunozs> KevinWright, hello! I'm here for the Twitter meeting too
[18:29] <KevinWright> fmonozs: Hello!
[18:29] <KevinWright> Anyone else here from the Twitter client app dev team?
[18:30] <KevinWright> sorry, fmonozs == fmunozs
[18:31] <fmunozs> :) I think jaakko_kui is from the Twitter team too
[18:31] <jaakko_kui> Hi all!
[18:34] <KevinWright> jaakko_kui, fmunozs: Hello thanks for joining the talk for the Twitter client
[18:34] <KevinWright> jaakko_kui, fmunozs: Sorry I got cutoff for a second there. Hello thanks for joining the talk for the Twitter client
[18:34] <KevinWright> Anyone else here for thee Twitter client app development team?
[18:35] <KevinWright> jaakko_kui, fmunozs: Shall we get started?
[18:35] <jaakko_kui> Ok
[18:35] <KevinWright> jaakko_kui, fmunozs: Great!
[18:35] <KevinWright> jaakko_kui, fmunozs: Did you both get a chance to install Qt5 and the Ubuntu components?
[18:35] <KevinWright> Sorry mhall119 we started
[18:36] <jaakko_kui> Yes, I have played little bit-
[18:36] <KevinWright> jaakko_kui: Good stuff
[18:36] <KevinWright> jaakko_kui, fmunozs: I also sent a bunch of emails the past few days. Hope it wasn't too much all at once.
[18:37] <KevinWright> jaakko_kui, fmunozs: In there were some details about some rough work items I put into blueprints
[18:37] <jaakko_kui> it's good to get info :)
[18:37] <KevinWright> jaakko_kui, fmunozs: Did you have a chance to see those?
[18:37] <mhall119> #startmeeting Twitter app
[18:37] <meetingology> Meeting started Wed Feb 20 18:37:38 2013 UTC.  The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:37] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:37] <jaakko_kui> I have read them once
[18:37] <mhall119> #topic progress review
[18:38] <KevinWright> mhall119: thanks
[18:38] <mhall119> #link https://wiki.ubuntu.com/Touch/CoreApps/Twitter
[18:38] <KevinWright> jaakko_kui, fmunozs: If there are any questions about any of the info please don't hesitate to ask myself or mhall119
[18:38] <mhall119> #link https://blueprints.launchpad.net/ubuntu-twitter-app/+spec/initial-twitter-development
[18:38] <KevinWright> jaakko_kui, fmunozs: mhall119 is pasting some of the links now
[18:39] <fmunozs> thanks
[18:39] <jaakko_kui> ok
[18:39] <mhall119> those are links wo the wiki spec page and the blueprint
[18:39] <mhall119> the work items for the initial development are listed at the bottom of the Blueprint
[18:39] <KevinWright> jaakko_kui, fmunozs: Are there any questions you had on your mind we can help answer?
[18:39] <KevinWright> jaakko_kui, fmunozs: We can discuss the project specifics in a moment
[18:40] <mhall119> has everybody been able to install the SDK and grab a copy of the app's branch?
[18:40] <mhall119> and get that running
[18:40] <fmunozs> yes, Qt5 and SDK running on Ubuntu 12.10
[18:41] <jaakko_kui> i have sdk, but not apps branch yet
[18:41] <mhall119> and did you bzr branch lp:ubuntu-twitter-app?
[18:41] <mhall119> jaakko_kui: ^^ do that
[18:41] <jaakko_kui> ok
[18:41] <KevinWright> mhall119: Maybe you can answer a question for me actually
[18:41] <mhall119> then you can either run it from QtCreator, or just run "qmlscene twitter.qml" from inside the directory
[18:42] <jaakko_kui> ok
[18:42] <mhall119> KevinWright: sure?
[18:42] <KevinWright> mhall119: Did someone already do some work towards a Twitter client?
[18:43] <KevinWright> mhall119: I thought someone mentioned it to me before.
[18:43] <mhall119> there was a twitter app written in Qt4, gatox and mandel wrote it before the SDK was released
[18:43] <mhall119> I think they're on the team for this version too
[18:43] <KevinWright> mhall119: OK so it may or may not be useful for us here
[18:44] <mhall119> I'm sure some of it will be useful
[18:44] <KevinWright> mhall119: OK cool
[18:44] <mhall119> how much, I can't say
[18:44] <KevinWright> mhall119: OK, we can check on it later
[18:44] <KevinWright> mhall119: Thanks
[18:44] <mhall119> any other progress updates?
[18:44] <KevinWright> jaakko_kui, fmunozs: Did you have a chance to look at the work items that were proposed?
[18:45] <mhall119> #topic Work Items
[18:45] <KevinWright> mhall119: thanks again
[18:45] <mhall119> :)
[18:45] <jaakko_kui> yes
[18:45] <mhall119> there are 13 work items currently on https://blueprints.launchpad.net/ubuntu-twitter-app/+spec/initial-twitter-development
[18:45] <KevinWright> fmunozs: Did you have a chance to see them?
[18:45] <fmunozs> KevinWright, you mean the functional requirements?
[18:46] <mhall119> we need to get those assigned to members of the team
[18:46] <fmunozs> I see them now
[18:46] <KevinWright> fmunozs:  mhall119 pasted a link to the work items, but they are from the functional requirements
[18:46] <KevinWright> jaakko_kui, fmunozs: Take a look and volunteer yourself for something that sounds interesting to you
[18:47] <jaakko_kui> I can do test related tasks
[18:47] <KevinWright> jaakko_kui, fmunozs: at the start of the line in the blueprint put your Launchpad ID in [] brackets
[18:47] <KevinWright> jaakko_kui: Cool. Testing is very important
[18:48] <KevinWright> So the format will be [you-lp-id] This is a work item: TODO
[18:48] <jaakko_kui> ok
[18:48] <fmunozs> yea, just noticed pretty much the same, I don't see anything about sharing stuff from other applications, I saw in the tablet announcement there will be a sharing framework, right? somebody else will take care of that?
[18:48] <KevinWright> fmunozs: Anything there look interesting?
[18:48] <mhall119> #action jaakko_kui to self-assign work items
[18:48] <meetingology> ACTION: jaakko_kui to self-assign work items
[18:48] <mhall119> #action fmunozs to self-assign work items
[18:48] <meetingology> ACTION: fmunozs to self-assign work items
[18:48] <mhall119> who can email the rest of the team and ask them to each take 2 work items?
[18:49] <KevinWright> mhall119: I can do that. I already sent one or two about this topic.
[18:49] <mhall119> #action KevinWright Email the ubuntu-twitter-dev team, ask each member to assign themselves to 2 work items
[18:49] <meetingology> ACTION: KevinWright Email the ubuntu-twitter-dev team, ask each member to assign themselves to 2 work items
[18:49] <KevinWright> jaakko_kui, fmunozs: Also don't be shy about suggesting new work items
[18:49] <jaakko_kui> ok
[18:49] <KevinWright> jaakko_kui, fmunozs: Or modifying the wording, expanding details etc.
[18:49] <mhall119> yeah, these aren't set in stone, we can add/remove and reassign as needed
[18:50] <mhall119> they are just there to keep things on track
[18:50] <KevinWright> jaakko_kui, fmunozs: Some of what I put in there was done quite quickly and might not read like a proper work item
[18:50] <fmunozs> ok I will see the items and select one today
[18:50] <KevinWright> jaakko_kui, fmunozs: I'll fix them up, but we need some additional detail in many cases
[18:50] <KevinWright> fmunozs: great!
[18:50] <jaakko_kui> any guide etc for the test documents ?
[18:51] <KevinWright> jaakko_kui: Let me send an email about testing
[18:51] <mhall119> # Testing
[18:51] <jaakko_kui> great
[18:51] <KevinWright> jaakko_kui, fmunozs: Testing is an important topic that everyone should know about
[18:51] <mhall119> #topic Testing
[18:51] <mhall119> #action KevinWright send email to ubuntu-twitter-dev providing information on testing
[18:51] <meetingology> ACTION: KevinWright send email to ubuntu-twitter-dev providing information on testing
[18:51] <KevinWright> One more time for the meeting bot :) Testing is an important topic that everyone should know about
[18:52] <KevinWright> jaakko_kui, fmunozs: I would like to send something to all the app devs on all teams about this
[18:52] <jaakko_kui> ok
[18:52] <KevinWright> jaakko_kui, fmunozs: OK we have just a few minutes left
[18:52] <KevinWright> jaakko_kui, fmunozs: Any final questions for today?
[18:53] <jaakko_kui> nope :)
[18:53] <mhall119> #topic other Q&A
[18:53] <fmunozs> no, I'm ok
[18:53] <KevinWright> jaakko_kui, fmunozs: I'm available any time by email of course, or IRC (this week I am not on very often, but next week back on a regular schedule)
[18:53] <KevinWright> jaakko_kui, fmunozs: Alright great!
[18:53] <KevinWright> jaakko_kui, fmunozs: Thanks for joining today
[18:53] <jaakko_kui> ok bye!
[18:53] <KevinWright> jaakko_kui, fmunozs: I'm looking forward to working with you both!
[18:53] <KevinWright> jaakko_kui, fmunozs: Cheers!
[18:53] <mhall119> I'm also available if you guys have any questions about using bzr or Launchpad
[18:53] <KevinWright> jaakko_kui, fmunozs: Yes mhall119 is also there for you
[18:54] <jaakko_kui> good!
[18:54] <fmunozs> Thanks
[18:54] <KevinWright> (sorry mhall119, forgot to add that in!)
[18:54] <KevinWright> jaakko_kui, fmunozs: Bye all!
[18:54] <jaakko_kui> bye
[18:54] <KevinWright> Thanks mhall119 for the meeting help
[18:54] <mhall119> alright, thanks everyone
[18:55] <mhall119> #endmeeting
[18:55] <meetingology> Meeting ended Wed Feb 20 18:55:07 2013 UTC.
[18:55] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-phone/2013/ubuntu-phone.2013-02-20-18.37.moin.txt
[18:55] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-phone/2013/ubuntu-phone.2013-02-20-18.37.html
[18:55] <mhall119> KevinWright: now I'm just going to copy/paste the text from the moin.txt link above into the wiki page for Twitter/Meetings
[18:55] <wastrel> fmunozs: sorry i lied about the twitter meeting
[18:56] <fmunozs> wastrel, hehe
[19:28] <darthmuffins> possibly a stupid question: I'm interesting in joining the development team for one of the core apps, is it open to whomever?
[19:32] <KevinWright> Hey, hey are there any devs from the YouTube client team here?
[19:33] <KevinWright> mhall119 ... another mtg. might be underway shortly
[19:34] <mhall119> KevinWright: want to try running the bot?
[19:34] <liio> KevinWright: Josip here
[19:34] <KevinWright> mhall119: I would except I can't scroll up atm to see what you did before
[19:34] <KevinWright> liio: Hello!
[19:35] <KevinWright> liio: Let's wait just a moment to see if others join us
[19:35] <mhall119> KevinWright: start with: #startmeeting <meeting title>
[19:35] <darthmuffins> can anyone join the development teams?
[19:35] <mhall119> change topics with #topic <topic>
[19:36] <KevinWright> mhall119: OK thanks
[19:36] <mhall119> and if you want to record an action item: #action <nick> <what to do>
[19:36] <KevinWright> mhall119: And to wrap up?
[19:36] <mhall119> just #endmeeting
[19:36] <KevinWright> mhall119: cool thanks
[19:37] <KevinWright> OK liio let's start...I guess it is just us
[19:37] <KevinWright> #startmeeting YouTube Client Meeting
[19:37] <meetingology> Meeting started Wed Feb 20 19:37:08 2013 UTC.  The chair is KevinWright. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:37] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:37] <liio> KevinWright: okay
[19:37] <KevinWright> #topic housekeeping
[19:37] <KevinWright> liio: Did you get a chance to install qt5 and the ubuntu components?
[19:38] <liio> KevinWright: I had it installed before the final release but haven't updated it since, to be honest, I guess I'll have to do it today or tomorrow
[19:39] <liio> but everything was working, I don't think it's going to be a problem
[19:39] <KevinWright> liio: OK please do, and if you run into any trouble and need help with something this channel is a great place to ask
[19:39] <liio> KevinWright: sure, I'll do that.
[19:39] <KevinWright> liio: I sent some emails out the past few days, in particular a few about work itesm. Did you have a chance to see those?
[19:40] <KevinWright> itesm == items
[19:41] <liio> KevinWright: Sure, I did, and I had a peek or two at the links you sent. I was hoping we'll discuss how to split work items and whose gonna do what, but I guess that's not smart thing to do since others aren't here?
[19:42] <KevinWright> liio: Great. Well if there is something there that you think you would like to take care of please go ahead and put your name next to it.
[19:42] <KevinWright> liio: The format again is [your-launchpad-id] This is a work item: TODO
[19:43] <liio> KevinWright: No need to coordinate with others?
[19:43] <KevinWright> liio: We can work with the other team members to sort out the other work items
[19:43] <mhall119> KevinWright: might want to #topic Work Items
[19:43] <KevinWright> liio: But of course we want to make sure to coordinate as much as possible
[19:43] <KevinWright> #topic Work Items
[19:44] <liio> KevinWright: okay then, I'd just like to get the whole idea how the app is going to work and what's needed beforehand
[19:44] <KevinWright> for the meeting bot ... discussing work items and coordinating amongst team members
[19:44] <liio> KevinWright: oh, a question, are there any deadlines we have?
[19:44] <KevinWright> liio: OK so would it help if I drew up a summary?
[19:44] <KevinWright> #topic Milestones
[19:44] <liio> KevinWright: Sure, that would be of great hel
[19:44] <liio> help*
[19:45] <KevinWright> liio: OK some milestones do need to be established. I will create a more explicit summary of a suggested definition for each milestone and the work items that go with it
[19:45] <KevinWright> #action KevinWright Create more explicit details of milestones, project summary and work items for milestones
[19:45] <meetingology> ACTION: KevinWright Create more explicit details of milestones, project summary and work items for milestones
[19:46] <liio> KevinWright: Cool, thanks
[19:46] <KevinWright> liio: Other than that are there other questions you had on your mind that I can help answer?
[19:47] <KevinWright> liio: Any questions about the development environment, way of working etc.?
[19:47] <KevinWright> #topic: Any other questions
[19:47] <liio> KevinWright: Just one more :) Regarding yesterdays tablet announcement, is the app we're working on supposed to have a dedicated(?) tablet interface or that's a out-of-this-project task?
[19:48] <KevinWright> liio: That's out of the scope of this project at them moment, but certainly something to consider or discuss at a later date
[19:49] <liio> KevinWright: Okay, thanks. I think that's it from the questions I had for now.
[19:49] <KevinWright> liio: OK cool
[19:49] <liio> oh, one more, can we start working on the app or we're still waiting for something?
[19:50] <KevinWright> liio: You can start right away!
[19:50] <KevinWright> liio: Nothing stopping us at all
[19:50] <KevinWright> liio: Full steam ahead :)
[19:50] <rob_w> let there be twitter
[19:51] <KevinWright> liio: I'm available to answer questions anytime by email or irc ... this week I might not be around as much on irc or as responsive by email
[19:51] <KevinWright> liio: but next week I'll be back on a regular schedule
[19:51] <KevinWright> liio: and mhall119 is around to support you as well
[19:51] <mhall119> yup
[19:52] <liio> KevinWright: Wonderful! :) Thanks for the help, and sure, I hope I'll have the need to bug you guys with emails
[19:52] <KevinWright> liio: I'm looking forward to working together on this project
[19:52] <liio> KevinWright: Same here :)
[19:52] <KevinWright> liio: Thanks for joining today. Talk with you soon!
[19:53] <liio> KevinWright: No probs, hopefully the whole team is going to chime in next time :)
[19:53] <KevinWright> liio: Cheers, and have a great evening!
[19:53] <KevinWright> #endmeeting
[19:53] <meetingology> Meeting ended Wed Feb 20 19:53:30 2013 UTC.
[19:53] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-phone/2013/ubuntu-phone.2013-02-20-19.37.moin.txt
[19:53] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-phone/2013/ubuntu-phone.2013-02-20-19.37.html
[19:53] <liio> KevinWright: Cheers
[19:53] <mhall119> KevinWright: I already setup a meeting page for YouTube: https://wiki.ubuntu.com/Touch/CoreApps/YouTube/Meetings
[19:53] <mhall119> so just copy/paste the moin.txt text to the bottom of that
[19:54] <rob_w> ah its all KevinWright  ... lol
[19:55] <GuidoPallemans> mhall the current dev sdk is only a preview, what will the full sdk look like? a GUI editor? an IDE plugin? or just the same of what is online now, but complete?
[19:56] <mhall119> GuidoPallemans: IDE will be QtCreator with extra plugins
[19:56] <mhall119> to make it work better with Ubuntu and our devices
[19:56] <GuidoPallemans> brilliant, now I have something to look forward to :D
[19:56] <GuidoPallemans> oh
[19:57] <GuidoPallemans> is there anything new SDK-wise with the introduction of the tablet?
[19:57] <mhall119> GuidoPallemans: shouldn't be too long of a wait
[19:57] <GuidoPallemans> brilliant, thanks
[19:57] <mhall119> GuidoPallemans: I don't think so, not as far as API and Components go
[19:57] <GuidoPallemans> ok, thanks
[19:57] <GuidoPallemans> (I'll wait for the full sdk :D )
[19:57] <mhall119> we'll of course keep adding on Components as they are developed, but nothing specifically because of Tablet
[19:57] <GuidoPallemans> yup
[19:58] <mhall119> GuidoPallemans: play with what's available now, and keep you system up to date to get the latest as it lands
[19:58] <GuidoPallemans> btw, I have a proposal for a Component: a date/time picker, and I think I can make it myself, how would I add that?
[19:59] <mhall119> bzoltan: jppiiroi1en: ^^
[19:59] <mhall119> can you answer that for him?
[20:01] <darthmuffins> mhall119: how can we get involved developing the core apps? (specifically, i'm interested in assisting with the email client)
[20:03] <GuidoPallemans> darthmuffins: https://launchpad.net/~ubuntu-emailclient-dev
[20:03] <GreenChris> At what time will the developer preview get published?
[20:04] <GuidoPallemans> darthmuffins: it's closed, but you can mail the devs...
[20:04] <GuidoPallemans> GreenChris: jono has just said "in the afternoon European time"
[20:04] <GreenChris> :(
[20:04] <GreenChris> So late
[20:05] <GreenChris> I can't wait
[20:05] <darthmuffins> GuidoPallemans: I found that, I guess "closed" was the actual answer to my question lol. thank you
[20:05] <GuidoPallemans> but they're not entirely sure yet
[20:06] <bzoltan> GuidoPallemans:  the date and time picker components are on our lists.  I would not rush into implementation before we got the design guidelines.
[20:06] <GuidoPallemans> darthmuffins: if you have anything special to offer (like if you already made a mail client with js) you might get in with a mail
[20:06] <bzoltan> mhall119 ^
[20:06] <GreenChris> I will install it on my n7 and n4 as soon as they release the images
[20:08] <darthmuffins> GuidoPallemans: I don't, I was investigating possible QML components to add from the c++ side, but wanted to get a better idea of the current status and roadmap before jumping in with coding
[20:08] <GuidoPallemans> oh
[20:09] <darthmuffins> no worries, i'll wait for the src rel tomorrow
[20:09] <bzoltan> darthmuffins: keep in mind that _all_ our components are implemented in pure 100% QML
[20:11] <darthmuffins> bzoltan: as in, don't write additional QML classes unless absolutely needed?
[20:11] <wastrel> darthmuffins has promised to write me up a howto for getting the os up and running in a VM :]
[20:12] <darthmuffins> bzoltan: I was aware the entire UI was in QML, I was thinking along the lines of communications with servers, caching data, etc in c++, through a non-ui QML class
[20:12] <darthmuffins> wastrel: thats the first thing i'm doing with the release tomorrow, so you can have all my personal notes on how to do it :-)
[20:13] <GuidoPallemans> darthmuffins: there's also javascript
[20:13] <darthmuffins> GuidoPallemans: is that the best practice way of doing so?
[20:14] <GuidoPallemans> darthmuffins: I don't know, I haven't tried to couple c++ with qml yet. javascript is really easy in qml
[20:14] <GuidoPallemans> i made my reddit app completely without c++
[20:15] <darthmuffins> GuidoPallemans: yeah JS is easy in QML, but the Qt docs make it very clear how to interface C++ with QML, and there's a whole host of important operations that would benefit from the might and power of C++
[20:15] <darthmuffins> I was designing my current application with JS for gui related 'signals and slots' type stuff, with the 'workhorse' classes implemented in non-ui qml components
[20:16] <darthmuffins> ex: a game engine written in C++, exposed through a QML class, and user interactions handled through JS linking the ui qml classes to the game engine qml class
[20:16] <GuidoPallemans> if you need C++, use it, and you might, in the same go also port some of your javascript to C++
[20:16] <darthmuffins> seems a good combo of speed and easy use/debugging
[20:16] <GuidoPallemans> I really need to learn qml c++...
[20:16] <darthmuffins> yeah, i'll keep my eye on c++ vs js usage
[20:16] <codealot> anyone from the Terminal App here?
[20:17] <GuidoPallemans> I wonder if the core apps are going to be qml/js only
[20:17] <darthmuffins> I just feel that despite the fact that i'm sure js can handle speed requirements, c++ uses less proc to do so... => less battery usage
[20:17] <GuidoPallemans> yup
[20:17] <GuidoPallemans> I wonder if you have to compile your qmlfiles before installing
[20:17] <darthmuffins> and we all <3 long battery life
[20:18] <darthmuffins> you have to compile the C++ code into a lib for the QML project to use
[20:18] <darthmuffins> QML is interpreted though
[20:18] <darthmuffins> just like js
[20:18] <frankencode> battery live is no real issue
[20:18] <GuidoPallemans> if they could make qml's into binary's with c++ - like power that would be ideal
[20:18] <frankencode> the js expression are byte compiled at load time
[20:18] <darthmuffins> GuidoPallemans: not really possible unfortunately, dynamic languages are bad for that
[20:19] <frankencode> and when you hate js, you may still love qml/js
[20:19] <GuidoPallemans> for what, speed?
[20:19] <darthmuffins> GuidoPallemans: or at least, you need something like a jit
[20:19] <frankencode> because in qml there are types (like int) and you have way more checks at load time
[20:19] <frankencode> the animations run in hard-compiled code anyway
[20:20] <frankencode> the app logic is just-in-time compiled byte code...
[20:20] <frankencode> this is not p-code like you may be used from java
[20:21] <frankencode> p-code = pascal code, hee... when will the would stop reinventing the same shit (sorry I'm depressed!)
[20:21] <wastrel> GuidoPallemans: can you point me again to your source ?
[20:21] <GuidoPallemans> what source?
[20:22] <GuidoPallemans> reddit?
[20:22] <GuidoPallemans> https://github.com/brambram/UbuntuPhoneRedditApp
[20:22] <wastrel> ty
[20:22] <GuidoPallemans> but I'm not actively working on it
[20:22] <wastrel> ok
[20:23] <GuidoPallemans> don't have the time
[20:23] <GuidoPallemans> but I make notes on what I can do
[20:26] <darthmuffins> thanks for sharing though, alwasy good to look at other designs
[20:28] <mhall119> darthmuffins: you can get involved in writing code for the email client without being on the tema
[20:28] <mhall119> team
[20:29] <mhall119> darthmuffins: read the "For Developers" section of https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[20:29] <mhall119> that's all you need
[20:30] <darthmuffins> mhall119: in the future, i'll read the intro page before attacking the 'email client' link... thank you
[20:33] <belak> When the tablet version is released, will this be the place to ask questions?
[20:33] <k1l> !tablet | belak
[20:33] <belak> Thanks
[20:33] <wastrel> i watched the tablet video
[20:34] <wastrel> seems like phone apps run on tablet as phone apps in the little side thingy
[20:35] <k1l> yep
[20:47] <_inf> hey guys, I've got a question.
[20:47] <darthmuffins> i've got an answer
[20:47] <_inf> ok, perfect
[20:47] <wastrel> my answer is 7
[20:47] <darthmuffins> 42
[20:47] <darthmuffins> no wait, pi
[20:48] <wastrel> pi day is next month
[20:48] <wastrel> hm a pi day app
[20:48] <darthmuffins> and then star ways day is 2 months later
[20:48] <darthmuffins> star wars**
[20:52] <_inf> concerning the standard apps, how much real C++ is involved there? I would like to help but would prefer doing some real C++ with C++11 and boost, are the core apps closed to Qt or open to other libs?
[20:54] <darthmuffins> Qt replicates nearly everything boost provides, id say no to boost unless you can demonstrate a significant need of it
[20:54] <darthmuffins> (especially in light of C++ TR 2011)
[20:54] <darthmuffins> however, QML does interface with C++ easily, so you can write performance intensive components in a native language
[20:54] <darthmuffins> but all the gui stuff is QML/JS
[20:57] <darthmuffins> _inf: did that answer your question?
[21:03] <_inf> While qt might offer a lot of the functionality boost also offers, the style qt uses is somehow the anti-definition of modern c++. IMHO, writing clean modern code with Qt is just not possible and also much less fun. I personally don't have any experience with QML and no doubts that it is good for the UI parts. What are the plans yet for e.g. the networking stuff? (Random side note: C++11 is not a TR)
[21:04] <darthmuffins> _inf: you're right, sorry, it had been at TR status for so long i've gotten into a bad habbit calling it that
[21:04] <_inf> no prob, that's just terms.
[21:05] <darthmuffins> _inf: i'll have to somewhat disagree with you on Qt (though I do love boost from a previous life)
[21:05] <darthmuffins> it's not my favorite design or language patterns and paradigms, but in general, is relatively clean (granted: I don't use Qt containers unless i'm forced to)
[21:05] <darthmuffins> I generally use standards only features, and layer in qt when I have to play nice with other Qt stuff
[21:11] <_inf> maybe a naive question, but how far are those core apps yet? I mean those questions should be basic ones before starting anything. I was checking this stuff https://code.launchpad.net/~ubuntu-emailclient-dev/ubuntu-emailclient-app/trunk but found it to be rather empty.
[21:11] <ajalkane> They are not far.
[21:12] <darthmuffins> _inf: i experienced the same thing a few weeks ago. Idk if they have not been worked on much yet, or if more code will be released for them tomorrow, or what
[21:12] <ajalkane> Ask again in 2 months and you'll get better estimates
[21:12] <darthmuffins> I'm very keen on developing the email app...
[21:12] <darthmuffins> its pivotal for good acceptance of the mobile platform
[21:12] <darthmuffins> eg: good integration with calendar, tasks, contacts, etc
[21:15] <_inf> yeah, I am very keen on uphone in general as it is the first mobile OS which really appeals to me.
[21:16] <darthmuffins> ditto. I want to help make it succeeds as much as possible
[21:16] <darthmuffins> (read: as much as my full time job will allow me time-wise)
[21:18] <_inf> that's the spirit of opensource
[21:18] <darthmuffins> amen :)
[21:27] <comjf> what phones are supported for tomorrows sdk release?
[21:27] <comjf> I think I'll buy one on ebay
[21:28] <ajalkane> anyone built C++ plugins for QML in Ubuntu?
[21:29] <ajalkane> I've been banging my head against this problem for quite a while, where I have a finely compiling plugin but I can't get qmlscene to import it
[21:29] <darthmuffins> errors?
[21:30] <ajalkane> The only error is filemanager.qml:3 module "org.nemomobile.folderlistmodel" is not installed
[21:31] <ajalkane> So the plugin is not found. But I do give the folder as parameter to qmlscene (qmlscene -I path/to/folderlistmodel)
[21:32] <darthmuffins> its hard to know without seeing your computer, but:
[21:32] <darthmuffins> http://qt-project.org/doc/qt-4.8/declarative-tutorials-extending-chapter6-plugins.html
[21:32] <darthmuffins> gives some details on the process
[21:35] <papertigers> Does anyone know if you will interact with something like gstreamer directly or will it be a QT lib that you interact with
[21:40] <ajalkane> darthmuffins: you just linked me to Qt 4.8 docs :)
[22:03] <darthmuffins> ajalkane: ahhH!!!
[22:11] <ajalkane> Any Ubuntu SDK people around at this hour?
[22:42] <dank101> time to wait
[22:44] <dank101> waitt for the phone
[22:44] <k1l> someone said evening. so its some alot time to wait
[22:46] <dank101> time zone?
[22:46] <k1l> gmt i think
[22:46] <dank101> HA thats morning for me
[22:46] <k1l> yep
[22:47] <k1l> like in 20 hours or so
[22:47] <dank101> 5 pm for me
[22:47] <dank101> thats about the time i get to work
[22:47] <dank101> 12 pm
[22:48] <dank101> XD
[22:49] <robin-gloster> mhall119 are normal applications e.g. LibreOffice, GIMP available with the tablet UI on the nexus7? couldn't really tell from the video
[22:49] <mhall119> robin-gloster: I'm not entirely sure, but I am confident you'd hate trying to use them as they are on a touch-only interface
[22:49] <dank101> sort of
[22:50] <dank101> attach a blue tooth keyboard and mouse
[22:50] <dank101> then it's TOTAL ubuntu
[22:50] <robin-gloster> it isn't perfect but usable atm and can imagine it would work even better with HUD
[22:51] <doomlord> can it be used with bluetooth keyboard + touchscreen
[22:52] <dank101> Yeah
[22:52] <doomlord> (phone-screen = pointing device for desktop mode)
[22:52] <dank101> i like how they kept the very unity-like UI
[22:52] <dank101> i LOVE unity
[22:57] <dank101> people comming for the release?
[22:57] <dank101> *coming
[23:08] <mainerror> bzoltan: Any update on the Qt5 status on Raring?
[23:19] <dank101> ????
[23:19] <dank101> you already can run (most) of the Qt5 parts on Ubuntu
[23:20] <mainerror> I'm talking about a dependency issue within the Qt5 PPA used for the Ubuntu SDK.
[23:20] <dank101> oh...
[23:20] <fyksen> Hey! Does anybody know when the phone and tablet images will be released? :)
[23:20] <dank101> tomorrow
[23:20] <dank101> most likely 19 hours
[23:25] <dank101> Mainerror: manually download the debs
[23:27] <dank101> thats how i got it running on Quantal in early January
[23:28] <dank101> Before it was for Quantal
[23:30] <mainerror> dank101: Technically it would work already but there is a problem within the PPA. I'll just wait until that issue is resolved, it's not a critical problem for me to wait. ;)
[23:31] <dank101> mainerror: i was giving a HTTP method instead of debian's packaging system that should work on all debian based OS's
[23:31] <dank101> no matter what bug