 |
|  |
 |
|
LDiCesare
|
|
La Ferté sous Jouarre France
Jan 2001 time: 05:31
|
|
I don't plan to actually work on the CtP2 code. (I'm too busy with Clash and don't want to let this project down).
But I DO want to look at the code, maybe make some comments, and generally follow what's being done here. (I also don't want to buy MSVC++, I already hate working with it at work, so not at home if I can avoid it).
Now, how will I be able to follow the mess that this forum will soon become when everyone asks stuff about the function m_cxSchmoofoobar() in class ctpMrOgPyaJBytwrnemdByLcts?
What about making a sticky thread by package (I call package the source directories), where vital information about each package would be kept and discussed? When a post limit of (something) is reached, the information should be digested somehow, the thread unstickied and a new one put in place instead?
Of course, I am not proposing myself to do the nasty work of organising things up, just suggesting someone else do it for my own convenience.
This could help, however. Particularly, I want to peek and maybe comment a few ai and mapgen files. There are silly stuff, but having dedicated threads per topic might help a bit, and the source is already organised in folders so it looks like a convenient way to organise our posts here. What do you think?
|
|
|  |
 |
|
MrBaggins
|
|
I've documented new original (database front end) code. Pretty straightforward, since we were going from a full design, and referencing to within those documents.
The CTP2 code is a different beast. Somethings are straightforward. Other things, are not.
I don't feel that we are going to have the degree of familiarity with the code, and why what goes where, and at what points changes can be made, until a while.
To a certain degree we are gaining familiarity through hacking the obvious bugs away.
As far as the code itself, its not *terribly* untidy. I can do bug hunting without code documents, and I think Dale and John feel similarly.
At some point, we'll have the kind of familiarity to start to write some documents. We can certainly comment the bits we are fixing.
Last edited by MrBaggins on 04-11-2003 at 01:14
|
|
|  |
 |
|
MrBaggins
|
|
No problem, Dale. Where do you want it?
|
|
|  |
 |
|
MrBaggins
|
|
Sure. It is, btw, DirectX Media 6.0 SDK, not 7.
|
|
|  |
 |
|
MrBaggins
|
|
Thanks Locutus, much appretiated. I'll take it down after I know Dale has it. Perhaps we'll set up an "official" appropriate dial-up viable DirectMedia package when we have some sort of source repository going.
|
|
|  |
 |
|
MrBaggins
|
|
You've got to put your foot down Dale, and tell her who's boss... *chuckles*
|
|
|  |
All times are GMT. The time now is 05:31. Apolyton Time is 00:31. |
top of page
|
|
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|