On July 10, 2010, Alessandro Diaferia wrote:
> data sharing through the dataengine as we're no longer creating a source
> for each query but, actually, this isn't mandatory as rarely different
> applets will show the same data from the dataengine.
this really is the key issue. if the answer is "th
Sorry for the delayed reply.
As far as i know making use of services is really useful when asking
additional information to existing sources. And this, as Aaron suggests,
might be done on sources representing each available plugin. So, likely, the
dataengine can have a source for each available ba
On July 8, 2010, Hayri Bakici wrote:
> > is this something that belongs more in a DataEngine, or in a Service?
> > consider
> > whether the results will be useful to more than one visualization,
> > whether a
> > visualization will want to change the query often (versus them being
> > long- lived),
>
> is this something that belongs more in a DataEngine, or in a Service?
> consider
> whether the results will be useful to more than one visualization, whether
> a
> visualization will want to change the query often (versus them being long-
> lived), etc..
so, what do you suggest then? :)
_
On July 5, 2010, Onur-Hayri Bakici wrote:
> I was thinking about the queries that should be used when querying tha
> addons since we mostly search for web-media i'll suggest the queries like
is this something that belongs more in a DataEngine, or in a Service? consider
whether the results will be
okay, that looks like a more generic query.
bests
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
2010/7/6 Onur-Hayri Bakici
> Hey guys!
>
> I was thinking about the queries that should be used when querying tha
> addons
> since we mostly search for web-media i'll suggest the queries like
>
> provider:media?constraint1=value1&constraint2=value2
>
> so for example
>
> flickr:photo?text=birds /
Hey guys!
I was thinking about the queries that should be used when querying tha addons
since we mostly search for web-media i'll suggest the queries like
provider:media?constraint1=value1&constraint2=value2
so for example
flickr:photo?text=birds //for searching photos text "birds"
flickr:albu
