From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Jansen Date: Sat, 15 Jun 2002 09:44:09 +0000 Subject: Re: xhotplugd -- project idea Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Saturday 15 June 2002 02:48, you wrote: > Here I'm not sure whether it's better to have a single list or a > per-desktop environment list -- since programs to launch are commonly > tightly connected to the desktop environment. e.g. different "New device > is found" programs, different apps to handle digital cameras etc. You certainly need a per-desktop environment list. But I would rather let an desktop environment-specific daemon (that is based on a lib) start the apps, at least in KDE this has some advantages: - it would be possible to implement the gui or a part of it (e.g. a system tray icon or a popup dialog) in the daemon - KServices could be used as handler, and a KServiceType to describe the handlers for various events, which is the KDE way to do things like that. - apps could be started using kdeinit which is faster and requires less memory > The disadvantage would be that a KDE digital camera program couldn't try > to register itself for Camera USB devices unless its running under a KDE > xhotplugd, since it expects to talk to it via DCOP. Yes, but I dont see many apps doing this, and those that do should work without these events (in the worst case you have to restart them). Most hotplug events just trigger configuration dialogs. bye... _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel