On Mo, 2010-11-08 at 13:42 +0000, Sivan Greenberg wrote: > On Mon, Nov 8, 2010 at 2:57 PM, Patrick Ohly <patrick.o...@intel.com> wrote: > > > > The question of Ovi.com<->MeeGo interoperability is something completely > > separate from that. It is done inside Nokia and I don't know much about > > it. Sateesh should be able to tell you more. My interest is more from an > > Sateesh, could you please kindly elaborate on the state of things > then? Also, what efforts, if at all, are carried to create a QT/MeeGo > UI ?
If your question is about a MeeGo UI, then I can answer that: for Handset, Intel is working on a MTF-based UI. I don't know of any plans for a desktop Qt UI or of data storage support for KDE/Evolution. > > architectural point of view: if tweaks to a shared file in /etc/sync are > > necessary, how can we get those into MeeGo Core? > > My experience with Debian tells me that you need a package in core for > sync configuration, or delivering the sync framework package (be it > Buteo or else) with the required configuration file modifications > represented in the binary package, possibly through a patch phase in > the package build process. Installing the file isn't the problem ;-} It's already part of the buteo-syncml package. The open question is: which value should the omit-data-update-status value have in it? If the value depends on who Buteo is talking to, then it has to be in a peer-specific config file. -- 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
