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 11:02:58 +0200	[thread overview]
Message-ID: <1186736578.20129.202.camel@violet> (raw)
In-Reply-To: <fb2ac3c90708092110y3a4ffff1ka8d5ea1ebdd17e32@mail.gmail.com>

Hi Andrew,

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

> Another problem with this approach is that it creates a dependency on
> gnome-vfs-obexftp and assumes that it's present.  If it's desirable to
> have the applet launch other programs it should support more than
> obex:// and there should be some generic mechanism for programs to
> plug themselves in as handling a given service.  It should be possible
> some day to get a bluetooth mouse working from the GUI, or a bluetooth
> headset, for example.

It only supports Bluetooth FTP and is not meant to support everything.
So I have no idea what you are talking about. Use the preferences dialog
or the upcoming wizard to connect other type of Bluetooth devices.

> Of course there needs to be better integration of gnome-vfs-obexftp,
> but that integration should be in nautilus where everything else
> vfs-related is found.  A bluetooth link under computer:/// when an
> adapter is present would be sufficient (though I wish we'd treat OBEX
> more generically as well - it's got 3 or 4 transports besides
> bluetooth).

We know that OBEX supports more than the Bluetooth transport, but which
of these transports actually have devices that support FTP like
transactions. Most of them only allow to push or pull a file. However
feel free to fix gnome-vfs-obexftp to make this work.

If you wanna have the Bluetooth adapters (yes, plural. We can have more
than one) under computer:/// then go ahead a send patches upstream. I
personally don't care and I am not responsible for that part of
software.

As usual with these kind of things, I am not the UI expert and if you
wanna have fixed or changed something, you better send in a patch. We
always welcome new development blood.

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  9:02 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 [this message]
2007-08-10 12:45   ` Timothy Murphy
2007-08-10 13:04     ` Marcel Holtmann
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=1186736578.20129.202.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