Modules - Revision history

50.76.38.36: /* Introduction */

2012-09-18T19:46:27Z

‎Introduction

X2WikiAdmin at 22:25, 17 September 2012

2012-09-17T22:25:12Z

X2WikiAdmin: Created page with "= Introduction = Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-appli..."

2012-09-17T22:24:57Z

Created page with "= Introduction = Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-appli..."

New page

= Introduction =
Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-applications of the main web application. A convention followed in X2EngineCRM's codebase is that the first part of the url past the entry script is the name of the module being accessed by the request. So, <code>contacts/[route]</code> would access the route <code>[route]</code> within a controller belonging to the contacts module.

== Creating a module ==
The first step one can take to create a module is to use X2Studio. That will create a basic customizable module whose model can be extended and customized using X2Fields. Once satisfied with the fields, one can further tailor the module to practically any purpose by modifying/adding properties to all the classes in the module.

(todo: expand upon this with the new procedure for the URL rules and the conventions for naming classes)

← Older revision		Revision as of 22:25, 17 September 2012
Line 1:		Line 1:
		+	[[Category:Development]]
		+
	= Introduction =		= Introduction =
	Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-applications of the main web application. A convention followed in X2EngineCRM's codebase is that the first part of the url past the entry script is the name of the module being accessed by the request. So, <code>contacts/[route]</code> would access the route <code>[route]</code> within a controller belonging to the contacts module.		Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-applications of the main web application. A convention followed in X2EngineCRM's codebase is that the first part of the url past the entry script is the name of the module being accessed by the request. So, <code>contacts/[route]</code> would access the route <code>[route]</code> within a controller belonging to the contacts module.

@@ Line 4: / Line 4: @@
 Most of the functionality of X2EngineCRM is contained within ''modules''. Modules are in essence self-contained applications in themselves acting as sub-applications of the main web application. A convention followed in X2EngineCRM's codebase is that the first part of the url past the entry script is the name of the module being accessed by the request. So, <code>contacts/[route]</code> would access the route <code>[route]</code> within a controller belonging to the contacts module.
-== Creating a module ==
+= Creating a module =
 The first step one can take to create a module is to use X2Studio. That will create a basic customizable module whose model can be extended and customized using X2Fields. Once satisfied with the fields, one can further tailor the module to practically any purpose by modifying/adding properties to all the classes in the module.
 (todo: expand upon this with the new procedure for the URL rules and the conventions for naming classes)