It is quite funny that so many of the posts here (CI Forum in general) seem to be a complaint about Codeigniter not being able to write the application on its own.  In many cases the complaint centers around a mythical crud model that will magically do the work for you.  I wonder what the poster wants Codeigniter to do?  At some point you must write actual code.

CI provides what I consider to be a well balanced approach to structuring a php framework.   

I wonder if Ellislab has perfected Artificial Intelligence yet.  That would certainly limit the number of “complaints”.  Perhaps that will be released in the future

Thanks for a great framework and to those who believe in magic thanks for the laughs.

I think the worse part of it all is - so many people think scaffolding is a basis for their application. It’s not!

To be honest, it could be removed and would save a lot of posts from occurring here on the forums. I am curious as to how many people actually use it - I’ve never seen it before, phpMyAdmin or the MySQL command line are more than enough for me.

walesmd - 07 August 2007 01:18 AM

I think the worse part of it all is - so many people think scaffolding is a basis for their application. It’s not!

To be honest, it could be removed and would save a lot of posts from occurring here on the forums. I am curious as to how many people actually use it - I’ve never seen it before, phpMyAdmin or the MySQL command line are more than enough for me.

I think this type of attitude lends itself to the “Rails” phenomenon more than anything else. I should know cuz I learned my rails_fu through their hit book “Agile Web Development with Rails” a great book IMHO but it espouses the use of scaffolding as a main tool for CRUD. Although in fairness there are Rails gurus that don’t practice the “CRUD” approach.

I also started with Rails with the same book - thankfully I was also working through various websites that weren’t designed in an “OMG get me to the end result as quickly as possible to show me how cool Rails is but not really teach me anything” mentality.

One of these sites, and I can’t remember a URL or anything (sorry), stressed the fact that you should ignore the scaffolding and develop it all yourself. It was the best move I made in learning Rails, especially since I’m the type of person that wants to understand how everything works.

You cannot use scaffolding to develop a public application - it’s poor design/planning - and in the long run you, or your clients, will suffer because of it.

Lets make sure we let the newbies know about the difference in Rails scaffolding and CI scaffolding.

In CI => scaffolding is the term they used for quick database access.

In Rails => scaffolding is a commandline script to quickly create your skeletin module with a couple of words on the prompt.

Hope this helps with any confusion.

walesmd - 07 August 2007 02:25 PM

I also started with Rails with the same book - thankfully I was also working through various websites that weren’t designed in an “OMG get me to the end result as quickly as possible to show me how cool Rails is but not really teach me anything” mentality.

One of these sites, and I can’t remember a URL or anything (sorry), stressed the fact that you should ignore the scaffolding and develop it all yourself. It was the best move I made in learning Rails, especially since I’m the type of person that wants to understand how everything works.

You cannot use scaffolding to develop a public application - it’s poor design/planning - and in the long run you, or your clients, will suffer because of it.

“OMG get me to the end result as quickly as possible to show me how cool Rails is but not really teach me anything”

I agree, CI isnt meant to write itself.

There are plenty of things out there that do write alot of the code for you such as Rapyd and CodeCrafter. If people want a system and dont want to write any code, dont waste everyones time by bitching on here… hire me! :p