From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco website problems
Date: Sun, 16 Jan 2005 08:13:07 -0700 [thread overview]
Message-ID: <41EA8483.8080600@xmission.com> (raw)
In-Reply-To: <41EAA3A4.4040509@dark-reality.de>
yeah, i've been thinking it needs work. i'll go push it together with
your outline.
Lars Grunewaldt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
>
> I just took a look at our website to find out why some people have setup
> problems like using the btsco for a2dp and stuff. Don't get me wrong,
> it's great that we have a page and the content is not that bad ->
> credits to the writer :)
>
> I think the problem is that the sections are not very well-named on the
> web page, so one does not know what section describes what part of the
> project (hs or a2dsp profile).
>
> Right now we have:
>
> *introduction
> Stereo Streaming!
> Alsa userspace plugin
> Build
> Discussion
> Credits
>
> with no more info in the headlines. If I - as a btsco n00b - would come
> to the site I would think that
>
> stereo streaming -> alsa -> build
>
> are all about the same topic, making the stereo streaming work.
>
> I think things would be much easier if the headlines of the sections
> would be a little more descriptive, also it might be usefull to re-order
> them.
>
> I'd propose:
>
> *introduction
> ~ (hello world, supported headsets - pretty much like the current version)
>
> Features
> (here we describe what parts of btsco handle what part of features and a
> bit of the technical background)
> ~ * HS profile description ("Headset support")
> ~ * a2dp description ("Stereo sound")
>
> Download
> ~ proper link into the download section and to CVS (do we have nightly
> tarballs, by the way? I think SF builds those for us, and puts them
> somewhere?)
>
> Installation
> (with remarks "building this is only for hs or a2dp" or alike)
> ~ * build process
> ~ * build provess for alsa kernel module (headset profile)
> ~ * build process for a2dp (if this is different)
>
> Usage
> ~ * hs profile, daemon
> ~ * a2dp examples
>
> If we use this structure, anyone should be able to distinguish between
> headset and stereo stuff.
>
> Too bad I don't have time right now :(
>
> If no one else as a little bit of time to write this together, it will
> have to wait until I do. I won't mind to do it, though :)
>
> best regards,
> ~ Lars
>
>
> - --
> Lars Grunewaldt
> * software development
> * multimedia design
> skills: C/C++/Java/PHP/(X)HTML/Flash/audio/video
> web: http://www.dark-reality.de
> mail: lgw@dark-reality.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFB6qOkQWC6DTWkDAoRAr5xAJ4qILrefqnDFluLsdte/N9c6Yu5WgCeLmwU
> 878FORnXs7u5k0hfmIoZuBA=
> =eYzF
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-01-16 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 17:25 [Bluez-devel] btsco website problems Lars Grunewaldt
2005-01-16 15:13 ` Brad Midgley [this message]
2005-01-16 16:54 ` Lars Grunewaldt
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=41EA8483.8080600@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@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