Actually, I’m not saying that you can’t build a HMVC stack at all. Just I don’t like to deal with chained controllers, MVC triads and the related stuff. In either case, if you’re interested in tweaking the code samples and get a pretty functional HMVC implementation, a good start would be refactoring the Route class, so it can accept, for instance, an array of page controllers, rather than just one. In doing so, you’d be able to invoke multiple controllers, along with their associated models and views, when a given route matches a single request. Just an idea that should be polished down the road to fit more specific requirements. Thanks :)
↧