linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: xhotplugd -- project idea
Date: Sat, 15 Jun 2002 09:44:09 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102413271307356@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102406538226828@msgid-missing>

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

  parent reply	other threads:[~2002-06-15  9:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 14:34 xhotplugd -- project idea Ilya Konstantinov
2002-06-14 15:59 ` Bill Nottingham
2002-06-14 16:49 ` Greg KH
2002-06-14 17:55 ` Tim Jansen
2002-06-14 18:04 ` Chris Hanson
2002-06-15  0:22 ` Ilya Konstantinov
2002-06-15  0:38 ` Tim Jansen
2002-06-15  0:48 ` Ilya Konstantinov
2002-06-15  9:44 ` Tim Jansen [this message]
2002-06-18 17:14 ` Jim.Gettys
2002-06-19 20:19 ` Ilya Konstantinov
2002-06-20 14:06 ` Jim.Gettys
2002-06-20 17:28 ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-102413271307356@msgid-missing \
    --to=tim@tjansen.de \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).