HMVC the right way ?! |
06-01-2015, 10:25 PM
(This post was last modified: 06-01-2015, 10:34 PM by RogerMore. Edit Reason: typo )
Ok. And here we are again.
There isn't a lot of trouble I'm having to make it work. It was already working, but was searching for a way out of the controller calling controller thing. The choice of HMVC is made, and this thread is not about whether to use it or not, it is about learning a way without modules::run. I don't think projects aren't really harder to understand for a noob dev, because when you explain a module is like an application within CI they are fine. When a project as this is calling code from another module it maybe needs 15 minutes more explaining. I'm guessing a hardcore coder like you, no1youknowz, would have no problem whatsoever. So you have your own code which you can put from 1 project to another which is called libraries. Who doesn't have that. One thing I'm missing though, is that your auth lib doesn't seem to need models and views for login/password forget screens or your payment gateway doesn't need at least some views for choosing which payment and so on. I hope that your login screen isn't popping out of your auth lib because I don't know if that would be a best practice... I like things structured, so I like the idea of having a module folder with all models, view, controllers, libraries and so on. I honestly don't know how to do it another way, and as long the HMVC nay sayers only say nay and don't give a real answer to the questions or provide a similar solution I am good with HMVC. |
Welcome Guest, Not a member yet? Register Sign In |