public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluetooth-applet and gnome-vfs-obexftp
Date: Fri, 10 Aug 2007 15:04:07 +0200	[thread overview]
Message-ID: <1186751047.20129.213.camel@violet> (raw)
In-Reply-To: <f9hmm2$e7i$1@sea.gmane.org>

Hi Timothy,

> >> Version 0.10 of bluez-gnome added support for "browsing devices" - a
> >> much needed feature by any account.  What I'm not thrilled about is
> >> that it was written to support gnome-vfs-obexftp.
> >> 
> >> Don't get me wrong - gnome-vfs-obexftp is awesome, but
> >> bluetooth-applet is the wrong entry point for it.  The applet should
> >> allow you to see what devices are around you and allow you to initiate
> >> a bonding with them but the assumption that you want to browse OBEX is
> >> bad.
> > 
> > it is exactly the right entry point. You might wanna compare how MacOS X
> > handles it. The actual bonding will be done automatically. You are the
> > client and so we can rely on the actual FTP server to ask for a bonding
> > and not wasting time to try to pair a public FTP repository that has no
> > key anyway.
> 
> What I find odd is that it suggests bluez is somehow connected to gnome.
> As a KDE user I find it strange that I have to use a gnome application.
> This doesn't offend me, but I assumed - wrongly as it happened -
> that installing bluez-gnome would require 
> a whole slew of gnome applications.

actually the name is a little bit misleading when it comes to the
dependencies since bluez-gnome only depends on GTK and D-Bus. However
the intention is to provide UI applications for the GNOME desktop. It
doesn't link against the GNOME libraries, because I am not mad ;)

> As far as I can see, one has to have bluez-gnome just to establish pairing.
> Is that right?

That is wrong. Every desktop framework can have its own UI. The
bluez-gnome provides stuff for GNOME and kdebluetooth provides this for
KDE. They all communicate over D-Bus.

> I don't understand why you can't just put the code in a file.

Because pairing is global and the security implications of a file based
approach are too complicated.

Regards

Marcel



-------------------------------------------------------------------------
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-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-08-10 13:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  4:10 [Bluez-users] bluetooth-applet and gnome-vfs-obexftp Andrew Jorgensen
2007-08-10  9:02 ` Marcel Holtmann
2007-08-10 12:45   ` Timothy Murphy
2007-08-10 13:04     ` Marcel Holtmann [this message]
2007-08-10 14:22       ` Timothy Murphy
2007-08-10 13:13   ` umamahesh yelchuru venkata
2007-08-11 18:05     ` Marcel Holtmann
2007-08-10 17:01   ` Andrew Jorgensen
2007-08-10 17:30     ` Andrew Jorgensen
2007-08-11 18:04       ` Marcel Holtmann
2007-08-11 22:32         ` Andrew Jorgensen
2007-08-10 17:47     ` 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=1186751047.20129.213.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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