Modular Extensions - Version 4.3

[eluser]wiredesignz[/eluser]
This quote may help explain the use of HMVC modules as posted by Rick Jolly. Thanks Rick

[quote author="Rick Jolly" date="1203688844"]
Q. What are modules, why should I use them?

A. http://en.wikipedia.org/wiki/Module

Q. What is Modular HMVC, why should I use it?

A. Modular HMVC = Multiple MVC triads

This is most useful when you need to load a view and its data within a view. Think about adding a shopping cart to a page. The shopping cart needs its own controller which may call a model to get cart data. Then the controller needs to load the data into a view. So instead of the main controller handling the page and the shopping cart, the shopping cart MVC can be loaded directly in the page. The main controller doesn't need to know about it, and is totally isolated from it.

In CI we can't call more than 1 controller per request. Therefore, to achieve HMVC, we have to simulate controllers. It can be done with libraries, or with this "Modular Extensions HMVC" contribution.

The differences between using a library and a "Modular HMVC" HMVC class is:
1) No need to get and use the CI instance within an HMVC class
2) HMVC classes are stored in a modules directory as opposed to the libraries directory.

Q. Is Modular Extensions HMVC the same as Matchbox?

A. Since version 3.0 it is.

Modular HMVC means modular MVC triads. Matchbox and Modular Extensions allows related controllers, models, libraries, views, etc. to be grouped together in module directories and used like a mini application.[/quote]