This is a multi-part message in MIME format. -- [ Picked text/plain from multipart/alternative ]
Well, to not put large portions of Valves code into the public and not have to deal with all the diffs you would have to rewrite most if not all of the SDK. Like I said the downside is that is a lot of work. The positive side is that the users don't have to diff anything and you get lots of experience. It might work better for a while to do diffs so that multiple people can work together to rewrite it. Overtime more code can be included in the diff until it is all rewriten. Then it can all be released. Of course in theory. - Nate ----- Original Message ----- From: Nikolaos Tzimoulis<mailto:[EMAIL PROTECTED]> To: [email protected]<mailto:[email protected]> Sent: Saturday, February 03, 2007 2:00 AM Subject: Re: [hlcoders] Re: Open Source Mods (again) What do you mean "so that it is all modified", Nate? And now that I think about it, it's not an option to start from a specific version of the SDK and diff that. How would everyone coordinate with that since you don't get to choose which version of the SDK Steam downloads? Also, it wouldn't be in accordance to Valve's policy of not having large portions of their code public. I don't see a way of not having to redo the patches every time an update comes out for the SDK. If the code management utility (like CVS) saves projects in a diff way, then I guess that would be a viable option. The online project could consist of CVS project files, and if one were to apply it to the latest SDK he would get the mod's code. Is that possible? Nicholas _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders<http://list.valvesoftware.com/mailman/listinfo/hlcoders> -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
