Einführung in CodeIgniter
Auf IBMs developerworks gibt es eine Einführung in CodeIgniter. Es werden die absoluten Basics behandelt, aber da ich letzten Monat gerade mal wieder eine Seite mit CodeIgniter realisiert habe dachte ich rein damit ins Blog:
Finally, the good folks at EllisLab released CodeIgniter. After working with and experimenting with all the available PHP MVC frameworks, CodeIgniter has come out as the winner at many firms, mostly because it supports just enough freedom within its organizational dynamic to allow developers to work fast.
Freedom means that with CodeIgniter, you don’t have to name your database tables a certain way, nor do you have to name your models after your tables. This makes CodeIgniter the perfect choice to refactor a legacy PHP application, in which you may have all kinds of crazy structures that need porting over.
CodeIgniter doesn’t require a huge footprint of code (the 1.6.2 release is a slender 2.8 MB, 1.3 MB of which is user documentation you can delete), nor does it ask you to plug in to huge libraries like PEAR. It works equally well in PHP 4 or PHP 5, allowing you to create fairly portable applications. Finally, you don’t have to use a templating engine to create your views — just old-fashioned HTML and PHP will do.