Re: alsa-lib plugin devel

[Takashi Iwai <tiwai@suse.de>]

At Mon, 24 Jan 2005 13:08:25 -0700,
Brad Midgley wrote:
> 
> Takashi
> 
> > Agreed, I/O plugin can set itself as the list candidate.
> > 
> > 
> >> In the case of a2dp the option
> >>"type a2dp" should result in asking the plugin if its devices (or maybe
> >>this device) are listed or not. An additional option looks for me like
> >>over-configuration.
> > 
> > 
> > Well, I think it's useful to have this as an option, too.
> > If you have your own favorite configuration, you can add it to the
> > list of supported devices.
> > The attribute should be off as default, of course.
> 
> This sounds great. It's your project, so I shouldn't jump in and do it 
> but let me know if you do want me to get in there. As long as you intend 
> to make this change, it makes the plugin development worthwhile from my 
> perspective. :)
> 
> One question... will the client need to change how they query for 
> devices? How much latitude do you have while keeping the api stable?

It'll be an additional API function.  So, applications will need
rewrite, of course, if they use the new query function.

But I won't change the existing APIs.  This should never happen, at
least, during ALSA 1.0.x.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl