foobar2000 v0.9.5.3 beta 2
Reply #29 – 2008-05-13 19:47:43
One more thought about SDK license violation incidents: After having watched this forum for over 5 years, as well as observed behaviors of component developers, it seems to me that the main problem here is lack of communication between different developers. People prefer writing hacks to get the functionality they need over asking other developers to provide legit means to implement that functionality. Even if those hacks rely on quirks of someone else's code and generate dozens of tech support posts when they fail miserably with the next foobar2000 release or changes in other components that they depend on. Some examples:X-Fixer menu hooking incident - early 2003 or so - proper APIs to create your own arbitrary main menu commands were introduced a few versions later, nobody ever tried to hack that again. foo_dockable_panels - cwbowron could have asked UI developers to create some kind of API to dispatch whatever main window events he needs to process, but nooo, hooking the window is so much more "leet" than asking another person for help. An API similar to what is needed there already exists in 0.9.5+ but it's private to the new Default UI, I don't want to publish it until I know how exactly people want to use it so I don't have to create multiple incompatible revisions later. foo_dsp_crossfader - I guess we'll never know what it was that output APIs were used for, I certainly don't remember getting any feature requests about that. foo_albumlist_autoupdate - No longer relevant as the new Album List version updates by itself.