On Mo, 2011-03-21 at 21:31 +0000, Philip Van Hoof wrote: > On Mon, 2011-03-21 at 20:54 +0100, Patrick Ohly wrote: > > On Mo, 2011-03-21 at 17:45 +0000, zoltan....@nokia.com wrote: > > > > From: Patrick Ohly, on 21 March, 2011 16:37 > > > > In a nutshell, the goal is to keep QtContacts, QMF and KCalCore as the > > > > main APIs used by applications and the higher-level QtMobility APIs. If > > > > we can achieve that, very little will have to be done in applications > > > > once we change the core components. > > > > > > This will break libcommhistory. > > > > I'm aware of that, and I don't claim that there is an answer. There is a > > task open for those who need libcommhistory (or something like it) to > > look into this problem and comment on the current proposals. > > Ok, so.. I'll need something like libcommhistory. Check. > > What are the current proposals for things like libcommhistory? > > (this is a real question. You're the architect: don't sidestep it again)
No, I'm not officially a MeeGo architect. I might be doing some of the work at the moment, but others also need to comment, in particular for communication history. > This part is opinion I'll refrain from commenting on opinions. Remember, let's keep it technical. -- 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 MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
