Because there appear to be problems with extending the FrameFactory, an
approach similar to the FileTypeResolver code could be added to the
FrameFactory so support for new frame types could be inserted into the
default instance.<br>
<br>
-Brian<br><br><div><span class="gmail_quote">On 7/19/06, <b class="gmail_sendername">Scott Wheeler</b> <<a href="mailto:wheeler@kde.org">wheeler@kde.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Heya folks --<br><br>As mentioned, I want to do a 1.5 release relatively soon and as of today my<br>internet connection is back. I've been looking over the mailing list<br>archives trying to put together a TODO list of issues to look at before a
<br>release. Since it's been a while since the last release, I'm sure that I've<br>missed some. Here are the topics that I've currently flagged:<br><br>- package config file for c bindings only?<br>- [patch] tbytevector::find() bug with unicode?
<br>- WavPack<br>- Re: [taglib] lyrics support<br>- Speex tag support in taglib<br>- Re: Weird genre problem with taglib<br>- Calculation of MPEG frame length is wrong<br>- GEOB frames (was Re: extending taglib (ID3v2 frames))
<br>- Re: Odd APIC frame<br>- wrong TDAT conversion<br><br>Additionally there's the topic of the Windows port which has about a dozen<br>threads. I'll send a follow up mail on that topic in just a minute. (I just<br>want to keep the threads separate.)
<br><br>- If I missed your issue in the list above, please respond in this thread<br><br>- If you reported a bug, whether it's in the list above or not, please put it<br>in the bug tracking system. It's somewhat more reliable than my brain.
<br><br>- If you sent a patch to support a new format I'd like to (in this thread)<br>hear what you've done in terms of testing (especially writing). Make sure<br>that files still playback. If there's a tool for reporting info for your
<br>format (i.e. ogginfo) please test with that. Also consider doing a<br>byte-for-byte comparison with reference implementations. People naturally<br>get pissed off when their files get corrupted. (And for that reason some of
<br>the new format stuff may not make it into 1.5 if I'm not fairly convinced<br>that it's ready.)<br><br>- There are a lot of bindings for TagLib now. Some of them (i.e. Dong Xu's<br>for Perl) probably get more visibility in the current place (in this case
<br>CPAN) than they would being distributed with TagLib. However, I'm willing to<br>consider distributing additional bindings with the library. If you're<br>interested in getting your bindings in please respond here too. Languages
<br>that I'm not very comfortable in (Ok, so that mostly means everything that's<br>not C, C++ or Perl, so almost all of the new bindings.) I'd like to ask other<br>developers that are comfortable in those languages to review the APIs before
<br>inclusion in TagLib. If it's your first API to write in that language, say<br>so. Also keep future compatibility in mind. You're stuck with any included<br>APIs until TagLib 2.0.<br><br>- Don't post feature requests without code (in this thread).
<br><br>Thanks people!<br><br>-Scott<br><br>--<br>Many people would sooner die than think; in fact, they do so.<br>--Bertrand Russell<br>_______________________________________________<br>taglib-devel mailing list<br><a href="mailto:taglib-devel@kde.org">
taglib-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/taglib-devel">https://mail.kde.org/mailman/listinfo/taglib-devel</a><br></blockquote></div><br>