From: Martin Stolle <mstoll@sus.mcgill.ca>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] help with Logitech Travel Mouse
Date: Wed, 26 Sep 2007 10:05:08 -0400 [thread overview]
Message-ID: <20070926140507.GA5913@sus.mcgill.ca> (raw)
In-Reply-To: <20070926113035.GC8781@suse.de>
On Wed, Sep 26, 2007 at 01:30:35PM +0200, Stefan Seyfried wrote:
> On Tue, Sep 25, 2007 at 08:34:41AM -0400, Martin Stolle wrote:
>
> > The other problem is - what about people who don't use gnome or kde? I
> > always thought Linux was about choice. Clearly, if I want to use
> > bluetooth, I am forced to use one of these desktop systems with their
> > desktops, wms etc..., which is quite restrictive. That is quite a step
> > back from the "hidd --search" way of doing things!
> >
> > (Now, I am not saying that hidd --search should be the only way -
> > definitely not. Gnome and KDE integratino are really important. But
> > please not at the expense of simple command-line tools!)
>
> Just go ahead and write them. Take those python scripts as a base and write
> some nice ncurses-based inputwizard. Or maybe XLib-based or whatever. Lots
> of people are complaining that "there is no way to do it on the command line"
> but the only people providing code are the desktop people.
Unfortunately, I am not a "desktop" person or "command-line" person. I
am a user. A significant amount of people earn their living writing
Gnome/KDE tools. Thats, IMHO, why they provide code faster. I don't
think I have the time and resources to promise that I will write and
maintain tools that the bluez-team decided were no longer necessary.
It's a shame. I guess it's bound to happen - the more successful Linux
gets, the more it's gonna be like Windows. Less choice, more
clicky-clicky! I still don't quite understand the decision to drop
support for command-line tools, but I am not entitled to judge the
bluez-developers. I can only express my frustration.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-09-26 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:13 [Bluez-users] help with Logitech Travel Mouse Jared Greenwald
2007-09-24 19:22 ` Martin Stolle
2007-09-24 19:33 ` Jared Greenwald
2007-09-24 22:14 ` Marcel Holtmann
2007-09-24 22:21 ` Martin Stolle
2007-09-24 23:12 ` Marcel Holtmann
2007-09-24 23:21 ` Martin Stolle
2007-09-25 11:50 ` Jared Greenwald
2007-09-25 12:24 ` Claudio Takahasi
2007-09-25 12:34 ` Martin Stolle
2007-09-26 11:30 ` Stefan Seyfried
2007-09-26 14:05 ` Martin Stolle [this message]
2007-09-26 22:06 ` Marcel Holtmann
2007-09-26 22:18 ` Martin Stolle
2007-09-27 7:39 ` Marcel Holtmann
2007-09-27 13:42 ` Martin Stolle
2007-09-27 23:08 ` Marcel Holtmann
2007-09-25 12:41 ` Jared Greenwald
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=20070926140507.GA5913@sus.mcgill.ca \
--to=mstoll@sus.mcgill.ca \
--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