On Friday, March 25, 2011 09:11:48 AM Ville M. Vainio wrote: > On Thu, Mar 24, 2011 at 10:16 PM, Richard Dale > > <richard.d...@telefonica.net> wrote: > > I personally think that the Nepomuk non-application specific integrated > > data approach could be a killer feature of MeeGo. In comparison iOS is > > completely > > Agreed. Luckily tracker will still be there on the platform (as Marius > stated earlier in this thread), so it can be used by willing > applications. It's just that contact information is not *primarily* > stored there anymore - but we can arrange for an (unofficial) way > where it gets moved there from EDS anyway. Well Tracker is in MeeGo sure, but I was talking about RAD environments on top of Tracker, and in one of the mails on this architecture thread I saw this:
On Monday, March 07, 2011 10:06:08 PM Arjan van de Ven wrote: > > Are you planning to support or implement a QSparql backend for EDS? > > I suspect we'll never see QSparql in MeeGo the way things are going.... Disclaimer: I am a QSparql developer QSparql is the standard way of accessing Tracker from Maemo in Qt code, and as far as I know it has been packaged for MeeGo too. In order to build the Qt based RAD environment, that I personally dream of, QSparql will be needed. Maybe it shouldn't be used directly by application programmers, but it will be needed as a base for building visual development tools that might use QML with QtCreator plugins support. -- Richard _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
