From: "Joël Krähemann" <joel@weedlight.ch>
To: Carl Canuck <carl.canuck.official@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Documentation Request
Date: Wed, 04 Sep 2013 17:21:01 +0000 [thread overview]
Message-ID: <1378315261.17166.7.camel@debianWEED> (raw)
In-Reply-To: <CAPOzVs7vNnaRpnH_-k2yxVBb09LoAovADSkzZiXNVTQYMO9R+Q@mail.gmail.com>
Hi
Assumed it's really an open source project why not looking at code from
other projects. There are many applications that do midi e.g. lmms,
rosegarden and probably many more.
http://code.ohloh.net and http://www.codase.com is providing good code
search engines.
So let me help you. Pick a function you're interested in and just copy
it to the search field.
And don't get being disappointed of frustrated open source developers.
have a nice day
Joël
On Wed, 2013-09-04 at 10:30 -0400, Carl Canuck wrote:
> Continue the conversation if you choose, but I am searching for the
> unsubscribe button as we speak.
>
> I have no incentive to port anything to Linux other than some general
> feelings of goodwill towards the open source community. If you truly feel
> that writing a kludgy API with poor documentation and example code that's
> only meant to be wrapped into other APIs developed by those brave souls
> willing to take the time to reverse engineer it all is good business, then
> by all means keep on doing what you're doing. It is my personal
> conviction that I would much rather retain full control of my application
> by communicating directly with ALSA rather than delegating control to Jack
> just to ease the pain of deciphering your poor documentation.
>
> I am truly sorry for taking time away from your driver development, please
> continue with your work and let this conversation die in peace, I will not
> be participating in this conversation or your mailing list any further.
>
>
> On Wed, Sep 4, 2013 at 10:05 AM, Clemens Ladisch <clemens@ladisch.de> wrote:
>
> > Carl Canuck wrote:
> > > if the attitude of the ALSA community is
> >
> > There is no individual that has the power to speak for the community.
> >
> >
> > Regards,
> > Clemens
> > _______________________________________________
> > Alsa-devel mailing list
> > Alsa-devel@alsa-project.org
> > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2013-09-04 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 0:32 Documentation Request Carl Canuck
2013-09-04 0:58 ` Eliot Blennerhassett
2013-09-04 1:45 ` Carl Canuck
[not found] ` <CACckToUBiwJg1TUMuw3eFws_rvf9qc3ZPfSzy7MRCB8b0JEnRg@mail.gmail.com>
[not found] ` <CAPOzVs4+Sd=UXZ3gMGSNwMk1EW_yKPK+7dTo_vuWD_acyrWw6g@mail.gmail.com>
2013-09-04 3:15 ` Carl Canuck
2013-09-04 6:04 ` Felix Homann
2013-09-04 7:58 ` Clemens Ladisch
2013-09-04 8:18 ` Florian Faber
2013-09-04 13:20 ` Carl Canuck
2013-09-04 14:04 ` Felix Homann
2013-09-04 14:05 ` Clemens Ladisch
2013-09-04 14:30 ` Carl Canuck
2013-09-04 17:21 ` Joël Krähemann [this message]
2013-09-05 12:13 ` Keith A. Milner
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=1378315261.17166.7.camel@debianWEED \
--to=joel@weedlight.ch \
--cc=alsa-devel@alsa-project.org \
--cc=carl.canuck.official@gmail.com \
/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