HMVC the right way ?! |
(06-01-2015, 10:25 PM)RogerMore Wrote: 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... What are you talking about? A library is a block of code that facilitates certain functions to be exposed for the Controller or to pass data to/from the Model. I have libraries which then can be extended should that particular project need it. Or I can just use minimal functions because the project is simplistic. To be clear, the Libraries I have are not written in Codeigniter (so they are framework agnostic). They are "included" and then I use whatever endpoints I need to. The future endeavor is to use namespaces and then include composer support. So then I autoload them and exist out of the structure of the framework. But then thats out of the scope of this discussion. After I have completed the integration of the library. The controllers are updated, again very trivial, the database is updated and the models written (again very trivial) and whatever views I want to use for the project are used. All this work, literally 5 to 10 minutes work of dropping in a specific functionality. In future, when I have the code in composer. It's just a case of changing the composer file. Doing an update and then hitting the ground running. Like I am doing with the several composer modules I'm using now. |
Welcome Guest, Not a member yet? Register Sign In |