Modules is only a static helper class, it isn’t meant to be instantiated. The HMVC class is extended by your module… I suppose it could be called Module.

One last thing… I’m not sure if the Modular Extensions is just a helper or it is a library. For me, it is a library that have a helper inside. Even more, it is in the same level of Controller and Model libraries. In my opinion, it should go to “application/libraries”, with the name “Module.php”.

Edemilson Lima - 25 February 2008 07:26 AM

Modules is only a static helper class, it isn’t meant to be instantiated. The HMVC class is extended by your module… I suppose it could be called Module.

One last thing… I’m not sure if the Modular Extensions is just a helper or it is a library. For me, it is a library that have a helper inside. Even more, it is in the same level of Controller and Model libraries. In my opinion, it should go to “application/libraries”, with the name “Module.php”.

If it was a library, then CI would instantiate it when it’s loaded. That doesn’t make sense. If you want to make it a true CI helper instead of a static class then change the methods. For example:

- run() becomes modules_run()
- so to call it, modules::run() becomes modules_run()

In my view, a helper is a standalone function and a library is a set of functions or classes that work together. It doesn’t matter if it can be instantiated or not, unless the library concept in CI only applies to intantiable classes. Anyway, I do prefer to use modules::run() than modules_run().

By the way, what do you think about the version 3.0? Is it more a library than a helper or not?

http://codeigniter.com/forums/viewthread/72580/