(05-29-2015, 07:30 AM)kilishan Wrote: I don't see any problems with loading models from a library, personally.
Agreed. Libraries are there to fill the gaps in the MVC structure when building an application. By using a model from within the library, not only is the library staying out of a clearly-defined role in the MVC structure, it's also allowing the data access to remain consistent if a controller or some other part of the application needs to access the same data, as it should use the same model.
I also feel like I should elaborate on the hydra reference. When we tried to cut the MX_Controller out of Bonfire's use of HMVC, especially in my own application where some of the code is now nearly 3 years old (but the newest module was written yesterday), some bugs popped up which eventually came back to CI_Controller being attached to multiple points in the class hierarchy when calling $this->{whatever}. Essentially, what was a singleton under MX_Controller became a multi-headed monster when using CI_Controller and Modules::Run(), and attempting to squash the bug just lead to finding more bugs.
