I like that :) On Tue, Jun 22, 2010 at 9:11 AM, <[email protected]> wrote:
> Hi Patrick, > > I am Min working with Gerard in Qt product management team. As Gerard said > it is exciting times. :) > > And thanks for offering code review on APIs! Great news is that the public > tech preview for Mobility 1.1 that includes Calendar API is scheduled in two > weeks time. It will be announced on Qt Labs at > http://labs.trolltech.com/blogs/. If you cannot wait till then, you can > check the public repository at > http://qt.gitorious.org/qt-mobility/qt-mobility/commits/master even though > I don't think Calendar API is merged in master yet. Is Michael Goddard one > of your contacts in Qt Mobility? Michael is a tech lead for Calendar API as > well. > > Then, we would like to invite you to > [email protected] list to discuss domain specifics. > You can join the mailing list from > http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback. We will > be using this one until we set up a new infrastructure under Qt open > governance. > > The MeeGo backend will be developed by the Qt Mobility team and we aim to > release it in Mobility 1.2 which is due in early April 2011. For now our > main focus is Mobility 1.1 release in October. > > It seems http://bug.meego.com is down at the moment so I will skip to > Mutlimedia question. QtMultimedia in Qt is only covering low level, basic > use cases. As there is some common parts, Multimedia module in Mobility is > called QtMultimediaKit and it has rich APIs for playback, recording, image > viewing, playlist etc. QtMultimediaKit will be released with Mobility 1.0.1 > release in a couple of days. You should use it instead of QtMultimedia in Qt > if you want to use features just mentioned. > > Thank you. > > Best Regards, > Min > > P.s I will ask Qt web team to fix the link breakage. > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of ext Patrick Ohly > Sent: Tuesday, 22 June 2010 4:25 PM > To: Loughran Gerard (Nokia-D-Qt/Brisbane) > Cc: MeeGo-dev > Subject: Re: [MeeGo-dev] Qt Mobility says "Hello MeeGo World!" > > Hello Gerard! > > On Tue, 2010-06-22 at 04:22 +0100, [email protected] wrote: > > By way of introduction, my name is Gerard Loughran and I am a senior > > product manager at Nokia. My key responsibility is our Qt Mobility > > program and the new APIs we are bringing to Qt developers. > > I wanted to make this slightly formal introduction prior to involving > > myself more on the lists. > > Thanks for taking the time to introduce yourself. That's definitely > useful. Using MeeGo as the main development platform is of course good > news. > > FWIW, my own interest in QtMobility is primarily around PIM storage. As > the author of SyncEvolution, I have worked with a variety of systems > that handle PIM data - not just Evolution, as the name implies, but also > Mac OS Addressbook, Akonadi, and now of course QtContacts and > KCalExtended. > > Can you perhaps say a bit more about the QtMobility team's plan to add a > calendar API? It is mentioned here > http://qt.nokia.com/developer/qt-roadmap#calendar-api but without any > further details. BTW, the link underneath for "How to contribute" leads > to a "page not found" error. Is that meant to link to qt.gitorious.org? > > If you already have some API drafts for calendar, then I'd be interested > to have a look at them. I could help review them. We also need a backend > implementation for MeeGo. > > I have already been in touch with several of your colleagues in the > QtContacts related projects. We are currently working towards including > the latest code drops in MeeGo, see: > http://bugs.meego.com/show_bug.cgi?id=2590 > > #qtcontacts-tracker on freenode is used to discuss issue live. For > recording issues, as of today there is a component in bugs.meego.com for > it, which also happens to be the first public bug tracker for > qtcontacts-tracker, the main backend for QtContacts (at least in MeeGo): > > http://bugs.meego.com/enter_bug.cgi?product=OS%20Middleware&component=QtContacts > > There was some debate (http://bugs.meego.com/show_bug.cgi?id=3153) > whether each individual component (QtMobility/Contacts, > qtcontacts-tracker, ...) should get is own entry in the tracker. In the > end we went for one component "QtContacts" because as a user of Bugzilla > and of the API it is hard to tell the difference. > > Speaking of packaging QtMobility, there's one issue that was encountered > in #2590 and also discussed recently here on the list ("Qt packaging"): > what's the status of QtMultimedia? Qt and QtMobility provide conflicting > (?) implementations of it. As Thiago pointed out, QtMultimedia is part > of Qt and must stay there for API compatibility reasons. Is that the > version of the API that applications should use until further notice? > > -- > Best Regards, Patrick Ohly > > The content of this message is my personal opinion only and although > I am an employee of Intel, the statements I make here in no way > represent Intel's position on the issue, nor am I authorized to speak > on behalf of Intel on this matter. > > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- Thanks and Kind Regards, Mahendra Panpalia
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
