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

List:       kde-bugs-dist
Subject:    [Bug 59833] Better integration of hotpluggin in KDE
From:       Christoph Eckert <mchristoph.eckert () t-online ! de>
Date:       2004-10-31 23:19:21
Message-ID: 20041031231921.13022.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
        
http://bugs.kde.org/show_bug.cgi?id=59833        




------- Additional Comments From mchristoph.eckert t-online de  2004-11-01 00:19 \
------- Well, incidentally I did play a bit with hotplug today. I simply wanted to \
download images from my camera as soon it gets plugged in, then deleted the files on \
the camera and then - which I didn't manage, konqueror to be loaded with the newly \
created directory.

Maybe a first step isn't kde related, but the hotplug people could add the following:

As soon a hotplug event is registered, hotplug looks in ~/.hotplug for scripts to \
execute them in the users context.

Then, KDE could add reasonalble preconfigured scripts there, maybe invoke digikam or \
camera:/ as soone a usbcam gets detected.

Furthermore, often new hardware gets bought which isn't yet included in the hotplug \
distribution.

So was mine. A successor model of a model which already has been in the \
/etc/hotplug/usb.usermap file. But mine didn't.

So I had to read a lot to understand how hotplug works. Perhaps KDE could offer \
somehow a kcontrol module to add new hardware using the admin mode.

Anyway, if we think about the desktop, we should work together with the hotplug \
people to achive the maximum result?


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