[eluser]Colin Williams[/eluser]
Quote:No, and that would also break the MVC structure.
I do agree that it's a bad approach that can be handled much more elegantly with enough forethought, but I'm done saying stuff like "this breaks the MVC structure." MVC is a
pattern that is largely open to interpretation. You can find MVC patterns applied to anything, real or virtual. CI's convention is that Controllers react to requests defined by the URI. Others argue that a controller is just something that reacts... to anything (which means that any function or method is in some respect a Controller). Same applies to Models. Anything that manipulates and/or retrieves data is a Model (so, for instance, one can argue that the Config class is a model for your configuration settings).
To call controller methods from anywhere in your app, search the Wiki for "Wick" and "Modular Extensions" (pardon the misleading nomenclature of that latter one... it's more like "Modular Organization" or "Modular Behavior"). They both provide a syntax for calling controller methods in many scopes.