On Fr, 2011-04-01 at 19:21 +0100, Jens Georg wrote: > > > Let's be more specific about identifying work which needs to be done. > > > I've put together some thoughts here: > > > http://wiki.meego.com/Architecture/planning/evolution-data-server > > > > I'd like to clarify something from the page: > > > > Maemo solution: QtContacts (API) + QtContacts-Tracker (glue code) + > > Could we stop calling it "glue code"? It's about as much glue code as > the folks backends.
That's my bad. I know that QtContacts-Tracker does a significant amount of work that goes way beyond mere glue code. What I must have had in mind is QtContacts-EDS: that really is just some glue code that binds together the QtContacts, QtVersit and libebook APIs. -- 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 http://wiki.meego.com/Mailing_list_guidelines
