CodeIgniter - An MVC framework for PHP
I have been using CodeIgniter since some time and used in couple of my projects. It's a good and easy to use PHP MVC Framework, which takes you on the road very quickly and you start developing real time application with it. For any experienced PHP Programmer it's matter of few hours to start working with CI and get started-on with production.
It's got decent documentation (User Guide, Wiki and Community support forum). No configuration and no command-lines. Last release was way back in September'09 and I heard something about v1.8 sometime after that. But now it has been more than 1 year and recently while going through news section on CI website I read a post stating that new version of framework CI2 is about to be released.
I got excited and downloaded a copy from bitbucket. I was happy to see that CodeIgniter2 will be dropping PHP4 support step by step. There are lot of new changes/additions which you might be interested in if you're day-to-day CI user. Ellislab being professional company CI2 has been already used in their newer version of ExpressionEngine.
Here are some of the changes I have grabbed from CodeIgniter2 User Guide:
- General changes
- PHP 4 support is deprecated. Features new to 2.0.0 may not support PHP 4, and all legacy features will no longer support PHP 4 as of 2.1.0. (Good)
- Scaffolding, having been deprecated for a number of versions, has been removed.
- Plugins have been removed, in favor of Helpers. The CAPTCHA plugin has been converted to a Helper and documented. The JavaScript calendar plugin was removed due to the ready availability of great JavaScript calendars, particularly with jQuery.
- Added new special Library type: Drivers.
- Moved the application folder outside of the system folder. (I liked this)
- Added routing overrides to the main index.php file, enabling the normal routing to be overridden on a per "index" file basis.
- Added the ability to set config values (or override config values) directly from data set in the main index.php file. This allows a single application to be used with multiple front controllers, each having its own config values.
- Added $config['directory_trigger'] to the config file so that a controller sub-directory can be specified when running _GET strings instead of URI segments.
- 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.
- In-development code is now hosted at BitBucket. (Go grab your copy)
- Removed the deprecated Validation Class. Read the rest of this entry »
