简体繁体 English

具有强大命名约定的框架的优点

[英]Advantages of a framework with strong naming conventions

原文 2009-08-21 12:28:13 0 2 php/ cakephp/ frameworks/ naming-conventions

I know some PHP and now I'm the stage of choosing a framework. 我知道一些PHP，现在是选择框架的阶段。 After some diggs, I've find that CakePhp is a good choice. 经过一些挖掘后，我发现CakePhp是一个不错的选择。 After some manual/tutorial readings and trying some cakephp code samples I'm wondering myself about how good is the idea of naming convention used by CakePHP. 经过一些手册/教程的阅读并尝试了一些Cakephp代码示例之后，我想知道CakePHP使用的命名约定的概念有多好。

They are using the term: "convention over configuration". 他们使用的是术语：“约定之上的配置”。 What do you think about this (give me your pro/cons opinions )? 您对此有何看法（请给我您的赞成/反对意见）？

Many thanks. 非常感谢。

2 个解决方案

这意味着您只需要指定应用程序的非常规方面。

If you don't have any experiencie and you don't have the habit of use a naming convention maybe is a good choice. 如果您没有任何经验并且没有使用命名约定的习惯，也许是个不错的选择。 For me, always is good have some kind of convention in code and filenames. 对我来说，在代码和文件名中总是有某种约定是很好的。 And a framework with that philosophy like Ruby on Rails once you now the convention the development of your web app could be really fast. 有了Ruby on Rails之类的具有这种理念的框架，一旦您约定了Web应用程序的开发可能会非常快。 But for choose a framework there is another things that you should analyse. 但是对于选择框架，您还需要分析另一件事。 For example perfomance, realiability, resources in the web, etc. 例如性能，可实现性，网络资源等。