[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [PATCH + FEATURE] Automatic notification of hotplugged devices
From:       Edwin Schepers <yez () home ! nl>
Date:       2005-05-13 20:08:12
Message-ID: 200505132212.49920.yez () home ! nl
[Download RAW message or body]

On Friday 13 May 2005 05:11, Kévin Ottens wrote:
> > I dislike seeing an intrusive windows poping each time I plug in a device
> > too. I made a similar feature in kdenonbeta/kvm, but with a more
> > unobstrusive passive popup. You could have a look at the code and make up
> > your mind.
>
> Hmmm, I didn't know kvm used a passive popup... I was thinking of this
> solution too. I'll take a look at it, I discussed with Aaron Seigo who
> tends to prefer the window in this case (using the same argument used by
> Edwin in this thread).
For me, this is a minor issue that can easily be made configurable.
>
> > As for your patch, I am currently working on a bug in HALBackend, and it
> > might become irrelevant. Still, I will think about it...
>
> Hence why I dislike the design decision to merge both like this. It must be
> something separate (another kded module, or something lying in the
> systray), or alternatively inherit from BackendBase this way the code would
> be far less intrusive...
My bigger problem is that (when using another kded module) is that users are 
saddled up with a program which takes resources, startup time, desktop space 
for something they're maybe never to use (or seldom). Can you address this 
issue ?

Thought from a 1.5hour car trip :
We now have the HAL daemon sending signals, catched by the kdedmodule. Now we 
need another program which catches signals from the kdedmodule ?

I think it is not intrusive to extend the functionality of the Media Manager 
with some notification. Even when that means that the notification has to be 
made at some more points ( However I'm not sure if I use cdpolling when I 
already use HAL).

I already looked at kvm before, but when I read the README stating that the 
functionality moved to the media:/ ioslave, I looked no further to this and 
concentrated on the media:/ + accessories.

What about the following (having full blown functionality :)

When kdedmodule receives a signal (i'll call the medianotifier now 
mediahandler):
1. if mediahandler is not started then
     start mediahandler
2. send out a DCOP signal about a new device

When the mediahandler gets started:
1. It gets started in the systray
2. It starts listening for signals.
3. When it receives a signal, it notifies the user (according to the user's 
configuration).

From the systray, the configuration can be accessed (just like kdeautorun) and 
devices can be "safely removed". (Also mediahandler can be exited of course)

I hope you can agree with this.

Regards,
Edwin

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]