[PATCH] A KJob jobtracker that uses kuiserver, or falls back to dialogs.

Rafael Fernández López ereslibre at kde.org
Thu Sep 4 11:31:46 BST 2008


> While that might certainly be an option, I don't know if that's the most
> desirable. Now, we have some kind of implicit configuration: the user has an
> kuiserver applet on his desktop or has the kuiserver app running, and it will
> be used, or he doesn't have it running and the oldskool dialogs will be used.
> Even when he adds a kuiserver later on, or removes it, the behavior of this
> jobtracker will automatically change.
> While it is easy enough to make this jobtracker read a config option and
> decide it's behavior based on that (well, the most difficult question in this
> case would be: where to place this option), I personally think the   
> 'automatic'
> setting (as it is now in this patch) would be the most desirable. But I'm
> absolutely not a usability expert so feel free to convince me having this
> setting is in fact better. :)

The main problem here is that I feel that you are talking exclusively  
about "Separate Windows" vs. "kuisever PLASMOID". kuiserver is a  
standalone application, which will be executed by its own (auto start  
service) if it is requested by D-Bus.

This is an important bit, because the plasmoid is a matter of "or you  
have it, or you don't". But an application that will just pop up, is a  
different matter...

As I say, I will give more time to this issue and see how can I handle  
this. However, I think this won't be too hard.

Rafael Fernández López.

More information about the kde-core-devel mailing list