Difference between revisions of "Guides/Platform Development/Tutorials"

From Sirikata Wiki
Jump to navigation Jump to search
(Initial import from sirikata-docs)
 
(→‎Platform Development Tutorials: Make link names more attractive)
 
Line 3: Line 3:
 
The sheer size of complexity of the Sirikata code can be a real barrier to contributing. The other parts of the guide try to help a new developer isolate themselves to a smaller portion of the code, allowing them to quickly understand the components they need to modify or extend. Here, we try to address a number of common tasks that span the entire project, either because they deal with utility code used throughout the project or because they deal with the architecture of the entire system.
 
The sheer size of complexity of the Sirikata code can be a real barrier to contributing. The other parts of the guide try to help a new developer isolate themselves to a smaller portion of the code, allowing them to quickly understand the components they need to modify or extend. Here, we try to address a number of common tasks that span the entire project, either because they deal with utility code used throughout the project or because they deal with the architecture of the entire system.
  
* [[Guides/Platform_Development/Tutorials/Application Structure]]
+
* [[Guides/Platform_Development/Tutorials/Application Structure|Application Structure]]
* [[Guides/Platform_Development/Tutorials/Writing a Plugin]]
+
* [[Guides/Platform_Development/Tutorials/Writing a Plugin|Writing a Plugin]]
* [[Guides/Platform_Development/Tutorials/Adding Options]]
+
* [[Guides/Platform_Development/Tutorials/Adding Options|Adding Options]]

Latest revision as of 17:58, 28 May 2012

Platform Development Tutorials

The sheer size of complexity of the Sirikata code can be a real barrier to contributing. The other parts of the guide try to help a new developer isolate themselves to a smaller portion of the code, allowing them to quickly understand the components they need to modify or extend. Here, we try to address a number of common tasks that span the entire project, either because they deal with utility code used throughout the project or because they deal with the architecture of the entire system.