Comments on: Build Your Portfolio With CodeIgniter http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/ Musings, Insights, and Ramblings of a Seattle Web Developer Sun, 24 Jan 2010 14:31:32 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: David Coe http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-626 David Coe Sun, 24 Jan 2010 14:31:32 +0000 http://andrewwoods.net/blog/?p=233#comment-626 Thank you for publishing this. It's given me a very useful and different insight into CodeIgniter. As a total beginner to the subject I found a couple of parts of your tutorial confusing and missing. Hopefully a couple of amendments will help other beginners on their way. (1) You ask to save the first file as Main.php. I found when doing this the file wasn't found. Dropping the capital letter and renaming it to main.php solved this error. (2) You make no reference to create another view .php file for the detailed client page. A file called 'work_client' needs to be created in the 'views' directory. This contains the php echo statements. (3) It's probably worth noting that foo and bar in the array are the client names. and that to test everything is working they should visit either example.com/index.php/work/client/foo or example.com/index.php/work/client/bar I know some of this is elementary but this makes the tutorial appeal to a wider demographic. Good work on the tutorial. I found it very useful... Thank you for publishing this. It’s given me a very useful and different insight into CodeIgniter.

As a total beginner to the subject I found a couple of parts of your tutorial confusing and missing. Hopefully a couple of amendments will help other beginners on their way.

(1) You ask to save the first file as Main.php. I found when doing this the file wasn’t found. Dropping the capital letter and renaming it to main.php solved this error.

(2) You make no reference to create another view .php file for the detailed client page. A file called ‘work_client’ needs to be created in the ‘views’ directory. This contains the php echo statements.

(3) It’s probably worth noting that foo and bar in the array are the client names. and that to test everything is working they should visit either example.com/index.php/work/client/foo or example.com/index.php/work/client/bar

I know some of this is elementary but this makes the tutorial appeal to a wider demographic.

Good work on the tutorial. I found it very useful…

]]> By: David Coe http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-625 David Coe Sun, 24 Jan 2010 14:31:02 +0000 http://andrewwoods.net/blog/?p=233#comment-625 Thank you for publishing this. It's given me a very useful and different insight into CodeIgniter. As a total beginner to the subject I found a couple of parts of your tutorial confusing and missing. Hopefully a couple of amendments will help other beginners on their way. (1) You ask to save the first file as Main.php. I found when doing this the file wasn't found. Dropping the capital letter and renaming it to main.php solved this error. (2) You make no reference to create another view .php file for the detailed client page. A file called 'work_client' needs to be created in the 'views' directory. This contains the php echo statements. (3) It's probably worth noting that foo and bar in the array are the client names. and that to test everything is working they should visit either example.com/index.php/work/client/foo or example.com/index.php/work/client/bar I know some of this is elementary but this makes the tutorial appeal to a wider demographic. Good work on the tutorial. I found it very useful. Thank you for publishing this. It’s given me a very useful and different insight into CodeIgniter.

As a total beginner to the subject I found a couple of parts of your tutorial confusing and missing. Hopefully a couple of amendments will help other beginners on their way.

(1) You ask to save the first file as Main.php. I found when doing this the file wasn’t found. Dropping the capital letter and renaming it to main.php solved this error.

(2) You make no reference to create another view .php file for the detailed client page. A file called ‘work_client’ needs to be created in the ‘views’ directory. This contains the php echo statements.

(3) It’s probably worth noting that foo and bar in the array are the client names. and that to test everything is working they should visit either example.com/index.php/work/client/foo or example.com/index.php/work/client/bar

I know some of this is elementary but this makes the tutorial appeal to a wider demographic.

Good work on the tutorial. I found it very useful.

]]> By: Nick Yeoman http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-623 Nick Yeoman Fri, 20 Nov 2009 22:55:15 +0000 http://andrewwoods.net/blog/?p=233#comment-623 You forgot the most important part that differentiates CI to other frameworks: documentation! You forgot the most important part that differentiates CI to other frameworks: documentation!

]]> By: drew http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-620 drew Sat, 24 Oct 2009 01:50:27 +0000 http://andrewwoods.net/blog/?p=233#comment-620 Nice work, most tutorials seem to push a programatic approach as opposed to a functional one - thinking about it from the view or presentation side as opposed to "this is a controller, this is a model, this is a view" and getting lost. Nice work, most tutorials seem to push a programatic approach as opposed to a functional one – thinking about it from the view or presentation side as opposed to “this is a controller, this is a model, this is a view” and getting lost.

]]> By: Montana Flynn http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-615 Montana Flynn Mon, 31 Aug 2009 18:36:39 +0000 http://andrewwoods.net/blog/?p=233#comment-615 I am in the process of trying to put together my online portfolio with CodeIgnitor. Definitely a new way of thinking for a designer like me. Great tutorial, thanks! I am in the process of trying to put together my online portfolio with CodeIgnitor. Definitely a new way of thinking for a designer like me. Great tutorial, thanks!

]]> By: url directory http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-610 url directory Thu, 11 Jun 2009 08:13:47 +0000 http://andrewwoods.net/blog/?p=233#comment-610 Nice i too will try 2 Build my Portfolio With CodeIgniter, if any problems wil ask you Nice i too will try 2 Build my Portfolio With CodeIgniter, if any problems wil ask you

]]> By: Andrew Woods http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-609 Andrew Woods Thu, 11 Jun 2009 00:32:46 +0000 http://andrewwoods.net/blog/?p=233#comment-609 @natebot Thanks! The use of routes is a nice feature and it's not always obvious to new CI users. I like features that are elegant, as they usually lead to more concise code. @natebot Thanks! The use of routes is a nice feature and it’s not always obvious to new CI users. I like features that are elegant, as they usually lead to more concise code.

]]> By: natebot http://andrewwoods.net/blog/2009/06/10/build-your-portfolio-with-codeigniter/comment-page-1/#comment-608 natebot Wed, 10 Jun 2009 23:34:40 +0000 http://andrewwoods.net/blog/?p=233#comment-608 Nice introduction. Good choice I think on the routing urls to a single controller for a small site. I find there is a balancing act to play between intuitive urls, slim and fast loading controller files, and ease of maintaining/extending your code. The routing class certainly helps mediate that. Nice introduction.

Good choice I think on the routing urls to a single controller for a small site.

I find there is a balancing act to play between intuitive urls, slim and fast loading controller files, and ease of maintaining/extending your code. The routing class certainly helps mediate that.

]]>