2007/1/15, Fabrice Colin <[EMAIL PROTECTED]>:
On 1/15/07, Mikkel Kamstrup Erlandsen <[EMAIL PROTECTED]> wrote: > 2007/1/12, Fabrice Colin <[EMAIL PROTECTED]>: > > - ShowConfiguration > > > Open a graphical interface for configuring the search tool. > > Is it safe to assume that because this method was called on the session > bus > > that a graphical display is available ? > > No you can't assume that. We could make the method return a string with an > error message. The method would be considered failed if the response != "". > Okay. > Errors could also arise if you don't have the toolkit installed in which the > 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 set. > Are you saying it would be possible to mix and match calls to the simple and 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 change. Cheers, Mikkel
_______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
