Site:Frontend:Modules - Revision history

MetrixJustin: /* Listing Content */

2012-06-18T17:42:50Z

‎Listing Content

2012-06-18T17:42:19Z

‎Listing Content

2012-06-18T17:42:02Z

‎Listing Content

2012-06-18T17:38:34Z

2012-06-18T17:13:38Z

‎Creating a Module

2012-06-15T21:00:31Z

2012-06-15T20:59:59Z

2012-06-15T20:59:15Z

‎Common

2012-06-15T19:56:57Z

‎Module Only

2012-06-15T19:25:54Z

@@ Line 74: / Line 74: @@
 Example: Listing the titles of the context Content: All
-   <?cs
+   <?cs each:item = MS.content.items ?>
-  each:item = MS.content.items ?><?cs
+    <?cs var:item.title ?><nowiki><br /></nowiki>
-    var:item.title ?><nowiki><br /></nowiki><?cs
+  <?cs /each ?>
-  /each ?>

@@ Line 76: / Line 76: @@
    <?cs
    each:item = MS.content.items ?><?cs
-     var:item.title ?><br /><?cs
+     var:item.title ?><nowiki><br /></nowiki><?cs
    /each ?>

@@ Line 68: / Line 68: @@
 == Listing Content ==
-Listing content relies on the context of module page, not the parent page.
+Listing content relies on the context of module page, not the parent page. For example if the parent page has a context of "My Videos" but the module page doesn't have a context nothing will be listed on the page.
-For example if the parent page has a context of "My Videos" but the module page doesn't have a context nothing will be listed on the page.
+The HDF keys/values will still remain the same, so they can be accessed the same way as a regular page.

← Older revision		Revision as of 17:38, 18 June 2012
Line 65:		Line 65:

	Each module that requires javascript should have its own controller. The controller is made up of classes that control different parts of the module. This allows us to only enable functions and listeners that are required on the page, instead of having them always active. This also ensures that when concatenating the javascript file that function and listeners wont overlap.		Each module that requires javascript should have its own controller. The controller is made up of classes that control different parts of the module. This allows us to only enable functions and listeners that are required on the page, instead of having them always active. This also ensures that when concatenating the javascript file that function and listeners wont overlap.
		+
		+	== Listing Content ==
		+
		+	Listing content relies on the context of module page, not the parent page.
		+
		+	For example if the parent page has a context of "My Videos" but the module page doesn't have a context nothing will be listed on the page.

← Older revision		Revision as of 17:13, 18 June 2012
Line 61:		Line 61:

	If you're using the stack module, all CSS/JS stack includes would be called here		If you're using the stack module, all CSS/JS stack includes would be called here
		+
		+	== Javascript Controller ==
		+
		+	Each module that requires javascript should have its own controller. The controller is made up of classes that control different parts of the module. This allows us to only enable functions and listeners that are required on the page, instead of having them always active. This also ensures that when concatenating the javascript file that function and listeners wont overlap.

@@ Line 34: / Line 34: @@
     http://example.com/?page=auth&mpage=users.json&output=moduleonly
-==Creating a Module =
+= Creating a Module =
 == Common ==
-==== Default Page ====
+=== Default Page ===
 This is the default page that loads when no mpage is set.
-==== Autoload ====
+=== Autoload ===
 Autoloaded modules will be included on every page of the site. This is helpful for caching and including JS and CSS files throughout the site.
-==== Key / Value Pairs ====
+=== Key / Value Pairs ===
 Key / Value pairs are module-wide variables that can easily be changed. These are often used as settings for the module.
@@ Line 56: / Line 56: @@
    <?cs /if ?>
-==== Initialization ====
+=== Initialization ===
 Initialization is the first part of the module that is loaded. If there are any required modules to be loaded before this module you will need to include them here.
 If you're using the stack module, all CSS/JS stack includes would be called here

@@ Line 1: / Line 1: @@
-== Introduction ==
+= Introduction =
 Modules contain stand-alone code, files, pages, and page includes required to perform the tasks of the module.
-== Module Integration ==
+= Module Integration =
-=== Adding a Module to a Page ===
+== Adding a Module to a Page ==
 After a module is created or imported, it will be listed under Module Integration while editing a site page.
@@ Line 19: / Line 19: @@
    </html>
-=== Accessing Module Pages ===
+== Accessing Module Pages ==
 Since modules are injected into a parent page, pages within a module need to be called with the '''mpage''' URL parameter.
@@ Line 27: / Line 27: @@
    http://example.com/?page=auth&mpage=login
-=== Module Only ===
+== Module Only ==
 Some modules contain pages that serve up JSON or XML content and should ignore the included header and footer. This can be done by adding the URL parameter "output=moduleonly"
@@ Line 34: / Line 34: @@
     http://example.com/?page=auth&mpage=users.json&output=moduleonly
-== Creating a Module ==
+==Creating a Module =
-= Common =
+== Common ==
 ==== Default Page ====

← Older revision		Revision as of 19:25, 15 June 2012
Line 33:		Line 33:
	Example:		Example:
	http://example.com/?page=auth&mpage=users.json&output=moduleonly		http://example.com/?page=auth&mpage=users.json&output=moduleonly
		+
		+
		+	== Creating a Module ==
		+
		+	=== Common ===
		+
		+	==== Default Page ====
		+
		+	This is the default page that loads when no mpage is set.
		+
		+	==== Autoload ====
		+
		+	Autoloaded modules will be included on every page of the site. This is helpful for caching and including JS and CSS files throughout the site.
		+
		+	==== Key / Value Pairs ====
		+
		+	Key / Value pairs are module-wide variables that can easily be changed. These are often used as settings for the module.
		+
		+	For example, if we have a setting called "show_stats" and want to see if its set to "yes"
		+
		+	<?cs if:'<!show_stats!>' == 'yes' ?>
		+	Showing Stats
		+	<?cs /if ?>
		+
		+	==== Initialization ====
		+
		+	Initialization is the first part of the module that is loaded. If there are any required modules to be loaded before this module you will need to include them here.
		+
		+	If you're using the stack module, all CSS/JS stack includes would be called here