-
Notifications
You must be signed in to change notification settings - Fork 12
Developer Guidlines
Alex edited this page May 10, 2014
·
6 revisions
Hello and welcome to our community project. In order to streamline the development process read this document and always see that your contribution is compliant with our standards.
On a side note standards always have to be updated. So if you see something that you know/think should be different please inform the team and we will elaborate.
- Toolbox
- Unity3D 4.3.4
- MonoDevelop - IDE
- Git - Source Control
- Asana - Task Management (Submit your email and we will send an invite)
- FB - our facebook page
- Code guide lines
- Unity3D C# Coding Guide lines Link
- Try to encapsulate properties by using find FindGameObjectsWithTag
- Make public only properties you must have as public for tweaking. Any other properties should be private
- When creating a visual/mesh. Always use an empty and add the mesh to it as child. And the code collision etc should be on the empty. (this way you will be able to change the graphics without breaking the scene)
- Dont clutter the scene with spawned objects. Set spawned objects to an empty.
- Read this article
- Write OO design
- Source Control workflow
- Each team member will fork the main branch
- After you completed your work create a pull request
- The code will be reviewed and then pulled to the main branch
- Tasks assignment
- Each team member will be assigned to a task via Asana
- Preferably when taking a task you should be able to give a date of delivery
- If you wish to create something cool we will not stop you. Just make it to a side branch and we will review your idea. Every one should have his chance to shine.
- Unity3D
- The hierarchy should be arranged by moving items in too empties
- Tags should be all CAPS
- Try to never scale stuff like art and meshes. Always import them at the right size.
- Mono Develop
- File Templates for Unity3D Link