Personal tools

Difference between revisions of "Creating a new module"

From MohidWiki

Jump to: navigation, search
m (1 revision)
 
Line 1: Line 1:
 
In order to create a new module and include it in [[Mohid Framework]], one should always use [[Module Shell]] as the starting file. Exceptions can me made if it is proven that starting from another module is more profitable. In this case, keep in mind that all source code actualizations must be made to the 2 modules (old and new) in order not to spread “dirty” code to new modules.  
 
In order to create a new module and include it in [[Mohid Framework]], one should always use [[Module Shell]] as the starting file. Exceptions can me made if it is proven that starting from another module is more profitable. In this case, keep in mind that all source code actualizations must be made to the 2 modules (old and new) in order not to spread “dirty” code to new modules.  
  
Remember to include, if applicable, the module keywords at the source code file header, as it is made in other Mohid modules and also update [http://www.mohid.com/IHS/ Mohid Keyword Online Database]
+
Remember to include, if applicable, the module keywords at the source code file header, as it is made in other Mohid modules and also update [http://wiki.mohid.com/index.php?title=Keyword_list MOHID keyword Database]
  
 
[[Category:Programming]]
 
[[Category:Programming]]

Latest revision as of 13:56, 3 October 2019

In order to create a new module and include it in Mohid Framework, one should always use Module Shell as the starting file. Exceptions can me made if it is proven that starting from another module is more profitable. In this case, keep in mind that all source code actualizations must be made to the 2 modules (old and new) in order not to spread “dirty” code to new modules.

Remember to include, if applicable, the module keywords at the source code file header, as it is made in other Mohid modules and also update MOHID keyword Database