<div dir="ltr">On Thu, Aug 7, 2008 at 6:53 PM, Tim Starling <span dir="ltr"><<a href="mailto:tstarling@wikimedia.org">tstarling@wikimedia.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">DirectShow and QuickTime can add those interfaces at a later date. When<br></div>
the backends develop this capability, there should be a standard way to<br>
go the next step and expose it to JavaScript. Otherwise every<br>
implementor will develop their own interface.</blockquote><div><br>Sure. But the interface has to be able to say "I don't know". And then we're relying on authors to do the right thing if they get that answer ... which is always a worry.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">In fact, QuickTime already has enough query capabilities for Wikimedia's<br>
purposes.</blockquote><div> </div></div>Probing for a particular component is a different problem from listing all supported codecs, which is what I thought you were asking for. I suppose we could hardcode a list of well-known components along with the codecs they support and then probe for them to estimate what codecs are supported. But, yuck.<br clear="all">
<br>Rob<br>-- <br>"He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]<br>
</div>