Modules system implementation

[lonnieezell]

I have this started but I was originally going for a much bigger refactor when I was playing with this.

We need to add a module system so that we can modularize certain parts of the app into portions that can be turned on/off. CodeIgniter's built-in modular code support already provides 80% of the work. To make it so we can turn those on/off, though, we need the following:

• automatically add active module namespaces to the autoloader
• admin area to manage modules
• module file support to allow any special initialization for app and admin areas.
• Streamlined event support so modules can tie into UI easily.

[neznaika0]

I tried to create a modular project. It's a bit like vendor/ - each modules/* directory provides control over entities.

app
modules
- Main (all basic functions, starter code, libraries)
- Thread
- Post
- Category
- Tag

The Admin module is not needed. The app/Controllers/Admin/Dashboard controller should work with all admin routes from the modules.

app/* contains almost no code, mainly configuration settings.
The views have NS modules Thread\list

There may be problems with disabling when there are dependencies between modules. For example, you can't disable Post - Category, Thread.. they won't work.

I came to the conclusion that the module is a separate section of the project. Everything else should be in the App.

[lonnieezell]

Agree - and I was originally taking it that far also. The way to handle that is that everything must be completely separate and use an event type system to work together. That's not what I was thinking about here, though. My intent is that the core functionality should be just in app like it is. Anything that we feel a site might want to turn off could be an option for a module, though.