Starting A New Component

From rootshell wiki

(Difference between revisions)
Jump to: navigation, search
 
Line 1: Line 1:
-
#REDIRECT [[Supermonko/Starting A New Component]]
+
{{SuperMonkoHeader}}
 +
 
 +
When you are creating a new component, note that :
 +
* We hold only one copy of each component, which is located in Super-Monko Component repository
 +
* Components should be written with reusing concept in mind, without any project-specific codes
 +
* Components should deliver their events to the client using Objective-C Protocols
 +
 
 +
 
 +
 
 +
Steps to create a new component :
 +
* Create a header file for component event delivery protocol
 +
* Document each interface message and describe about the overall behavior, arguments and the return value.
 +
* Commit the component into the following svn repository under the '''Source''' folder: <code>http://svn2.xp-dev.com/svn/Monko-Components</code>
 +
* Create a new test project under '''UnitTests''' Folder and import the component
 +
* Implement test cases and verify the component behavior
 +
* Check the component for memory leaks using Instruments
 +
 
 +
{{SuperMonkoFooter}}

Latest revision as of 15:03, 3 May 2010

Processes

Index

This page belongs to Turned On Ventures Guideline Series.


When you are creating a new component, note that :

  • We hold only one copy of each component, which is located in Super-Monko Component repository
  • Components should be written with reusing concept in mind, without any project-specific codes
  • Components should deliver their events to the client using Objective-C Protocols


Steps to create a new component :

  • Create a header file for component event delivery protocol
  • Document each interface message and describe about the overall behavior, arguments and the return value.
  • Commit the component into the following svn repository under the Source folder: http://svn2.xp-dev.com/svn/Monko-Components
  • Create a new test project under UnitTests Folder and import the component
  • Implement test cases and verify the component behavior
  • Check the component for memory leaks using Instruments




HierarchyPrevious.gif Starting Project | Using a component in project HierarchyNext.gif


Copyright Turned On Ventures 2010, turnedonventures.com

Personal tools