public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] make bluez GNOME UIs singletons
Date: Wed, 17 Oct 2007 16:11:48 +0100	[thread overview]
Message-ID: <1192633908.10179.2.camel@snoogens.fab.redhat.com> (raw)
In-Reply-To: <5f84803c0710170748j57f46eebh37a6707b9ec02b86@mail.gmail.com>


On Wed, 2007-10-17 at 10:48 -0400, Chris Rivera wrote:
> On 10/17/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>         
>         actually the wizard and the properties applications are meant
>         to be
>         _not_ singletons. They are designed in a way that multiple
>         instances can
>         exist and work together.
>         
>         For the applet, only one instance is useful. However for
>         testing and 
>         development purposes it is nice to start two of them.
> 
> The applet already has the ability to launch the properties dialog and
> I think it should also have an entry to launch the wizard.   This
> makes it very easy to get to a state where you have multiple copies
> open at once.  I think it's confusing to users and it doesn't buy you
> anything.  Just in case it's not clear, the patch allows for one
> instance per desktop session. 

Both of you are right. Developers should be able to launch another
applet or prefs for testing, but users should only ever see one applet
and prefs dialogue.

Maybe a command-line flag or envvar to disable the singleton behaviour
in Chris' patch would be acceptable for Marcel?

Cheers


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-10-17 15:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 18:38 [Bluez-devel] [PATCH] make bluez GNOME UIs singletons Chris Rivera
2007-10-17 14:24 ` Marcel Holtmann
2007-10-17 14:48   ` Chris Rivera
2007-10-17 15:11     ` Bastien Nocera [this message]
2007-10-18 10:15       ` Fabien Chevalier
2007-10-31 16:14         ` Marcel Holtmann
2007-10-31 16:24           ` Bastien Nocera
2007-10-31 16:36             ` Marcel Holtmann
2007-11-13 16:24             ` Chris Rivera
2007-11-13 16:30               ` Bastien Nocera
2007-11-13 17:06                 ` Chris Rivera
2007-11-27 15:45                   ` Chris Rivera
2007-10-24 19:54       ` Chris Rivera

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=1192633908.10179.2.camel@snoogens.fab.redhat.com \
    --to=hadess@hadess.net \
    --cc=bluez-devel@lists.sourceforge.net \
    /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