Renegade
20.06.2010, 00:48:09
Easiest way to start is either a) looking into bug reports for existing Ares code, since you probably won't need new stuff for that, or b) using the "No ASM required" filter, which pulls up all issues for which the necessary ground work has already been laid, and that just need the actual C++ implementation written.
Check out the source, do your modifications, have svn generate a .patch file, attach that .patch file to the issue in question.
Someone will look at the code and either request changes or apply the patch.
For general information, you can have a look at the auto-generated API reference coming with the source, but "the old guard" isn't big on commenting...so it's mostly bare-bones technical information, save for some newer Ares functions written by Alex and me.
Also, actually staying in IRC for communication purposes helps.
P.S.: The UI and event management functions are buried in a mess of ASM anyway, and you usually work with plain functions and inside hooks, so the lack of GUI app experience shouldn't be an issue.
Check out the source, do your modifications, have svn generate a .patch file, attach that .patch file to the issue in question.
Someone will look at the code and either request changes or apply the patch.
For general information, you can have a look at the auto-generated API reference coming with the source, but "the old guard" isn't big on commenting...so it's mostly bare-bones technical information, save for some newer Ares functions written by Alex and me.
Also, actually staying in IRC for communication purposes helps.
P.S.: The UI and event management functions are buried in a mess of ASM anyway, and you usually work with plain functions and inside hooks, so the lack of GUI app experience shouldn't be an issue.
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.