Application structure question

[eluser]beemr[/eluser]
[quote author="wiredesignz" date="1216820187"]A library loading views?... This sounds suspiciously like a controller to me.[/quote]
Yes. It's a bit of a bastardization, but it is tidy. All of my auth code exists in the auth library. If I need global access to another discreet "module", it will live in its own separate library. Models and views are still separated CI-style. Call it MVLibrary.

Micheal Wales was describing what is often called a "Super Controller" pattern, but the tradeoff is that there is only one parent controller. If you are running many different such "modules" through your Super-controller, you will have a monolithic entity that holds disparate functions. While the Super-controller is passing down an auth module, it might also be passing down a cart and a messaging cue.

Super-controller: Would you like a shopping cart, messaging, and advertisements with that context-nav?

MVLibrary: what controller?