Linux bluetooth development
 help / color / mirror / Atom feed
From: "Gilboa Davara" <gilboad@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper
Date: Sun, 27 May 2007 21:35:04 +0300	[thread overview]
Message-ID: <9050516b0705271135v6deebe42s5e822fcae630b0ac@mail.gmail.com> (raw)
In-Reply-To: <1180289071.21432.76.camel@aeonflux.holtmann.net>

Marcel,

On 5/27/07, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Gilboa,
>
> > > I am not
> > > really open for crazy hacks.
> >
> > Why crazy hack?
> >
> > kdebluetooth aside, If -I- (being, among others, the IceWM Fedora
> > maintainer) can use this wrapper (coupled with zenity and/or xdialog)
> > and create a workable out-of-the-box bluetooth experience on IceWM
> > (without the bluez-gnome dep-chain) and other low-end WM's - doesn't it
> > enhance the user experience?
>
> I agree that the bluez-gnome dependency chain is crazy, but that is a
> GNOME issue. However you can write a simple nice passkey agent for every
> windowing system that you wanna use. The scripting part is not a clean
> solution. We should have never used scripts for entering pin codes at
> all, but at that point of time any useful solution was not ready.

OK.
I can't say that I agree (IMHO having bash/scripting support for
right-about-everything is major feature in Linux/Unix - not a
drawback), but I accept the fact the being the upstream-man, you get
to choose what goes in and what doesn't - and this code doesn't.

> > ... And hopefully I took it, expanded it, and put it to good use.
> >
> > At best, I managed to enhance the bluetooth experience on
> > low-end/older/minimal distro/machines/configuration/etc. At worst,
> > (after some clean up) I created yet-another-how-to-do-passkey example.
> >
> > Having said all that, I'm far from forcing the issue down your throat...
> > I merely suggesting. If you don't like the idea, I'll keep it
> > Fedora-only, until a working DBUS patch is released... or until KDE4
> > comes out.
>
> I am fine with having something KDE specific since I don't really care
> about KDE, but this is not solution that is acceptable by Bluez
> upstream.

Just for the sake of the archives, this wrapper is completely generic - it has
nothing KDE (or kdebluetooth) specific in it.

... But as I said, you're the boss...

- Gilboa

-------------------------------------------------------------------------
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-27 18:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-27 13:52 [Bluez-devel] Suggesting bluez_pinhelper Gilboa Davara
2007-05-27 16:36 ` Marcel Holtmann
2007-05-27 17:28   ` Gilboa Davara
2007-05-27 18:04     ` Marcel Holtmann
2007-05-27 18:35       ` Gilboa Davara [this message]
2007-05-28  8:29         ` Marcel Holtmann
2007-05-27 16:59 ` Petteri Räty
2007-05-27 17:31   ` Gilboa Davara
2007-05-27 17:48     ` Petteri Räty
2007-05-27 18:41       ` Gilboa Davara
2007-05-29 11:27         ` Stefan Seyfried
2007-05-29 12:45           ` Gilboa Davara
2007-05-27 23:19 ` Daniel Gollub
2007-05-27 23:39   ` Denis KENZIOR
2007-05-28 16:48     ` Daniel Gollub
2007-05-28 21:11       ` Denis KENZIOR
2007-05-28 22:21         ` Daniel Gollub
2007-05-28  8:29   ` Marcel Holtmann
2007-05-28 16:53     ` Daniel Gollub
2007-05-29  3:50       ` 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=9050516b0705271135v6deebe42s5e822fcae630b0ac@mail.gmail.com \
    --to=gilboad@gmail.com \
    --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