Ok, maybe I have to clarify what my project is about to understand my questions.
I'm developing a custom cms for a client, which I'm almost to use for another client.
The idea is that a client can create a page and add 1 or more elements like html from a wysiwyg, image gallery, news list or other views of a certain module.
I use HMVC because it give me the possibility to create sepperate modules which contain all code for one topic like news. So all views for front-end elements like news list and news item, and the backend maintanance application are there. Every module has his own db tables which are only used by that module.
Using the modules::run method gave me an easy way to get content from a certain module, and my pages controller would call modules::run for every element and put all collected data in the template of that page.
Because I'm constantly reading that 'controllers calling controllers is bad' (practice), I wanted to get rid of modules::run and find another way. Because HMVC has the possibility to have libraries per module I thouht I could move the code to gather data from the database and create the needed HTML for my views.
So now my page controller can load the library from my news module and create my news list or news item without calling controllers from other controllers.
Narf will probably never touch HMVC with a ten foot pole, so I get that he wants to keep the libraries portable - without the use of models. But when using HMVC each module can contain it's own libraries, and my libraries use only module specific data. And because of HMVC they are portable in their own way, which gives me the possibility to copy and paste this module to the module folder of client nr 2 and by creating a new table in the db it can work right out of the box.
I would think this is a better way of doing than using modules::run, but if there's still a better way I am open for suggestions. I'm eager to so...
-Roger
