1. wiredesignz
  2. codeigniter-modular-extensions-hmvc


wiredesignz  committed 70838d7

Update readme.md

  • Participants
  • Parent commits ddcf4ea
  • Branches default

Comments (0)

Files changed (1)

File readme.md

View file
-===Support development of Modular Extensions - HMVC===
+###Support development of Modular Extensions - HMVC
 [[https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FK79XNCUE9P5C|{{https://www.paypal.com/en_US/i/btn/btn_donateCC_LG.gif | Support development}}]]
-==Modular Extensions - HMVC==
+##Modular Extensions - HMVC
 Modular Extensions makes the CodeIgniter PHP framework modular. Modules are groups of independent components, typically model, controller and view, arranged in an application modules sub-directory, that can be dropped into other CodeIgniter applications.
 Module Controllers can be used as normal Controllers or HMVC Controllers and they can be used to help you build view partials.
 All controllers can contain an $autoload class variable, which holds an array of items to load prior to running the constructor. This can be used together with module/config/autoload.php, however using the $autoload variable only works for that specific controller.
 If you add the _remap() method to your controllers you can prevent unwanted access to them from the URL and redirect or flag an error as you like.
 To use HMVC functionality, such as Modules::run(), controllers must extend the MX_Controller class.
-==View Partials==
+##View Partials
 Using a Module as a view partial from within a view is as easy as writing:
 Parameters are optional, You may pass any number of parameters.
-==Modular Extensions installation==
+##Modular Extensions installation
 1) Start with a clean CI install.
 -Steps 9-11 show MX working with both controller and view in the “welcome” module - there should be no files in the application/controllers or application/views directories.
 Q. What are modules, why should I use them?