QUOTE((\/)(\/) @ Jun 16 2003 - 01:46 AM)
Before I venture into that, it would be great to know the design philosphy behind FB2K. I have read a lot of the General forum postings and though I have come across things that the developer hates, I am not very sure what is his definition of good/useful. I know that asking for Win 9x support is considered sacrilege and that ID3v2 is considered evil.

So far I have found that the prefence is for non-gui related feature requests and there is usually no beta-tests (expect for build 6.0).
Anything else we newbies need to know before we dare to contribute?
Win9x versions exist, no? Peter didn't want them at first because he figured it would be a big hack to get Unicode working properly. Eventually, he figured out a way to ditch unicode altogether in the 9x builds.
Peter isn't the only one who considers ID3v2 a bad thing. Do a search or two on Hydrogen Audio for more reasons why.
There are no GUI features that foobar lacks, per se. I don't think the main interface will change at all, other than becoming replaceable.
There are many beta tests, they're just not advertised on the forum.
@All:
If you want to aid development and can code, code good, interesting plugins. The fb2k architecture is broad and versatile enough that you can do many interesting things with it.
Present plug-in ideas of mine:
Extending foo_history to allow for true shuffle play. The idea is that the entire playlist is randomized, then set as items-to-be-played in the history. Probably somewhat difficult, should involve getting permission from foosion first.

Simple component for controlling Windows Mixer volume via Foobar. Probably really easy.
An input plugin similar to CUE files, but able to properly store metadata, and possibly seek times/positions as well for slow-seeking formats. (Aside: I've noticed faster seeking in MPC/CUEs lately. Is foobar caching the seek positions or something?)