public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Holland <ah160@student.cs.york.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] File transfer
Date: Mon, 16 Feb 2004 12:56:04 +0000	[thread overview]
Message-ID: <200402161256.04985.ah160@student.cs.york.ac.uk> (raw)
In-Reply-To: <200402161238.36360.tim@birdsnest.maths.tcd.ie>

On Monday 16 February 2004 12:38, Timothy Murphy wrote:

> Does KDE Bluetooth use Bluez?
> I looked briefly at the kde-bluetooth archive but couldn't see that
> info.

Yup, it depends on a correctly configured Bluez system to actually work.

> Also, is it necessary to use Konqueror (which I don't)?

Nope, you can run the obex stuff seperately. But I like being able to 
browse sdp:// in Konq.

It has kbtobexclient, which searches for phones then lets you send files 
to them, and an obex server running as a daemon, so you can send files 
to your PC at any time and it'll recieve them (with nice thumbnails, 
and an option to choose where to save). The latest CVS versions also 
have a Qt Pin helper, which is certainly preferable to bluepin (which 
never worked for me).

Other fancy functionality includes serial chat, a systray icon to show 
BT activity, bemused XMMS control, and the ability to have your PC go 
into screensaver lock as soon as your phone/PDA goes out of range, then 
unlock on return. Not everything's 100% yet, but it's maturing very 
quickly.

There's talk of irmc sync stuff through Kitchensync, but I got the 
impression that won't be around for a while yet. It would be great to 
abandon Evolution and Multisync, though.

> Sadly, there does not appear to be a Fedora RPM.

There's been a bit of chatter about it on the mailing list. There's 
certainly some instructions out for building from tarballs on Fedora, 
though possibly not on the main page.

> (Nb KdeBT is unknown to google - is it your abbreviation?)

My abbreviation, sorry. http://kde-bluetooth.sourceforge.net/ is the 
main page, but Sourceforge appears to be screwy at the moment.

Alex Holland
Who isn't being paid by the KDE BT team, just really likes their 
software.


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-02-16 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10  9:33 [Bluez-users] File transfer Lalith Chakravarthi
2004-02-16 10:05 ` Thomas Arendsen Hein
2004-02-16 11:04   ` Alex Holland
2004-02-16 12:38     ` Timothy Murphy
2004-02-16 12:56       ` Alex Holland [this message]
2004-02-16 13:16         ` Timothy Murphy
2004-02-16 13:40           ` Thomas Chiverton
     [not found] ` <200402161333.21502.thomas.chiverton@bluefinger.com>
     [not found]   ` <200402161515.37687.tim@birdsnest.maths.tcd.ie>
2004-02-16 15:31     ` Thomas Chiverton

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=200402161256.04985.ah160@student.cs.york.ac.uk \
    --to=ah160@student.cs.york.ac.uk \
    --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