A tutorial about Ion Auth and authentication in CI3 |
(10-30-2015, 02:07 AM)Martin7483 Wrote:(10-29-2015, 08:27 PM)orionstar Wrote:(10-29-2015, 04:14 PM)solidcodes Wrote: @Avenirer You don't have to use MX_Controller if you only want to use modular separation, MX_Controller is only required when you want to use the HMVC design pattern. You say it correctly "SHOULD BE" but in some use cases it's more simple and practical to create dependencies. For example if you have a module updater function in your CMS and you want to update the users module to the latest version and it's require to use the latest Ion Auth library, then you can't simple update only the module folder by replacing it, instead you have to replace libraries and other stuff in the core application. This makes the updater more complex and hard to maintain. Other examples as usual dependencies: settings, groups, permission, comments, files etc... Almost every complex module have dependencies... if you have a permission module then the dependencies of it can be the groups and the users module... If I would like to work in a strict environment which restrict me then I would choose Symfony 2 or Zend 2 and follow their best practises and PSR stuffs... I use CI because I can do everything the way I think it's appropriate and practical. Ps. In CI + HMVC based CMSs the best practise is using dependent modules... And also in L4 + creolab/laravel-modules... @avenirer: Sorry for the off topic :S |
Welcome Guest, Not a member yet? Register Sign In |