cgewrapper-development — Primarily for developers, mainly discussions about the future of cge.

[Cgewrapper-development] (no subject)

[vegan r. <xsk...@ho...>]

Hey,

I aint heard nothing on here, so I just thought I'd let anyone out there 
know there's at least one person on the list. :)

xEARTHIANx

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

Re: [Cgewrapper-development] Hey

[Ian P. <ipe...@ve...>]

> Hey, Ian you've been pretty quite for the last two weeks or so....how's it
going?
>
> Jacek

    Not bad.. between work and school there isn't much time for programming
though =/  Right now I'm just trying to pass my english course so my parents
won't kill me =]  How have you been?

  - Ian Perez (ipe...@ve...) - "It is by will alone I set my mind
in motion"

[Cgewrapper-development] Hey

[Jacek R. <Bla...@at...>]

Hey, Ian you've been pretty quite for the last two weeks or so....how's =
it going?

Jacek

[Cgewrapper-development] Compiler Problems

[<Bla...@at...>]

I have a problem with my VC++ 6.0 Profesional compiler....getting =
internal compiler errors, Fatal Error C1001, I think I'm going to have =
to uninstall my compiler and reinstall it...I get this error no matter =
what I try to compile, I belive that Windows XP puked on my compiler  =
;o)  This may take me a day or two to resolve.

Update on Input class:  I'm almost done, I'm working on the last part of =
it...the buffered joystick input, immediate input is working for mouse, =
keyboard and joystick and buffered for mouse and keyboard is =
working....so I just gota get buffered joystick input working.

Jacek Ringwelski

Re: [Cgewrapper-development] Coding style

[FireAngel <Fir...@ex...>]

Your right it is limited....I'll see about expanding it....your prefixes and
pre-prefixes are good but I kept mine shorted to make typing it in
easier...I only prefixed pointers and boolean variables.  I'll consider
adding more complexity to it....Thankx for the info.

Jacek Ringwelski

Re: [Cgewrapper-development] Coding style

[Ian P. <ipe...@ve...>]

    *smacks himself on the forehead*  I didn't realize there was
documentation yet =/  Sorry about that.  My SF username is irperez.  I tried
to use CVS once before, but only to check something out (and I had trouble
even with that).  I'm not familiar with it at all.  I'll try to contact you
on ICQ in a bit.

  - Ian Perez (ipe...@ve...) - "It is by will alone I set my mind
in motion"

P.S. Below is the naming convention I use.  Since yours is a bit limited
(pointers, class data members, global vars, and boolean), maybe you could
expand on it a bit with this.

Prefixes:

f          - Boolean flag.  Example: BOOL fEnabled;
ch         - Character.  Example: char chGrade;
st         - C++ string.  Example: string stName;
sz         - Null terminated string.  Example: char szName[64];
fp         - Floating point.  Example: float fpPercent;
i          - Integer.  Example: int iSize;
w          - Word.  Example: short wLength;
dw         - Double word.  Example: long dwBytes;
tm         - Templated.  Example: _Ty tmItem;
class name - Object.  Example: CList listUsers;

Pre-prefixes:

u          - Unsigned.  Example: unsigned short uwLength;
k          - Constant.  Example: const int kiNum;
r          - Reference.  Example: char &rchGrade;
s          - Static.  Example: static int siNum;
rg         - Array.  Example: long rgdwValues[10];
m_         - Class data member.  Example: int m_iLength;
g_         - Global variable.  Example: char g_szName[64];
p          - Pointer to a single thing.  Example: int *piVar;
prg        - Dynamically allocated array.  Example: float *prgfpSizes;

[Cgewrapper-development] Things not covered in the Coding Methodology:

[<Bla...@at...>]

There are some things I have not covered in the coding methodology...here
they are, as far as I know  ;o)

Using integers, there should not be any variable created by calling:
int (variable)
this is incorrect and is not platform spanable, so use the following
variables instead:
int8   //1 byte integer (char)
uint8  //1 byte unsigned integer (unsigned char)
int16  //2 byte integer (short)
uint16  //2 byte unsigned integer (unsigned short)
int32   //4 byte integer (long)
uint32  //4 byte unsigned integer (unsigned long)

Special DirectX variables are allowed such as: WORD and DWORD
Special compiler variables are allowed such as: HRESULT

Special Note on Hresult:
when creating an hresult variable it must be named:
HRESULT rval;
If the variable is a class member variable use
HRESULT m_rval;
If the variable is a global use
HRESULT g_rval;
and so on.

Structure naming convention.  Structures must be named using the following
convention.

typedef struct
{
(variables)
} cge_t(Name), *cge_t(Name)_ptr

//Special Note to Ian:

typedef struct
{
cge_tDriverMode pDriverList[64];
UINT16 ListSize;
} cge_tDriverList, *cge_tDriverList_ptr;

This structure is incorrect, I shall correct it and upload the corrected
version when I am uploading the cgeInput class (DX8 version).  As you can
see pDriverList[64] is NOT a pointer, this was an oversight by me...when I
initially programed this structure it was going to be a pointer but then I
decided to just make it a constant structure, easier to work with and it's
not very large anyway (71 bytes each).  Also I need to change the UINT16 to
use uint16 (lowercase uint, this is a C++ compiler difference, the variables
are the same but the lowercase version is default supported by the compiler
while the uppercase was a defined version of it.)

I think that was the extend of the conventions that I overlooked when
writting that file....

Jacek Ringwelski

Re: [Cgewrapper-development] Coding style

[FireAngel <Fir...@ex...>]

I have created a naming/coding conventions/standards for the code used in
the wrapper.  Check the documentation for the code and look under the
heading "coding methodology" and you will see it there.  I have somewhat
strictly adheared to it, except the input class which was designed by cdx
developers (I helped a little with it  ;o).  I will expand the methodology
as needed to cover areas which were not previously explained.

Jacek Ringwelski

p.s.  The documentation should have come in the zip file as a compressed
".chm" file (html help file), and in the cvs you will find that I have also
uploaded the decompressed version of the html file if you have an html
editor you can open it and modify the help file and recompress it.

p.s.s.  Please send me your sourceforge username, so that I may add you to
the developers list so you can access the CVS...if you don't know how to use
CVS I can explain the setup process to you....you can contact me over ICQ
for faster support, ICQ# 10279839 (please include that you are Ian when
asking permision).

[Cgewrapper-development] Coding style

[Ian P. <ipe...@ve...>]

    I've noticed that you've _very_ loosely conformed to some variation of
Hungarian Notation in your coding.  Perhaps you should write up a small
(slightly formal) document with some naming/coding conventions/standards and
strictly follow them throughout your code (which may or may not require some
changes to your current code).  Since this is an open source project and
people with all sorts of different coding styles will be using this code, it
would be worth the effort to make your code as readable/understandable as
possible.  It would also be useful to anyone who wants to modify or add to
the code so the coding style can remain consistent throughout the code.
Just my two cents.

  - Ian Perez (ipe...@ve...) - "It is by will alone I set my mind
in motion"

[Cgewrapper-development] test

[<Bla...@at...>]

test

[Cgewrapper-development] test

[<Bla...@at...>]

test