[13:42] <Wilberto> At what time is the event?
[13:51] <bzoltan_> in an hour and ten minutes
[13:51] <bzoltan_> Wilberto ^
[14:54] <dpm> Coming up: Ubuntu SDK Roadmap
[15:02] <dpm> can everyone see us on http://summit.ubuntu.com/uds-1303/meeting/21630/appdev-1303-ubuntu-sdk-roadmap/ ?
[15:02] <ara> I can
[15:02] <alecu`> yup
[15:02] <netcurli> yes
[15:02] <rdxrb> yup
[15:02] <bjaanes> yes
[15:02] <fugue88> Yes.
[15:02] <bzoltan> hello all
[15:02] <bjaanes> heh, yes
[15:02] <olafura> yes
[15:02] <victorp_> hello
[15:02] <Mirv> now yes
[15:02] <theDoctor> hello
[15:02] <jdstrand> weird, no
[15:02] <jdstrand> but don't wait on me
[15:02] <ahayzen> o/
[15:02] <jdstrand> :)
[15:02] <Mirv> after refreshing
[15:02] <theDoctor> is there no video here?
[15:03] <eclecticgeekery> Sight and sound. All good.
[15:03] <Mirv> theDoctor: I have, http://summit.ubuntu.com/uds-1303/meeting/21630/appdev-1303-ubuntu-sdk-roadmap/
[15:03] <highvoltage> theDoctor: try refreshing
[15:03] <alecu`> mute zoltan!
[15:03] <Mirv> bzoltan: muuute when keyboarding :)
[15:03] <robru> click clack!
[15:03] <victorp_> yeap!
[15:03] <bjaanes> That keyboard is *really* loud
[15:03] <victorp_> we can hear you
[15:03] <rdxrb> Yes!
[15:03] <mzanetti> yes
[15:03] <zebaszp> we hear you perfectly! :D
[15:03] <ahayzen> we can hear u :)
[15:03] <zebaszp> also, yes, the keyboard is loud as hell
[15:03] <bjaanes> no
[15:03] <victorp_> nope
[15:03] <corden_> yes
[15:03] <mzanetti> no
[15:03] <Mirv> my sound is breaking up but maybe a small refresh again..
[15:04] <victorp_> bzoltan you have a mute on the hang out
[15:04] <victorp_> at the top
[15:04] <mzanetti> Mirv: I had that with the keynote. Seems much more stable watching directly on youtube for some reason
[15:04] <tiagoscd|uds> hey guys :)
[15:05] <Mirv> mzanetti: ok, keynote was fine, now even that route doesn't seem to help but fighting..
[15:05] <Mirv> mzanetti: oh, a BT problem it seems :)
[15:06] <dpm> if anyone wants to join the hangout and participate or ask questions directly there, please let me know and I can easily let you in
[15:06] <codealot> ok
[15:06] <Mirv> reconnecting to headset fixed
[15:06] <Riddell> bzoltan: yes
[15:07] <nerochiaro> is it possible to disable video ?
[15:07] <nerochiaro> in the hangout ?
[15:07] <Riddell> nerochiaro: doubt it
[15:08] <nerochiaro> Riddell: can't really follow, the audio is too choppy
[15:08] <codealot> I think its possible
[15:08] <codealot> did it once
[15:08] <nerochiaro> does it work for you guys ?
[15:08] <mzanetti> nerochiaro: yes, fine here
[15:08] <codealot> Its fine here
[15:08] <theDoctor_> It's working for me. Video breaks up occasionally
[15:08] <eclecticgeekery> All fine here, too.
[15:09] <Mirv> all great now after kicking my BT headset/connection
[15:09] <nerochiaro> ok, my connection is horrible again then. fantastic. i'll run to another location and catch the rest of the meeting from there, hopefully better quality
[15:10] <olafura> My problem is that QML feels really strange. I'm looking at the source to see if it's possible to rebase the qt declarative to work with Enyo syntax, it would allow for faster prototyping and better use of components. It would also allow for a full convergance between web apps that could be used on Android and iPad/iPhone and then be supercharged on Ubuntu Phone
[15:11] <kyleN_> so this is qml/qt theming, distinct from the current gtk theme mostly used in Ubuntu
[15:11] <kenvandine> kyleN_, yes
[15:11] <Riddell> olafura: that seems unlikely
[15:11] <kyleN_> will there be a clear list of the assets one needs to rovide to create a new theme?
[15:12] <victorp_> bzoltan there is a lot of examples for QT
[15:12] <victorp_> how about porting some to ubuntu components
[15:13] <victorp_> like samegame
[15:13] <victorp_> or maroon
[15:13] <codealot> Would it be possible to have the Ubuntu SDK almost match the Blackberry Cascades SDK
[15:13] <codealot> where you can opt for either/both the C++ and QML
[15:14] <victorp_> maroon is qml AFAIK
[15:14] <victorp_> but they are kind of burried
[15:14] <mzanetti> what is the issue with Qt apps with QML ui?
[15:15] <t1mp> mzanetti: it is not an issue, its good.
[15:15] <codealot> mzanetti: I'm working on the Terminal app for Ubuntu Touch and I'd wish to integrate Busybox
[15:15] <codealot> now to get that in via QML is a challenge
[15:15] <bjaanes> Is there any real difference between QML with C++ backend and QML with C++ plugins? I know these are two possible options to use c++ in the qml application - but the plugins seem more messy in practice. Any input on that?
[15:16] <victorp_> bzoltan - please please make sure that Qtcreator works well with LTS versions (12.04)
[15:17] <bjaanes> Most importantly for me: why is "pure" QML (no c++) beeing pushed so hard? What is the reasoning behind this?
[15:17] <victorp_> dpm - I think LTS is what most android developers use in companies writting mobile apps
[15:18] <mzanetti> bjaanes: +1. Same question here
[15:18] <victorp_> bzoltan ^^
[15:18] <victorp_> dpm - I meant the question from mzanetti and bjaanes
[15:21] <victorp_> bzoltan - vanhoof did some experiments on that and wrote some docs for cross compilation
[15:22] <mzanetti> QML has serious portability issues. All the Qt apps I wrote so far just compile on ubuntu phone. Every line of QML had to be rewritten.
[15:23] <victorp_> mzanetti - really?  I run a few of the QML examples on my desktop and just works
[15:23] <kenvandine> i couldn't get very far with pure QML, about 20 minutes in I hit the point where I needed to add some Qt
[15:23] <mzanetti> victorp_: ok. if you only use Rectangles you're fine. But use a Button
[15:23] <kenvandine> the real issue is app developers building for the target devices
[15:23] <victorp_> mzanetti, well yes, if you are using ubuntu components
[15:24] <victorp_> that is a good point, bzoltan it would be great to see UBuntu components support for other platforms
[15:25] <mzanetti> zsombi_: yeah... all for it. I just don't see why an applications entry point _needs_ to be QML
[15:26] <greyback> bjaanes: does that answer your question?
[15:26] <bjaanes> greyback, pretty much
[15:26] <greyback> bjaanes: have you any thoughts? Anything we missed, or disagree with?
[15:27] <mzanetti> I fully agree with all the points you said so far
[15:27] <victorp_> bzoltan - I think it depends
[15:27] <victorp_> I agree with you on declarative
[15:27] <victorp_> but stay away from .js
[15:27] <victorp_> ;)
[15:27] <sil-unwell> I think my question would be sort of the other way around: why would you want to use C++? If you start writing a pure QML app and then find that there's something you want to do that *can't* be done in there (say, you need to call a particular D-Bus API) then sure, write a C++ plugin (and give it to others, and ask for it to be put in the SDK!) No-one's discouraging doing that.
[15:27] <sil-unwell> But pure QML is way easier for less experienced Qt hackers to write, to test, to run, and to package. Speaking as a less experienced Qt hacker, I'm all for that.
[15:28] <greyback> victorp_: by "support for other platforms" you mean that things like Button should be themed to suit the platform? Or that out components just work on other platforms
[15:28] <t1mp> sil-unwell: +1
[15:29] <Riddell> how do you run QML programmes without a c++ wrapper? no official way in Qt 4 but there was a developer binary to do it, what's the case in Qt 5?
[15:29] <mzanetti> Riddell: same with Qt5
[15:29] <victorp_> bzoltan - how about access to simulated hardware?
[15:29] <sil-unwell> Riddell: qmlscene (the Qt5 equivalent of qmlviewer)
[15:29] <mzanetti> Riddell: there is qmlscene which is not meant to be a production tool according to its docs
[15:29] <kenvandine> we need to solve that
[15:29] <victorp_> bzoltan - gps, sensors..
[15:30] <greyback> Riddell: we're using qmlscene for now, but I;m hearing of a production tool being added to qt5.1 maybe
[15:30] <greyback> Riddell: otherwise we'll write our own simple QQuickView wrapper
[15:30] <greyback> and share it
[15:30] <Riddell> cp qmlscene ubuntu-ui-toolkit-runner? :)
[15:30] <mzanetti> :)
[15:30] <victorp_> bzoltan - JDI!! ;)
[15:30] <greyback> Riddell: pretty much :)
[15:30] <sil-unwell> t1mp: I completely understand that for people who know what they're doing and have extensive C++ and Qt experience, they want to continue using that, and that's fine for them; I just don't want those people to make new Ubuntu developers believe that those new developers have to learn C++ in order to get anything done.
[15:31] <greyback> bzoltan: we've lost you
[15:31] <t1mp> sil-unwell: I agree fully with that.
[15:31] <codealot> How about we start with an android virtual machine installed with Ubuntu Touch?
[15:31] <mzanetti> I do so too
[15:34] <t1mp> note that the SDK APIs are not fully stable yet, so we may change/tweak them in the future
[15:35] <sil-unwell> It would be really good if the developer.ubuntu.com documentation included some indication of when each thing got implemented (a date) or when it's hoped to be implemented (a date). So I can see what a Component can do right now and what it is planned to do even if it doesn't work yet.
[15:35] <sil-unwell> that's a lot better than seeing a component's documentation with "TODO" and nothing else written there :)
[15:35] <ara> sil-unwell, ++
[15:35] <t1mp> sil-unwell: good point
[15:36] <sil-unwell> so I might be delirious, so you're allowed to ignore me ;)
[15:36]  * dpm hugs sil-unwell :)
[15:37] <sil-unwell> is the documentation not autogenerated from the QML files which actually implement the components? It's all written by hand????
[15:37] <t1mp> sil-unwell: it is auto-generated from the QML files
[15:38] <dpm> sil-unwell, automatically generated, but currently copied manually to d.u.c
[15:38] <sil-unwell> t1mp: ah, right, good, I was really worried for a second there ;)
[15:38] <kyleN_> Can you discuss i18n support in the SDK?
[15:38] <codealot> how can I access the Ubuntu components Qt source?
[15:38] <sil-unwell> t1mp: it should be fairly easy to add a date-when-this-first-appeared thing to the generated docs, then, I would think (although I don't know much about qml generated docs so I could be totally wrong!)
[15:39] <udsbotu> uds-appdev-1: 5 minutes left in this session!
[15:40] <udsbotu> uds-appdev-1: 4 minutes left in this session!
[15:40] <rickspencer3> be careful about keeping the bar for contributions too high
[15:40] <sil-unwell> the etherpad says "Recommendation: Use QML for creating a beautiful GUI, and C++ for the backend using QML plugins." Was that really the recommendation? Shouldn't it be "Use QML for creating your application, unless you really need to do something that QML can't do, and then use QML for creating a beautiful GUI, and C++ for the backend using QML plugins." ?
[15:40] <rickspencer3> in terms of talking to you guys first
[15:40] <rickspencer3> sometimes I make a component for my own apps, and only later realize it might be generally valuable
[15:41] <rickspencer3> so it's not necessarily the case that I set out to make something generally useful
[15:41] <udsbotu> uds-appdev-1: 3 minutes left in this session!
[15:41] <codealot> I'm willing to contribute on the documentation
[15:41] <greyback> codealot: yay!!
[15:41] <t1mp> sil-unwell: that recommendation was quoted from gerry.
[15:41] <t1mp> greyback: do you agree with the quote?
[15:41]  * sil-unwell disagrees with greyback then ;-)
[15:42] <codealot> yes it is
[15:42] <kyleN_> what is the i18n/l10n story?
[15:42] <t1mp> kyleN_: I think there is no more time now to discuss i18n.
[15:42] <udsbotu> uds-appdev-1: 2 minutes left in this session!
[15:42] <t1mp> kyleN_: it is fully based on gettext.
[15:42] <t1mp> kyleN_: it is there. Basically a QML binding for gettext.
[15:42] <greyback> sil-unwell: I'd more put it, if QML&JS does not let you do backend tasks you want, then you need to use C++ for the backend
[15:43] <sil-unwell> greyback: right, that's what I think too :) Would you like to update the etherpad?
[15:43] <greyback> sil-unwell: can do
[15:43] <kyleN_> t1mp: good.
[15:43] <codealot> I'd said this earlier: can have a look at Blackberry Cascades and see if we can borrow something from it?
[15:43] <ralsina_> Isn't linkguist the "recommended" way to i18n QML apps?
[15:44] <sil-unwell> ralsina_: we want to intergrate with Ubuntu's existing excellent translations structure.
[15:44] <t1mp> kyleN_: i18n.tr() function links to gettext(). Documenting it propery is on our TODO list.
[15:44] <udsbotu> uds-appdev-1: This session has ended.
[15:45] <Mirv> linguist is a Qt tool for translations, but eg. KDE uses gettext nevertheless
[15:45] <ara> ta!
[15:45] <kyleN_> t1mp, how about plurals (ngettext()) and others. :)
[15:45] <dpm> thanks everyone!!!
[15:45] <kyleN_> cheers
[15:46] <jdstrand> thanks!
[15:46] <codealot> cheers
[15:46] <mzanetti> cheers guys
[15:46] <theDoctor_> Good session
[15:46] <dpm> kyleN_, we can expand on i18n on the next session, sorry there wasn't much time
[15:46] <kyleN_> dpm. ack
[15:46] <eclecticgeekery> Stupid question time: should a complete newbie forget about Quickly/Python/GTK and focus on learning QML/QT instead?
[15:46] <t1mp> kyleN_: plurals are supported as i18n.tr("singular", "plural", n) and we have i18n.dtr() where you can pass the domain as the first parameter.
[15:47] <eclecticgeekery> Didn't want to interrupt session with my silly question.
[15:47] <kyleN_> good question eclectic
[15:47] <greyback> eclecticgeekery: what sort of application would you like to make? For desktop or phone?
[15:47] <kyleN_> t1mp: thanks for that answer.
[15:48] <bjaanes> eclecticgeekery, not stupid question at all. You should have asked it :) I think its a good bet to focus on QML/QT for both phone AND desktop.
[15:48] <codealot> eclecticgeekery: I think I'd say yes. I've used both QML and QT and QML just feels straight to the point
[15:48] <greyback> eclecticgeekery: I tend to agree with bjaanes & codealot :)
[15:48] <codealot> and coming from a C++ background, you feel depreived
[15:48] <eclecticgeekery> Thanks guys.
[15:48] <codealot> of some control
[15:49] <lool> how was the SDK roadmap session?  :-)
[15:49] <bjaanes> eclecticgeekery, np. happy coding!
[15:49] <codealot> lool: its been a great session
[15:50] <lool> cool
[15:50] <lool> I'll watch the recording
[15:59] <JoseeAntonioR> dpm: ping
[16:02] <robin-gloster> o/
[16:02] <bjaanes> picture:yes, sound:yes;
[16:02] <JoseeAntonioR> dpm: works
[16:02] <dpm> http://summit.ubuntu.com/uds-1303/meeting/21675/appdev-1303-app-development-roundtable/
[16:02] <nerochiaro> yes
[16:02] <DasWu> both great
[16:02] <mpalo91> yes
[16:02] <netcurli> see and hear
[16:02] <Mirv> yes
[16:02] <theDoctor_> gotcha
[16:03] <highvoltage> hi!
[16:04] <robin-gloster> could you add lower third please
[16:05] <bjaanes> what robin-gloster said, lower third +1
[16:05] <bjaanes> It would be really helpful if we could see the names in the hangout...
[16:05] <robin-gloster> dpm^
[16:06] <greyback> bjaanes: if you hover your mouse over our pictures, do you see our names?
[16:06] <highvoltage> I missed the question, sorry :)
[16:06] <DasWu> I started using it on the weekend looks good so far
[16:06] <bjaanes> greyback, not really, no
[16:06] <t1mp> greyback: no, not in the youtube stream
[16:06] <greyback> ah ok, sorry
[16:06] <JoseeAntonioR> and mute when you're not talking :)
[16:07] <JoseeAntonioR> dpm: Hangout Toolbox>Lower Third tab, the lower third app is not working anymore
[16:08] <robin-gloster> yep, have been using the sdk. working nice so far biggest problem so far is lacking documentation for compnents and sys integration
[16:08] <bhenderson256> Just downloaded SDK last night... and haven't had a chance to dig in yet...
[16:08] <t1mp> robin-gloster: what do you mean with sys integration?
[16:09] <robin-gloster> e.g. how to use notifications in ubuntu touch
[16:09] <bjaanes> For my part, it worked well. However, it is lacking in documentation and examples. I am also very confused about screen size I should use and so forth.
[16:09] <DasWu> I don't really know whether its sdk related but I am still a bit confused on how to get data sources behind the qml, like how to access calender data that might be fetched from google calender
[16:10] <nerochiaro> i had to write my own
[16:10] <nerochiaro> using libindicate
[16:10] <Mirv> o/
[16:10] <bzoltan> DasWu:  I will cover it
[16:10] <dbarth> bzoltan: hey, and when you think you'll have an emulator, or something that can run the images we've published? i've seen that being part of the topics for this week
[16:10] <DasWu> bzoltan: cool!
[16:11] <ali1234> yes, we really need an emulator....
[16:11] <t1mp> dbarth: fyi, we discussed in the previous session http://summit.ubuntu.com/uds-1303/meeting/21630/appdev-1303-ubuntu-sdk-roadmap/
[16:11] <bjaanes> People, mute when not talking. Its hard enough to hear the ones who are talking allready
[16:12] <bzoltan> dbarth:  I will say few words here too about emulation
[16:12] <bzoltan>  bjaanes: good point
[16:15] <DasWu> Can I check what plugins are available already so I don't do redundant work
[16:15] <bjaanes> I assume you know this: but a rich and updated documentation is reeeeally important. I would like to be able to find full API reference, examples, best practice, tutorials and everything else from the sdk docs site
[16:15] <dbarth> right
[16:16] <dbarth> ok, makes sense; thanks
[16:18] <DasWu> yeah I like this idea of a repo as well
[16:24] <sil-unwell> dpm: I think I disagree about having a how-to-write-a-plugin tutorial until there are more tutorials, otherwise if there are only 2 and one is about plugins then it looks like C++ is more important than it actually is :)
[16:24] <bjaanes> I agree. Focus should be on how to write good apps.
[16:25] <greyback> sil-unwell: yeah I agree, writing plugin is a more advanced topic. The Qt documentation already covers it anyway
[16:26] <DasWu> Maybe you can link to good tutorials on the page
[16:26] <sil-unwell> dpm: insulting question, here. The currency converter app in the tutorial looks quite ugly :( Does it look nicer with a newer version of the SDK?
[16:26] <robin-gloster> they should be added to the documentation anyway
[16:27] <sil-unwell> dpm: note, this is not your fault ;)
[16:27] <greyback> DasWu: which page? The QtCreator docs do include it already. I can point you to it if you want
[16:28] <DasWu> would be great, but I was also refering to the app developer page so a new developer finds them also
[16:29] <sil-unwell> right. It is not very clear at all at the moment what I'm supposed to use. The app design guidelines say things like "you need a header!" but there's no good example of how to use that in QML because the tutorial was written before Header existed ;) Should every app have a MainView, for example? These are, I think, the tutorials which are needed.
[16:30] <t1mp> sil-unwell: agreed
[16:30] <sil-unwell> I am sort of prepared to say that a new release of the SDK should not be released until the documentation and core examples are also updated. But I imagine there will be fight-back from bzoltan  about that ;)
[16:32] <sil-unwell> Yes. Yes, I want you to hold it back. :)
[16:33] <sil-unwell> You wouldn't release, for example, a new SDK version with a broken Label in it. I think the documentation is as important as the code ;)
[16:33] <greyback> DasWu: I see what you mean. https://qt-project.org/doc/qt-5.0/qtqml/qml-extending-tutorial-index.html or https://qt-project.org/doc/qt-5.0/qtqml/qtqml-cppintegration-exposecppattributes.html are best places to start
[16:34]  * sil-unwell laughs
[16:34] <t1mp> I agree with bzoltan. It is still a developer preview
[16:34] <DasWu> greyback: thank you I will look into them
[16:34] <t1mp> but documentation is very high on our priority list
[16:35] <greyback> bzoltan: what's the IRC channel we should hang out on, so public can ask us questions?
[16:35] <greyback> bzoltan: #ubuntu-devel?
[16:35] <Mirv> #ubuntu-touch
[16:36] <codealot> #ubuntu-touch would be best for that
[16:36] <codealot> or rather #ubuntu-touch-devel
[16:36] <codealot> since #ubuntu-touch is more of talk on design and other issues
[16:37] <t1mp> http://bugs.launchpad.net/ubuntu-ui-toolkit for UI toolkit bugs
[16:37] <dpm> ubuntu-phone (AT) listsl (DOT) launchpad (DOT) net for discussion
[16:40] <DasWu> dpm: I like the idea, i was a bit lost on where to ask questions
[16:40] <Mirv> we're using the ubuntu-ui-toolkit project also for tracking PPA issues for 12.04 & 12.10 users
[16:43] <t1mp> facebook integration for qtcreator ;)
[16:44] <t1mp> ^(please don't take that serious)
[16:45] <nerochiaro> bzoltan: seems pretty long term
[16:47] <DasWu> would maybe interesting if a new thing is developed to see like this is how things should be used now
[16:47] <nerochiaro> david_: another point is, do we really want to cram everything in the IDE ? Isn't it better to have more things that work well than one thing that tries to do everything ?
[16:47] <DasWu> sound and video are good here
[16:50] <netcurli> it would be good to have this welcome screen with news and so maybe also as website
[16:51] <DasWu> I think the biggest thing to get the community involved is an easy entry point
[16:51] <t1mp> now is the first time I look at the standard welcome screen from QtCreator. Normally I open a project with it immediately.
[16:51] <DasWu> I used it a little and so far its a nice sdk
[16:52] <greyback> netcurli: +1
[16:53] <codealot> I agree on that
[16:53] <zsombi_> t1mp: it is still the first screen that opens in QtCreator :)
[16:54] <greyback> DasWu: glad you like it.
[16:55] <codealot> thank you all
[16:55] <bhenderson256> thank you!
[16:56] <dpm> everyone: plenaries are now on ubuntuonair.com
[18:07] <payloadd> I think in the ubuntu dev documentation it is not emphasized that one should develop the Qt way and look into Qt docs to get things done. It took me a while to find and look into Qt Mobility for example.
[18:29] <lool> dbarth: did you bring up remote apps?
[18:32] <lool> QUESTION: would it be possible to support the remote apps use case (thinclient) with API similar to webapps?  e.g. to integrate apps in the launcher
[18:37] <dbarth> lool: sorry i missed that
[18:37] <dbarth> otp
[19:03] <QtRoS> Hi all
[19:03] <mainerror> o/
[19:03] <macastiblancot> Hi folks
[19:03] <FunnyLookinHat> howdy
[19:03] <QtRoS> I can't login, is it normal?
[19:04] <FunnyLookinHat> QtRoS, to the etherpad?  Try joining the linked group ( ubuntu-etherpad-users I think?  )
[19:04] <FunnyLookinHat> Then refresh
[19:04] <QtRoS> How can I join this group?
[19:05] <QtRoS> Now I am on http://summit.ubuntu.com/uds-1303/meeting/21616/appdev-1303-coreapps/, link from david's letter
[19:05] <QtRoS> In bottom I see form to logging in pad.ubuntu.com
[19:05] <robru> I can't seem to get the video on this one...
[19:05] <QtRoS> But I can't login :(
[19:05] <fginther> I've refreshed and see no video, should I?
[19:05] <robru> can somebody link the youtube page directly here?
[19:06] <QtRoS> Any one from RSS Reader team?
[19:06] <FunnyLookinHat> robru, I don't believe it has started yet - should be available soon
[19:07] <FunnyLookinHat> http://www.youtube.com/watch?feature=player_embedded&v=5gtCOQrugkk
[19:07] <robru> oh, there we go
[19:07] <robru> FunnyLookinHat, thanks
[19:07] <alecu`> yes!
[19:07] <bfiller> we can see you
[19:07] <FunnyLookinHat> Yup.
[19:07] <gatox_> yes
[19:07] <isantop> We've got you#
[19:07] <robru> yes
[19:07] <alecu`> loud and clear!
[19:07] <ahayzen> o/
[19:08] <b_> test
[19:08] <alecu`> I think gatox_  should join
[19:08] <alecu`> he's working on the twitter client
[19:08] <FunnyLookinHat> S76 here - we'll join the hangout if there's room
[19:09] <nerochiaro> hi folks
[19:09] <gatox_> alecu`: dpm i prefer tomorrow in the twitter app to join to the hangout... not having the best connection today
[19:09] <fmunozs> I'm from the twitter team too
[19:09] <daliusd> I'm calculator dev ;-) I will answer questions here if there will be any
[19:09] <nerochiaro> any questions on notepad or camera, you can ask me
[19:09] <mzanetti> nerochiaro: those are not core apps :P
[19:10] <nerochiaro> mzanetti: thought camera was
[19:10] <nerochiaro> mzanetti: seems pretty core to me
[19:10] <mzanetti> nerochiaro: its about the community developer core apps
[19:11] <nerochiaro> mzanetti: ok, clear titles then :)
[19:11] <pmcgowan> I think its fair to include the ones we already worked on
[19:11] <pmcgowan> in the discussion
[19:14] <isantop> Browser
[19:14] <mainerror> Awesome effect.
[19:14] <mainerror> Keep it like that. :D
[19:14] <pmcgowan> infinty
[19:14] <bjaanes> To infinty and beyond!
[19:14] <robru> can see only grass
[19:15] <fmunozs> backgraound screen
[19:15] <isantop> Only desktop
[19:15] <bjaanes> No
[19:15] <robru> no calendar
[19:15] <macastiblancot> nope
[19:17] <daliusd> basically we are waiting for further design ideas
[19:17] <pmcgowan> do have recommended designs in place for all the apps or a timeline for that?
[19:18] <pmcgowan> thanks mika
[19:21] <bfiller> we might want to think about having a mentor from the Phablet Engineering team for some of the key apps to ensure consistency, sound architecture, unit testing, etc..
[19:21] <codealot> anyone working on the Terminal?
[19:22] <isantop> Are these core apps listed the only apps in the pipeline, or are there plans to expand this list?
[19:22] <pmcgowan> any code reviews or merge reviews at this time?
[19:22] <bfiller> thanks David
[19:22] <pmcgowan> I can work with popey on that
[19:23] <daliusd> pmcgowan: we do that in our team
[19:23] <pmcgowan> great
[19:24] <daliusd> There is jenkins even running but it could run qmltestrunner as well (it looks like it doesn't)
[19:24] <dptm-desktop> https://launchpad.net/ubuntu-phone-coreapps
[19:24] <DasWu> are there efforts to unify things on an architectural level, like handling accounts, i.e. google account might be used in mail, contacts, calendar and it would be unwise to store the login stuff more than once
[19:25] <pmcgowan> DasWu: yes want to use ubuntu online accounts
[19:25] <DasWu> pmcgowan: is there stuff done that I could use already?
[19:25] <gatox_> DasWu: pmcgowan we are using online accounts in the twitter app
[19:26] <pmcgowan> needs to be more obvious as part of the kit, right
[19:26] <bfiller> DasWu: hasn't landed yet in the images but think they are almost done
[19:26] <bfiller> gatox_: you using the friends libraries?
[19:26] <dobey> gatox_: are you using the gwibber stuff? or will there be gwibber and a twitter app both?
[19:27] <bfiller> friends-service and friend api are currently being used by share-app
[19:27] <robru> mardy has already developed a maps app in qt, but I'm unsure if it's compatible with the phone or not.
[19:27] <dobey> i don't think anyone would ship a smart phone in 2013 without a maps app
[19:28] <gatox_> dobey: bfiller: no, we are not using anything from gwibber right now.... neither friends (which is made on python)... we need to analyze that a little further...... but currently we are using our own implementation in c++ talking with online accounts, the keyring and the twitter api
[19:28] <pmcgowan> yes we do intend to have a map app
[19:28] <bfiller> gatox_: you guys should sync with kenvandine to talk further about that
[19:29] <pmcgowan> starting with a webapp approach perhaps with something like here.net
[19:29] <dobey> for maps, i'd recommend possibly building on leaflet.js as a starting point (if their license permits this sort of use)
[19:30] <kenvandine> the people lens uses friends too
[19:30] <alecu`> A browser opening google maps, is better than having a crappy map app. (and remember ios maps!)
[19:30] <DasWu> gatox_: is there a branch that I can have a look at so I can use that code for the google account stuff I want to use it for the calender stuff
[19:30] <mmcc_> gatox_ and anyone thinking about twitter clients ,don't forget the 100K user token limit for twitter API clients that "replicate the twitter core user experience": https://dev.twitter.com/terms/api-terms
[19:31] <dobey> OpenMapQuest provides very nice tiles
[19:31] <dobey> this is why i suggest building on leaflet.js
[19:32] <fmunozs> gatox_, I see no merge request for the c++ code with online account integration on the ubuntu twitter app?
[19:32] <gatox_> DasWu: https://github.com/saruneko/tori
[19:32] <DasWu> gatox_: thx
[19:34] <gatox_> fmunozs: we haven't make an attemp to merge anything yet... we need to discuss a couple of things more i think
[19:34] <bfiller> regarding maps, qtlocation is working and enabled so that should be utilised for any maps application work
[19:34] <daliusd> no complains :)
[19:35] <DasWu> for the calendar app I am really happy with the designs
[19:36] <fredbuntu> How is the browser going?
[19:36] <QtRoS> Discussion about design problems, or what? And who are those guys? I know only David :)
[19:37] <QtRoS> Ahaha Thanks :)
[19:37] <fredbuntu> Okay, thanx
[19:43] <codealot> can we borrow from the PC-BSD phi packaging way?
[19:43] <codealot> *pbi
[19:43] <fmunozs> should the people from other core app teams wait for designs from the Design Team, or they will just focus on those apps already?
[19:45] <flosky> Will you be able to sync the calendar across different phones / PCs (via U1, Gmail, etc)??
[19:45] <PaulyboyUK> thimk thats a must have!
[19:46] <codealot> **sorry meant for different room
[19:47] <DasWu> flosky: I guess assuming that we can use things like the google accounts and have support for ical syncing should be possible
[19:48] <DasWu> to test I will probably look into supporting ical first
[19:48] <dpm> fmunozs, let me answer your question in a minute
[19:49] <isantop> What tools are being used to create the app wireframes?
[19:50] <isantop> What tools are being used to create the app wireframes?
[19:52] <dpm> https://ubuntu.mybalsamiq.com/projects/appdeveloperuploadprocess/grid
[19:53] <fmunozs> thanks
[19:57] <isantop> What is the timeframe for fleshing out the design guidelines?
[19:58] <isantop> THanks
[19:59] <QtRoS> This girl is really positive :)
[19:59] <QtRoS> Smiling all the time
[19:59] <daliusd> Thanks
[19:59] <fmunozs> bue
[20:00] <QtRoS> Bye!