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] CUPS plugin discovery bits
Date: Tue, 29 May 2007 11:26:23 +0100	[thread overview]
Message-ID: <1180434383.3030.70.camel@cookie.hadess.net> (raw)
In-Reply-To: <2d5a2c100705282058o22ace961y93308be3340bb2d4@mail.gmail.com>

On Tue, 2007-05-29 at 00:58 -0300, Luiz Augusto von Dentz wrote:
> I consider this as a wizard for printers, like in NetwokManager the
> network wizard also
> does start a discovery and it work like a charm but in my opinion it
> doesnt belong to bluez utils.

It's a standard feature of cups backends. If they support it, they
should list the accessible/known printers in the vicinity.

> Having each wizard to rely in its own discovery is probably a bad
> design, we can probably integrate 
> all wizard together and then having services configuring them in the
> background. This way we
> could leave to the user to use periodic scan and popup specific device
> wizard dependent on
> each service when active. Also in my opinion it should exist a printer
> service for those that want to 
> configure its devices that are not in discoverable mode.

True, it would be much better. But in the meanwhile, this patch simply
implements a CUPS feature and allows us to have some basic integration
in the distribution-provided printer tools.

Being able to configure the printer via a bluetooth configuration wizard
requires a bit more work, but it's also on my plans. There should be a
CUPS service that would allow hcid to add/remove bluetooth printers from
cups with minimum user interaction.

> Btw, The printer wizard as it is now wont work with periodic
> discovery, signals DiscoveryStarted and
> DiscoveryCompleted are not emitted while in periodic  discovery. 

The cups backend isn't supposed to run forever, so it can't do periodic
discovery.

-- 
Bastien Nocera <hadess@hadess.net> 


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-05-29 10:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 15:24 [Bluez-devel] CUPS plugin discovery bits Bastien Nocera
2007-05-23 15:51 ` Marcel Holtmann
2007-05-23 15:57   ` Tim Waugh
2007-05-23 16:15   ` Bastien Nocera
2007-05-23 16:26     ` Bastien Nocera
2007-05-23 16:56       ` Johan Hedberg
2007-05-23 17:07         ` Bastien Nocera
2007-05-24 13:39         ` Bastien Nocera
2007-05-24 15:31           ` Johan Hedberg
2007-05-24 18:49             ` Bastien Nocera
2007-05-25 12:30               ` Bastien Nocera
2007-05-25 12:58                 ` Bastien Nocera
2007-05-25 15:08                   ` Bastien Nocera
2007-05-29  3:58                     ` Luiz Augusto von Dentz
2007-05-29 10:26                       ` Bastien Nocera [this message]
2007-05-29 13:18                         ` Luiz Augusto von Dentz
2007-05-29 13:37                           ` Marcel Holtmann
2007-06-07 10:21                     ` Marcel Holtmann
2007-06-07 12:59                       ` Bastien Nocera
2007-05-24 15:03   ` Bastien Nocera
2007-05-24 15:20     ` Marcel Holtmann

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=1180434383.3030.70.camel@cookie.hadess.net \
    --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