Simple search API proposal, take 2
Mikkel Kamstrup Erlandsen
mikkel.kamstrup at gmail.com
Tue Jan 16 02:05:27 PST 2007
2007/1/15, Fabrice Colin <fabrice.colin at gmail.com>:
> On 1/15/07, Mikkel Kamstrup Erlandsen <mikkel.kamstrup at gmail.com> wrote:
> > 2007/1/12, Fabrice Colin <fabrice.colin at gmail.com>:
> > > - ShowConfiguration
> > > > Open a graphical interface for configuring the search tool.
> > > Is it safe to assume that because this method was called on the
> > bus
> > > that a graphical display is available ?
> > No you can't assume that. We could make the method return a string with
> > error message. The method would be considered failed if the response !=
> > Errors could also arise if you don't have the toolkit installed in which
> > config tool was implemented.
> Well, that's very much a package dependencies issue but I get the idea.
The package installing the search daemon might not depend on, say, Qt,
because the daemon could be written without it. The config ui could be
bundled in a package together with a search ui, depending on Qt.
> You would have yo use the live api to pick up such changes in the result
> Are you saying it would be possible to mix and match calls to the simple
> the live APIs ?
> If an app needs to be notified about changes, let it use the live API
> all the way.
I didn't mean to mix the two interfaces... Sorry if I was unclear. It would
be nice though if they used the same data structures and naming conventions.
That way the wasabi spec as a whole would feel more coherent, and it would
be easier for apps to port to the other interface if they decide their needs
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the xdg