Comments on: CodeIgniter 2.0 and Mercurial Transition

By: Rey Philip Regis

Rey Philip Regis — Tue, 22 Jun 2010 15:17:18 +0000

Why dont the CI team create an official ACL library like other PHP Frameworks have? Its also essential and also it can really help a lot of PHP developers out there..

By: Phil Sturgeon

Phil Sturgeon — Tue, 06 Apr 2010 14:09:31 +0000

Derek Allard said at EECI2009 (on the way to a pub, nothing official) that CodeIgniter will – at some point in time – probably have some sort of HMVC. Maybe. >.<

By: Jorge

Jorge — Mon, 15 Mar 2010 19:55:48 +0000

do you know if ELab think about introduce the concept of modules like something similar to Matchbox or HMVC?

By: Phil Sturgeon

Phil Sturgeon — Mon, 15 Mar 2010 08:41:18 +0000

@SeanJA: Using $this->somelib provides much more than just PHP 4 support. Not only is it a brilliant way to keep all instances of a libratry/modal global throughout the entire CI instance, but it allows support for the wonderful MY_ prefix.

If you were to create a MY_ whatever library while using __autoload() then you would have to run through your application changing $var = new Class() and $var = new MY_Class() which defeats the entire purpose.

I am perfectly happy to keep $this->library and I very much doubt it’s going anywhere anytime soon.

@Michael: Packages doesn’t support controllers and is not really intended to be a modular system. It is more to allow multiple applications to share a stash of libraries, models, helpers, etc something that is currently not possible without some crazy Symlinking or by shoving all your code into a shared “system” folder.

It’s a shame EllisLab have not added any modular support, but EE2′s modular system is very crazy and would not work directly in the CI codebase. Derek Allard assured me that “at some point, there will be modularity in CodeIgniter, but I’m not sure when”.

Luckily Modular Separation works fine in 2.0 with a few tweaks.

By: Yehosef

Yehosef — Sat, 13 Mar 2010 22:30:26 +0000

@Michael -
Autoloading and __get would allow you to use $this->new_library directly which would be mapped to the new functionality – should they chose to go this route. You just try to instatiate the new new_class in __get – the programmer won’t feel a thing (you can wrap the new class in a try/catch block incase the class doesn’t exist.)

Of course, you could use the traditional New_Class::factory() to make a new class – better for chaining. I don’t know what advantage there is to having the CI super object.

By: Michael Wales

Michael Wales — Fri, 12 Mar 2010 12:11:58 +0000

@SeanJA I don’t think they will ever go that route as that will force them to use the standard instantiation syntax ($var = new Class()) which is a far cry from CodeIgniter’s standard syntax (where everything is a child object of the CodeIgniter super global object).

By: SeanJA

SeanJA — Fri, 12 Mar 2010 05:33:38 +0000

“CodeIgniter 2.0.0 functionality is not guaranteed to work in PHP4″

Good to see that they are finally dropping that so they can start adding things like __autoload to get rid of the ugly $this->[helper|model|library]->load() stuff. That always bugged me.

By: Lonnie Ezell

Lonnie Ezell — Thu, 11 Mar 2010 19:32:23 +0000

I downloaded the latest code and had a look through the user manual and Packages are basically modules. Here’s the relevant info from the new UM:

“Added ability to set “Package” paths – specific paths where the Loader and Config classes should try to look first for a requested file. This allows distribution of sub-applications with their own libraries, models, config files, etc. in a single “package” directory. See the Loader class documentation for more details.”

By: Michael Wales

Michael Wales — Thu, 11 Mar 2010 19:18:19 +0000

Good call – I saw your comment on the forums about packages and went digging back through looking for what you had seen. Do you envision it being something where I could build up ErkanaAuth (all controllers, models, views, etc.) and distribute it to other people in a plug-and-play fashion via the third_party directory?

By: Phil Sturgeon

Phil Sturgeon — Thu, 11 Mar 2010 19:12:09 +0000

It looks like the third_party directory is just a default “package” location for adding shared libraries, models, etc.

Not really used for anything just yet, but could be very handy if your third_party folder was a symlink.