As I guess from the discussions about panels_ui and the titleformat language, it seems that the developers have rather distinct ideas of how a foobar plugin should work / be written.
While many of these are quite obvious (not creating a giant bug-filled mess, like panels_ui did...), others are not. This is especially true for the more hidden functions foobar offers to assure a consistent behavior across all components (eg. preferences->Appearance->Colors, standard_config_objects::query_show_keyboard_shortcuts_in_menus(), etc.).


In my opinion it's very important for such a large multi-developer, multi-component project to have clear design guidelines. This includes coding guidelines (as there are some given in the SDK) as well as interface guidelines (as Peter has given once). This would not only make life easier for the developers and the interface of foobar more consistent -> more fun to use for the user, but could also reduce Peter's dissapoinment with the developed components, I guess.

What do you think? Any chance we'll be getting some of those?

Yes, some. More specifically, I intend to provide more information on how to use the facilities in the SDK (e.g. title formatting) and how to improve integration with the core and other components (does anything besides foo_freedb2 implement an info_lookup_handler*?). However I will put the focus on the foobar2000 SDK. It is beyond out possibilities to educate people on programming in general and in C++ as well as software and user interface design.

*: Yes, that's just the information from the SDK processed by doxygen (except for the main page and the screenshots).

Happy to hear that. Would be great if you would not have to look through the whole SDK to be able to write a good component (to discover stuff like popup_message, that you should use "where possible" - something that's very difficult if you never heard of it - same for threaded_process and quite some more).

Btw. - just an offtopic question. This has been reported before, and I thought I reported that bug once, too - but I can't find the topic. Foobar is lacking support for the UNIQUEFILEID (UFID) id3v2 frame. While it may seem to be just another unused id3v2 frame, it's rather important since MusicBrainz uses it to store its file IDs in. Has this been fixed yet, or is this planned be fixed anytime?