[eluser]Unknown[/eluser]
I'm currently investigating using CodeIgniter for full-on application development, e.g. for building something like Wordpress on CI. I've come across a very interesting issue in the process -- structure, and how to work with code being added on e.g. through plugins/modules. How is it that you maintain custom application structures on top of CodeIgniter?
For example, many open source PHP applications have a "modules" directory. Where would that go in a CI installation -- under /system/application, I'm presuming, but can anyone foresee any problems with putting it in the root installation folder? Once the module code is somewhere in the application, is it possible to use existing CI structure and code to work with the modules, or is it best to create a new system to handle them?
I'm thinking of conforming to the existing CI structure and having modules function as libraries, being used with the hooks system (hooks to be bound automagically somehow) and placed in /system/application/libraries. However, I'm not sure of any potential conflicts of this, or if a more suitable system could be developed by cloning the libraries system and altering it to deal with self contained mini-applications. Interested in your thoughts on this, and info on any projects that have gone down this path before.
