[Kde-silk] [Draft] Video Providers DataEngine

Alessandro Diaferia alediaferia at gmail.com
Thu Oct 15 21:48:17 CEST 2009


2009/10/15 Sebastian Kügler <sebas at kde.org>

On Tuesday 13 October 2009 00:03:27 Alessandro Diaferia wrote:
> > 2009/10/12 Sebastian Kügler <sebas at kde.org>
> >
> > > On Sunday 11 October 2009 12:53:26 Alessandro Diaferia wrote:
> > > > > I'll give it a try later tonight, on a train right now :)
> > >
> > > Alright, I've tried it and it basically works. :-)
> > >
> > > From reading through the code, is my assumption correct that the engine
> > > searches in
> > > one service at a time?
> >
> > right but that's going to change if we want generic queries :)
> > I should probably load all the available providers at the beginning in
> >  order to query them all at each source request.
> >
> > > That might make sense, though I wonder if a generic query wouldn't be
> > > more intuitive
> > > to the user (the developer in this case). I wouldn't care a lot which
> > > service a video
> > > comes from, but on the other hand, it's easy enough to query for
> > > providers and then
> > > search through all providers. Not sure what's nicer though: prefixing
> the
> > > query with,
> > > for example youtube: is less intuitive, but this way, constraining the
> > > search to one
> > > provider is a lot easier.
> >
> > Well i was initially for allowing 2 kinds of query: one without
> specifying
> > the service so basically just "query&constraints"
> > and the second one like it acts now. From the mediacenter point of view a
> > generic query is nice since the user will just interact with a browser
> > widget that allows looking for videos hosted on the web. But at the same
> > time he (the user) might want to look for a specific video from a
> specific
> > provider. This is a hard point because from the silk point of view
> probably
> > the specific service stuff should be completely hidden.
>
> Well, not so sure about that. I indeed thought about the case where you
> want to
> browse a specific service (this also makes it more attractive to be used by
> content
> providers who want to build functionality around "their service"). I think
> being able
> to specialize here makes sense (but the default / easiest way should
> probably be
> "search in all providers".
>

+1


> Sorry for the delay btw. I've been travelling with spotty internet
> connection. Should
> become better again now :-)
>

No problem, I'm currently a little busy with my thesis :-)


> --
> sebas
>
> http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
>
> _______________________________________________
> Kde-silk mailing list
> Kde-silk at kde.org
> https://mail.kde.org/mailman/listinfo/kde-silk
>
>


-- 
Alessandro Diaferia
KDE Developer
KDE e.V. member




-- 
Alessandro Diaferia
KDE Developer
KDE e.V. member
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-silk/attachments/20091015/6a868c58/attachment.htm 


More information about the Kde-silk mailing list