Generated Code

Never touch the generated bindings of ogre4j if you don't know exactly what your are doing!

Code style

Have a look at the code style of the existing classes and use the same style.
Native methods are located at the end of a class.
Use java types if possible, instead of creating a new one (i.e. vector3f, etc).
Copy the function and class descriptions from the OGRE docu to support javadoc.
Use the same file header as in exiting files.
Update the build file for the JNI headers if adding new classes with native functions.
If declaring new native functions, implement them in c++ before you commit the java class.
Order the definitions in the C++ file same order as the declarations in the auto-generated JNI header files.

Enter a comment if commiting
Never commit if the change produces errors (a version control system is not a backup system)

► Sign in to add a comment