But I noticed several posters to that blog series mentionedCodeigniter as a great way to go with sort of the same philosophy.And today it was mentioned on Planet PHP. So I checked it out today, Wow!—it is really, really nice.

CodeIgniter is quite simple, nothing we couldn’t do ourselves butsomeone else has done all the coding. It follows some Rails MVCmethodology, but in a much more simplified way. And simple is reallygood because it gives flexibility which is the big advantage of PHP.CodeIgniter is very new, just released a few weeks ago.

For example, the main author is not finished with his active recorddesign so he only has support for MySql (and we usePostgrsql). But the framework is so simple, I can work around that fornow with skipping the active record stuff and just using standard dbcalls. (I can simplify that later when they finish the db architectureand add postgres support). The new Zend framework also takes the simple route too, and might also be a great answer but this approach seems even simpler.

Check out the codeigniter website�they seem very professional�the documentation is very good (great movie tutorials). Even the quality oftheir forum page is very good (apparently their cms product is verygood). I’m initially really impressed by this. I’m going to try it outtonight.