Hi Guys,
I have a question in regards to using your SDK for an application. I am not familar with foobar2000, as I have been sent to your site in search of documentation/advice. These are some questions I would like to know:
1. I looked at the SDK code, can this be used to build the fully executable foobar2000 application, or is this just to write components for foobar?
2. Can I compile the components in the SDK into some kind of DLL's so my application can call those functions and not load the foobar application?
3. Is there any fair amount of documentation on the SDK?
Im not 100% familiar with foobar, so please excuse my lack of intelligent questions.
Please let me know if you have any questions.
Thanks!
Full Version: Pre-Development question.
1. No, the SDK is just for developing components for foobar.
2. I guess you could load a DLL built from the SDK into your own program - I don't really see the point of this though. What are you thinking of doing?
3. The most common answer to this is that the code is its own documentation
, although foosion did write a nice tutorial going through the steps involved in creating a component of your own.
2. I guess you could load a DLL built from the SDK into your own program - I don't really see the point of this though. What are you thinking of doing?
3. The most common answer to this is that the code is its own documentation
, although foosion did write a nice tutorial going through the steps involved in creating a component of your own.
2. It should be possible to build an application that loads fb2k component DLLs (after all, foobar2000.exe does just that). However, the core implements quite a lot of other things besides simply loading the components, which you would have to replicate as well. So unless you have a really, really good reason to do this, I don't think it is justified given the amount of time that would be required.
QUOTE(Phi @ Feb 27 2004, 03:06 AM)
1. No, the SDK is just for developing components for foobar.
2. I guess you could load a DLL built from the SDK into your own program - I don't really see the point of this though. What are you thinking of doing?
3. The most common answer to this is that the code is its own documentation, although foosion did write a nice tutorial going through the steps involved in creating a component of your own.
2. I guess you could load a DLL built from the SDK into your own program - I don't really see the point of this though. What are you thinking of doing?
3. The most common answer to this is that the code is its own documentation
, although foosion did write a nice tutorial going through the steps involved in creating a component of your own. ah ok. To answer your questions:
#2 - We want to basically build our own frontend and use foobar's code since it does things we need, and not have to load foobar. If this is not possible, im sure there are other ways, but I was directed to this site, saw and SDK and figured id ask.
#3 - Even though the code documents itself, we were looking to build something quick, and have some time of documentation to refer back to.
Thx!
QUOTE(foosion @ Feb 27 2004, 08:29 AM)
2. It should be possible to build an application that loads fb2k component DLLs (after all, foobar2000.exe does just that). However, the core implements quite a lot of other things besides simply loading the components, which you would have to replicate as well. So unless you have a really, really good reason to do this, I don't think it is justified given the amount of time that would be required.
Thanks for your reply as well, looks as if this may not be a usable code base for us.
Thanks again!
It may or may not be an option for your project, but the SDK does allow you to replace the default user interface with one of your own. So the user would only be aware of whatever interface you came up with. I know you'd prefer not to load the foobar core, but that is where most of the useful stuff is implemented anyway. 
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.