Comments on: CodeIgniter: PHP Development Fun – Part 1

By: Mahbub

Mahbub — Thu, 12 Mar 2009 15:26:43 +0000

@ Wiggum

To know a true MVC, we don’t need to study struts. There are other sophisticated Frameworks like Zend, Kohana, CakePHP which have better OOP practices. CI is getting better and better. With the new release of 1.7.1, I’m convinced that CI can adopt the need of time. I’m not a die hard fan of CI but I find it very friendly, well documented and very large community support which makes it a pretty good choice.

By: Colin

Colin — Sat, 07 Feb 2009 08:16:44 +0000

CI is based entirely on PHP4 and will be its ultimate downfall.

Not at all true. If you delete the Base4.php file, you could then say CI is based entirely on PHP 5. It “runs” on PHP 4, which means any kid getting his hands into programming can use it on their $7/mo shared hosting account. It also means it can be dropped right into old systems reliant on PHP 4. Sure, CI might benefit from some design patterns if it left PHP 4 in the dust (see Kohana), but that’s a wholly different argument.

CI also has some really odd ‘abstraction’ choices and makes a half attempt at the MVC design pattern when it comes down to it. Most CI devleopers end up stuffing their controller files to the brim with spaghetti code anyways rendering any advantage of MVC moot.

So the fact that inexperienced developers improperly structure their apps has to do with a flaw in the framework? No. It’s actually a testament to CI’s flexibility.

By: signal response » Blog Archive » Igniter.

signal response » Blog Archive » Igniter. — Fri, 06 Feb 2009 13:08:14 +0000

[...] couple of tutorial posts on Devlounge regarding CodeIgniter (is everything CamelCase now?) Part One and Part Two. CodeIgniter will be intertwined with Expression Engine come 2.0 so it might be worth [...]

By: Jake Rutter

Jake Rutter — Thu, 05 Feb 2009 15:54:01 +0000

I just used code igniter for the first time to build: dogfriendlyparks.com. The learning curve is pretty easy, as long as you are familiar with how MVC works. I had prior experience with ruby on rails, and I found it very similar – except for the php part. Code Igniter has a great support community too!

By: CodeIgniter: Interacting With a Database | Devlounge

CodeIgniter: Interacting With a Database | Devlounge — Thu, 05 Feb 2009 11:12:06 +0000

[...] my previous post entitled, CodeIgniter: PHP Development Fun – Part 1, I talked a little about my excitement regarding CodeIgniter. So far, I have found the learning [...]

By: Wiggum

Wiggum — Mon, 02 Feb 2009 21:52:14 +0000

Ehh…CI is based entirely on PHP4 and will be its ultimate downfall. Any PHP application/framework built on PHP4 and its horrific object model should be avoided at all costs. PHP4 is dead and was an embarrassment. Let’s stop pushing out more PHP4 applications when PHP6 is around the corner.

CI also has some really odd ‘abstraction’ choices and makes a half attempt at the MVC design pattern when it comes down to it. Most CI devleopers end up stuffing their controller files to the brim with spaghetti code anyways rendering any advantage of MVC moot.

The good thing about CI is that it at least gets PHP developers thinking about cleaner code and thinking about MVC. Now getting PHP developers to actually understand MVC is another matter!

If you truly want MVC, just use Struts and be done with it.

By: Matthew Pennell

Matthew Pennell — Fri, 30 Jan 2009 09:03:21 +0000

One of the most attractive features of CodeIgniter is that it will shortly be the engine that runs ExpressionEngine. This means that anyone with CI skills can instantly turn their hand to developing add-ons for EE – quite a lucrative area of growth once EE hits 2.0.

By: Mike Stempień

Mike Stempień — Thu, 29 Jan 2009 19:57:17 +0000

Good choice, it is really great as a first framework and it has one of the best documentations I ever seen. Can’t wait what will version 2.0 bring.

By: Luke L

Luke L — Thu, 29 Jan 2009 18:50:33 +0000

After using CodeIgniter for several projects I’ve recently switched to Kohana (http://kohanaphp.com/). It’s a port of CI but written for PHP5 with several other tweaks (which ultimately make sense once you become adjusted to them i.e. the View system). In fact, I’m part way through rewriting my blog in Kohana at the moment.

By: Chung Bey Luen

Chung Bey Luen — Thu, 29 Jan 2009 16:44:30 +0000

I think I should check out CodeIgniter as well and see what it can offers. My PHP skill is not good enough compared to my Java skill.

By: Steve B

Steve B — Thu, 29 Jan 2009 16:30:33 +0000

I had the same exact experience as you. My PHP skills were not ninja like, I had limited knowledge of PHP OOP, I had no knowledge of the MVC framework, and my applications were starting to get a little out of hand and starting to become very messy.

CI was a step in the right direction. I have learned a ton of new PHP techniques, including OOP, CI makes learning the MVC model super easy, and my projects have become so much more manageable.

One of my favorite things about CI is how easy it is to write commonly used html objects. Takes anchors for example. Before I was writing them the usual way now, I can use: anchor(‘controller/method’, anchor name); Boom, done, so simple. CI takes care of the monotonous web dev tasks.

I look forward to your code examples and upcoming posts about CI. CI FTW!