Hello! 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 http://wiki.meego.com/Architecture/planning/evolution-data-server/QtContacts_storage_plugin http://wiki.meego.com/Architecture/planning/evolution-data-server/eds-improvements
The first page does include a very simplistic comparison of the different options. I thought about leaving out that part altogether, but decided otherwise because I believe that listing some of the pros and cons in public is useful. No flame wars, please. For contacts and calendar it is fairly obvious where the pain points are, so let's focus on that for now. I'm interested in getting feedback on the proposed EDS improvements. At this point, I have the QtContacts-EDS contact manager working for reading and writing contacts, as outlined in the page linked to above. Change notifications are missing. It's just proof of concept (non-)quality. I suspect that I need to get open source approval first before publishing it somewhere. I have not done any prototyping yet with KCalCore, but I expect that similar improvements as for contacts will be useful for that work, too. -- 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
