I think your missing the point of what im trying to do here. I have *zero* intention of writing documentation, well not after the first little bit anyways. Im more creating a tool+repository where documentation is submitted. Plus, with the documentation etc that it submitted being data based, all kindsa funky things can be done to it, namedly it can be searched, compilied into help files compatible with VS, etc. Personally, I think the concept of manually pulling tons of information together and building a CHM file out of it, would be about as exciting as watching paint dry. That said, I dont mind a computer doing it.
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: Re: [hlcoders] Documentation Date: Wed, 26 Jan 2005 19:26:40 +0100
I dunno, I think this sounds like a *very* boring project (come on, who actually LIKES to write documentation?), and I doubt you'd get much help. I too feel the SDK could be more documented but it is not our job (you'd think a large software corp such as Valve was more up-to-date with development techniques...).
I don't mind sharing my findings though, and this is why a wiki-solution is a much better idea IMO.
Ofcourse, if you were to write a 400-page documentation with no misleadings, I wouldn't start crying. :)
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: 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
