Comments on: My Perfect PHP Framework http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/ We Do Web Things Tue, 23 Aug 2011 21:51:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: massunu http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-4376 massunu Tue, 20 Feb 2007 08:40:54 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-4376 CakePHP ... saya juga make nih. Silahkan berkunjung jg ke : http://sunu.co.nr/tag/cakephp/ Smoga bermanfaat .. CakePHP … saya juga make nih. Silahkan berkunjung jg ke :

http://sunu.co.nr/tag/cakephp/

Smoga bermanfaat ..

]]> By: Mitz http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-2163 Mitz Wed, 20 Dec 2006 05:14:08 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-2163 Mine is CodeIgniter. Nice and easy to learn for just watching its video. Two thumbs up with CodeIgniter. Mine is CodeIgniter. Nice and easy to learn for just watching its video.

Two thumbs up with CodeIgniter.

]]> By: What Is Php http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-294 What Is Php Wed, 22 Nov 2006 17:21:12 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-294 <strong>Dave...</strong> Interesting topic... I'm working in this industry myself and I don't agree about this in 100%, but I added your page to my bookmarks and hope to see more interesting articles in the future... Dave…

Interesting topic… I’m working in this industry myself and I don’t agree about this in 100%, but I added your page to my bookmarks and hope to see more interesting articles in the future…

]]> By: charliez http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-72 charliez Thu, 19 Oct 2006 21:55:25 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-72 My favorite is QCodo and to supplement it I use Qooxdoo and Dojo to do AJAX stuff faster and easier.... try them you will like them to!! My favorite is QCodo and to supplement it I use Qooxdoo and Dojo to do AJAX stuff faster and easier…. try them you will like them to!!

]]> By: Kalileo http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-66 Kalileo Tue, 17 Oct 2006 04:57:52 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-66 Well, we looked at ROR and python`s Turbogear, but then we did stumble over CakePHP (http://cakephp.org). CakePHP was a kind of ROR clone when it started, but now it is much more than that. We did choose it over ROR simply because it is for us, especially since 1.0, <strong>better and faster to get real results, real applications</strong> <i>(and not just a little toy demo app)</i>, and <strong>very much alive</strong> and progressing. Examining its code shows that it is a <strong>very clean OO code.</strong> Codeigniter and similar do not reach the level of it. We use CakePHP now for all projects, and ported some multithousand line web applications to it, and are <strong>very happy</strong> with the result. Another plus is the friendly and fast support in the <strong>#cakephp IRC</strong> channel and in the google group. So for us, not just in theory and after scanning a introduction text on the website, <strong>"My Perfect PHP Framework" is CakePHP !</strong> Well, we looked at ROR and python`s Turbogear, but then we did stumble over CakePHP (http://cakephp.org).

CakePHP was a kind of ROR clone when it started, but now it is much more than that.

We did choose it over ROR simply because it is for us, especially since 1.0, better and faster to get real results, real applications (and not just a little toy demo app), and very much alive and progressing. Examining its code shows that it is a very clean OO code.

Codeigniter and similar do not reach the level of it.

We use CakePHP now for all projects, and ported some multithousand line web applications to it, and are very happy with the result.

Another plus is the friendly and fast support in the #cakephp IRC channel and in the google group.

So for us, not just in theory and after scanning a introduction text on the website, "My Perfect PHP Framework" is CakePHP !

]]> By: Sebbie http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-62 Sebbie Sun, 15 Oct 2006 23:32:34 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-62 My favorite would be Codeigniter it's like ROR My favorite would be Codeigniter it’s like ROR

]]> By: shyboy http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-50 shyboy Thu, 12 Oct 2006 11:22:38 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-50 My favorites framework are Prado and Mojavi, but i like seagull so. My favorites framework are Prado and Mojavi, but i like seagull so.

]]> By: Dean http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/comment-page-1/#comment-41 Dean Wed, 11 Oct 2006 01:17:48 +0000 http://www.ngoprekweb.com/2006/10/10/my-perfect-php-framework/#comment-41 PHP is already a perfect Framework for simple projects even as a templating language :P The bad thing is that there is not a single convention in function naming, and parameter passing. I feel that frameworks are unnecessary unless you are building large projects or working together with other people. My personal choice for large sites and intranet apps is the <a href="http://www.akelos.org" rel="nofollow">Akelos Framework</a>, which matches all your observations but number one. Actually this could be done as in <a>Rails</a> by separating the three components in separated pieces M ActiveRecord, V ActionView and C ActionController which the creators might do in a future if someone asks them. <a href="http://framework.zend.com/" rel="nofollow">Zend Framework</a> seems to be a good choice for a large projects, but I think its far more complicated than Rails/Akelos plus Akelos plays nicely on l10n and i18n were all the other frameworks trend to fail. I had a look to Cake after playing with Rails and I found many differences and naming inconsistencies. For small stuff I do as you <a href="http://pear.php.net" rel="nofollow">PEAR</a>, raw PHP if I'm coding by myself and <a href="http://bermi.org/projects/sintags" rel="nofollow">Sintags</a> when collaborating with Dreamweaver designers (luckily not too often). When do you decide to use or not to use a Framework? Has anyone measured the effort that requires learning a whole new set of conventions, and ways of doing things? Is it really worth? Should we kill all PHP frameworks and move to <a>Ruby on Rails</a> and stop discussing about which one is the best? Should we push a little bit Akelos and hope it becomes the new PHP on Rails (they still on development preview) or we should all move to Zend and empower their solution as the standard? I really feel that the amount of <a href="http://www.phpwact.org/php/mvc_frameworks" rel="nofollow">available frameworks for PHP</a> is causing a big damage to the language itself. Motivating other (like me) to use Ruby whenever its possible. PHP is already a perfect Framework for simple projects even as a templating language :P
The bad thing is that there is not a single convention in function naming, and parameter passing. I feel that frameworks are
unnecessary unless you are building large projects or working together with other people.

My personal choice for large sites and intranet apps is the Akelos Framework, which
matches all your observations but number one. Actually this could be done as in Rails by
separating the three components in separated pieces M ActiveRecord, V ActionView and C ActionController which the creators
might do in a future if someone asks them.

Zend Framework seems to be a good choice for a large projects, but I think its far
more complicated than Rails/Akelos plus Akelos plays nicely on l10n and i18n were all the other frameworks trend to fail.

I had a look to Cake after playing with Rails and I found many differences and naming inconsistencies.

For small stuff I do as you PEAR, raw PHP if I’m coding by myself and Sintags when collaborating with Dreamweaver designers (luckily not too often).

When do you decide to use or not to use a Framework?
Has anyone measured the effort that requires learning a whole new set of conventions, and ways of doing things? Is it really
worth?
Should we kill all PHP frameworks and move to Ruby on Rails and stop discussing about which
one is the best?
Should we push a little bit Akelos and hope it becomes the new PHP on Rails (they still on development preview) or we should
all move to Zend and empower their
solution as the standard?

I really feel that the amount of available frameworks for PHP is
causing a big damage to the language itself. Motivating other (like me) to use Ruby whenever its possible.

]]>