GuyHoozdis

Yes, I will have fun! Thank you, sir.

Wie Gehts, floele! Thanks for getting back to me. Yes, I did see the CDBurnerXP folder. At first I was only looking at it through the "Solution Explorer" window in VS2008; the *.cs files are not seen from that perspective, not even when I tried to add them. The directory looked empty. Obviously, I made a mistake somewhere there and should have looked a little bit harder. Still, I would say that there is room for me to help you guys and make it dead-simple to build process for the Ketarin source that you provide. That could be as simple as just writing a "how to" for you guys, but I'm totally cool with getting my hands dirty in the code. If you already have a roadmap for Ketarin or just thoughts on how/what you want to do with it, then let me know and I'll follow your lead. If you would like me to take the lead and suggest to you what the roadmap could be, just say the word and I will do that for you. As for my current progress building the source... There appears to still be one file missing; "IMirrorControl.cs". The IDE expects that file to be located: "CDBurnerXP\trunk\CsLib\CDBurnerXP\Controls\IMirrorControl.cs" along with the other logic that I did find in the CDBurnerXP folder came with the *.tar.gz I downloaded from your site. As a first attempt to get to a successful build, I reconstructed the expected directory structure using "junction points". I'm trying to model what the "real" build scenario looks like and get a successful build before I go changing too much. Beyond the simple "just write a how-to-build-ketarin" guild that I mentioned, I think the next easiest and lease invasive solution would be to automate what I did manually. That is, create a step in the build process that ensures either: 1) the real CDBurnerXP project has been checked out (as would be the case for developers with access to the CDBurner project) ... or ... 2) Creates a simple skeleton structure that imitates what the "real" directory structure so that the build process "thinks" it is there. That would be fairly simple to do. The longer and more involved solution, and in my opinion also the "right" or "proper" solution, would be to decouple the shared logic that exists between the two projects and package or provide it as its own component so that both CDBurner and Ketarin could use the logic w/o duplicating source files. If this is what you are thinking then we would need to plan a little bit before I started, but the outcome might be something like: 1) CDBurner Source - private/restricted access as it is today 2) Ketarin Source - public/open-source as it is today 3) SharedLib - a new component made up of the existing logic that both projects use; public/open-source * If you aren't familiar with "junction points" see junction.exe from SysInternals to quickly and easiliy make your own.

Thank you, Shawn. Is there someone that is actively in charge of maintaining the Ketarin source? I would like to help. Who should I talk to? I found the project listed on Ohloh and I am currently trying to integrate myself into the project there for starters. Are you aware that the Ketarin source that is distributed is not in a build-able state? As an outsider I do not have access to the CDBurnerXP source tree, and the Ketarin source code references some sources files in the CDBurnerXP source tree. I don't really want access to the CDBurner source tree, but I would like to clean up the Ketarin source tree so that it will build nice and easily for the next person. I can give details to whom ever needs to hear them, but the short story is that I went through the Ketarin source and cleaned out the references to source files that live under the CDBurnerXP project. I know Ketarin was only created, quick and dirty, to supply basic functionality for CDBurnerXP. The fact is though, Ketarin itself has gathered a cult following and deserves some proper attention. Like I said, I'll volunteer for that task. At the moment I am going through and re-implementing the functionality that is normally supplied by the handful of source files that reside under the CDBurner project. I looked around briefly, but would you confirm that the CDBurner source tree is not available for me to access? I'm starting down the path of re-implementing the logic already. If you, or the developer in charge, wants to make my life easier; I'm open to that. If the maintainer wants to remain as the lead and have me follow suit with the way they have planned for the project-- no problem. If there is no one responsible for it-- then I'm stepping up. If the maintainer of developer wants to save me the work, and the development faux paux, of duplicating the logic that Ketarin is missing; I can specify the source files that are missing and someone with access can pass me just those files. Thanks again, Shawn.

I downloaded the Ketarin source from the link provided on the website's mainpage (it's in the second paragraph under the "What's it all About" heading). After extracting the C# source files I open the project/solution in VS2008, clean, and rebuild. I get an error message immediately that I don't have the source code for CDBurnerXP which the project is expecting to find at "..\CDBurnerXP\trunk\...". I wanted to see if anybody else had some input on this before I dig in to the project's configuration files and start changing things. Is there a dependency on CDBurnerXP for Ketarin that I am noobishly not aware yet? I see that Ketarin was, in fact, created as a compliment to that app, but it's just Ketarin that I'm interested in. I've never used Ketarin before, but have been dying to employ it's awesomeness to bring some sanity back into the management of the myriad of Windows tools and utilities that I am otherwise constantly re-downloading and maintaining. I'm really looking forward to this! I came across Ketarin being used in someone else's project a while ago; that's how I came to be aware it's existence. I've read over the docs, the examples, external pad file references, and some community templates/scripts. I downloaded the binaries and source and am ready to dig in! I have run the pre-compiled binaries in a virtual machine before, but I would prefer to build the application from source myself from now on. From the path that is configured for CDBurnerXP, it appears that you guys have a code repository somewhere. Subversion maybe? Perforce or... what is M$ proprietary source control called? How do you feel about github? The license for Ketarin clearly would allow me to take setting up a public github repo, but I'd like to ask if that would offend the developers or maintainers? Maybe you guys already have a "system" and I should figure out how I might fit into what you have going on already. Any input on compiling the source, correcting me if I have any misunderstandings about Ketarin requirements, or the desire to have the source reviewed/QA'd/hosted in a public repo.... any comments or insight would be helpful. Thank you.