On Friday, March 25, 2011 03:01:43 PM Ville M. Vainio wrote: > On Fri, Mar 25, 2011 at 4:53 PM, Richard Dale > > <[email protected]> wrote: > > 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. > > Is there a particular reason not to have QSparql, when you already have > Tracker? I wouldn't have thought there was, but obviously the statement above from Arjan van de Ven concerned me.
> (Someone should really summarize these threads in a wiki) > > > 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. > > Perhaps you can elaborate on this RAD tools elsewhere, say, > meego-community mailing list? I have hard time thinking how a RAD tool > for sparql would look like, but the thought is intriguing... Well, RDF stores are just databases that happen to be more general and based on graphs, rather than being based on tables like relational databases. Often you can view RDF data as a table and that works fine. But I don't see any reason why visual development tools for RDF/SPARQL stores should look much different to what people are familiar with from tools like Visual Basic. Or ORM's like NeXT/Apple's Enterprise Object Framework, or the Core Data modern equivalent, that are combined with Interface Builder for visually composing UIs. -- Richard _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
