Re: [Bluez-devel] Suggesting bluez_pinhelper

Gilboa Davara
2007-05-27T17:28:04Z

Marcel,

>
> take this up with the KDE Bluetooth guys since it the Bluetooth support
> for KDE 3.x got basically abandoned. It is their job to actually fix it
> and provide whatever they need to make Bluetooth working.

It's their prerogative to spend their efforts on their up-coming KDE4
port.
While I know that SUSE had created a semi-working (at least by my
experience) dbus support, I rather not p*ck around with it, as I have
little experience with QT (and I don't really like CPP) and I'll zero
ability to fix it, if-and-when-things break.

Once it's official, (or once the SUSE patch works for me...) I'll be the
first man to drop this hack.

> 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?

> The passkey-agent.c source code is mainly
> an example on how to write a passkey agent and was used for initial
> testing.

... 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.

- Gilboa