Modular Extensions - HMVC version 5.2

[eluser]mark17[/eluser]
Dear wiredesignz,


My team will start a quite important project early next week. This project has some characteristics which force me to leave pure MVC behind and adopt the HMVC, perhaps even PAC-style, way of development. Although this is not the issue, i do have some concerns of which i hope you to alleviate them.

Somewhere overhere i read some text about ME not working properly when using alternative parents for controllers, the common MY_Controller practice. Although i've found answers to many of my doubts and questions, i cannot quickly redesign an application which does not allow for different parent controllers other than the one provided by CI alone.

I also got the impression from this topic (the PHP5 version) that since a while, there is a way to achieve this. But the question is how to do it and what consequences it implies. Obviously i understand the implications of disemboweling a modular design in which modulecontrollers inherit from one common ancestor, but due to the nature of this project and the all-to-tight deadline i am almost coerced in a situation in which i should't adhere to just my principles

Also, i prefer using a PHP5 version instead. Though it happens to be a rather young rewrite of the original PHP4 ME. I have searched this topic for things like bugfixes etcetera but didn't find much of interest. It also seems that you still keep the PHP5 version for testers-only, which tells me it is not production ready. Can you shed some light on the progress and the expected release of this nice piece of code?

Anyway,i've read tons of material this evening and i hereby excuse for asking for the already-known, so please bear with me.


Regards,