blocks|key|2479159|text|您可能会发现，在框架内工作意味着您只需要自己创建一些组件，并且有大量的最佳实践示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2479160|我从过程到Zend框架，这是一个很好的框架，包括一个完整的MVC模型，它有助于明确定义您的不同对象应该做什么，以及它们是如何结合在一起的。|offset|length|2479161|这可能是一个学习曲线，但过了一段时间，它比程序的东西更有意义！|2479162|entityMap|0|LINK|mutability|MUTABLE|url|http://framework.zend.com/^0|0|5|6|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

You might find that working within a framework means that you're only creating some of the components yourself and that there are plenty of examples of best practice.

I moved from procedural stuff to <a href="http://framework.zend.com/" rel="nofollow">Zend Framework</a> which is a great framework and includes a full MVC model which helps to clearly define what your different objects should do and how they all fit together.

It's likely to be a bit of a learning curve but after a while it makes so much more sense than procedural stuff!

blocks|key|1282839|text|使用一个面向对象的MVC框架，比如CodeIgniter+(非常容易)，Yii+(更难)，或者CakePHP或Symfony+(更难)。您可以看到不同的对象如何相互链接，以及使用它们的好处。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1282840|类的一个很好的例子是“表单”、“验证”和“模式”之间的交互。您可以通过传递一个模式来实例化一个表单，然后使用“form”中的方法生成HTML，而不必一遍又一遍地写它。当用户提交表单时，可以使用“Validation”类的实例化来验证每个字段，然后使用“Model”将其写入数据库。数据库中的每个表都有一个“模型”，它定义了如何将数据写入数据库(CRUD)并从数据库中检索数据。|1282841|您可以避免使用大量的需求，包括使用'__autoload()‘。|1282842|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Use an object-oriented MVC framework like CodeIgniter (which is very easy), Yii (bit harder), or CakePHP or Symfony (much harder). You can see how the different objects link to each other, and the benefits from using them.

A good example of classes is the interaction between 'Form', 'Validation' and 'Schema'. You can instantiate a form by passing it a schema, and then use methods in 'Form' to generate HTML without writing it over and over again. When a user submits the form, you validate each field using an instantiation of the 'Validation' class, and then write it to the database using a 'Model'. Each table in your database has a 'Model' which defines how data is written to and retrieved from the database (CRUD).

You can avoid using lots of requires and includes using '__autoload()'.

blocks|key|2838304|text|你有问题，这是我的答案！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2838305|您在PHP中创建的类可以与用户、Book等对象相关，就像在持久性程序中所做的那样。如果您查看像码点火器这样的框架，您可以使一个类具有特定的特性，比如将数据库查询构造为一个类，该类使用由多个类组成的MVC体系结构来呈现整个网站。|ordered-list-item|offset|length|2838306|例如，为了减少代码重复，您可以编写一个类来构造一个表(或者如果您真的喜欢div表生成器的话)。然后您可以编写诸如makeRow()、makeDivision()等方法.变得非常漂亮，然后您可以编写干净的PHP代码，这些代码可以生成非常大的强大页面。|2838307|编辑|style|BOLD|2838308|如果你说的是减少包含的数量，那么是的，自动修整课网站上的内容是你想要看到的！|2838309|您的网站结构可以基于您想要使用的模型。现在看来，MVC模型在框架中很受欢迎，但这取决于您希望如何制作您的web应用程序。我相信你可以采取任何建筑模型，并建立你的网站围绕它。|2838310|尽管如此，如果您不想从项目中从头开始，那么就有太多的PHP框架可供选择：|2838311|维基百科Web应用框架的比较:+PHP|2838312|entityMap|0|LINK|mutability|MUTABLE|url|http://codeigniter.com/|1|http://php.net/manual/en/language.oop5.autoload.php|2|http://en.wikipedia.org/wiki/Model%25E2%2580%2593view%25E2%2580%2593controller|3|http://en.wikipedia.org/wiki/Comparison_of_Web_application_frameworks#PHP^0|0|1B|4|0|0|0|0|2|0|J|5|1|0|O|3|2|0|0|4|F|3|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|19|8|@]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|G|3|H|5|D|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1E|8|@$E|1F|F|1G|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1H|8|@]|9|@$E|1I|F|1J|1|1K]]|A|$]]|$1|O|3|P|5|D|7|1L|8|@]|9|@$E|1M|F|1N|1|1O]]|A|$]]|$1|Q|3|R|5|6|7|1P|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Q|8|@]|9|@$E|1R|F|1S|1|1T]]|A|$]]|$1|U|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]|14|$5|X|Y|Z|A|$10|15]]|16|$5|X|Y|Z|A|$10|17]]]]

You have questions, here are my answers!

<ol>
<li>The classes you make in PHP can be related to objects like User, Book as you would do in a persistent program. If you look at a framework like <a href="http://codeigniter.com/" rel="nofollow">Code Igniter</a> you can make a class as specific as constructing database queries to a class that uses an MVC architecture consisting of multiple classes to render your entire website.</li>
<li>To reduce code duplication, you can, for example, write a class to construct a table (or if you are really fancy a div table maker.). Then you can write methods like makeRow(), makeDivision(), etc... get really fancy and then you can write clean PHP code that can generate really large powerful pages.
 
EDIT: 
If you were talking about reducing about the amount of include you'd have to do for classes then yes, <a href="http://php.net/manual/en/language.oop5.autoload.php" rel="nofollow">Autoloading Classes</a> on the PHP website is something you will want to look at!</li>
<li>Structure of your website can be based on the model you want to use. Right now it seems that <a href="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="nofollow">MVC</a> models are popular with frameworks, but it is up to you how your want your web app to be made. I'm sure you can take any architecture model and base your website around it. 
 
With all that said, if you don't feel like start from absolute scratch on your project there are a plethora of PHP frameworks to choose from:
 <a href="http://en.wikipedia.org/wiki/Comparison_of_Web_application_frameworks#PHP" rel="nofollow">Comparison of Web application frameworks: PHP</a> via Wikipedia</li>
</ol>

blocks|key|2479307|text|这取决于你想要完成什么。在一个相对复杂的web应用程序中，您可以遵循一个典型的MVC方法。在该场景中，您可以创建至少两个类，一个用于模型，另一个用于控制器。然后有几个模板(普通PHP文件)，其内容由控制器填充/完成。您可以创建更多的类(表单、实用程序、代码生成器、..)根据需要，但要注意保持代码的紧凑性和易于实现。|type|ordered-list-item|depth|inlineStyleRanges|entityRanges|offset|length|data|2479308|许多框架依赖于__autoload()神奇的方法。另一种选择是构建处理所有这些事情的机制，可能使用AutoLoader类。|style|CODE|2479309|使用框架。我是认真的。或者至少以一个框架为例。我推荐CakePHP或CodeIgniter，因为它们的fil结构简单。|2479310|unstyled|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Model%25E2%2580%2593view%25E2%2580%2593controller|1|http://cakephp.org/|2|http://codeigniter.com/^0|13|5|0|0|7|C|1D|A|0|Q|7|1|Y|B|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]|$A|13|B|14|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]|$A|19|B|1A|1|1B]]|C|$]]|$1|J|3|-4|5|K|7|1C|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]|U|$5|N|O|P|C|$Q|V]]]]

<ol>
<li>It depends on what you want to accomplish. In a relatively complex web application you could follow a typical <a href="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller" rel="nofollow">MVC approach</a>. In that scenario you can create at least two classes, one for the model and one for the controller. And then have several templates (plain PHP files) whose content are filled/completed by the controller. You can create more classes (forms, utilities, code-generators,..) as needed, but be careful to keep your code compact and easy to mantain.</li>
<li>Many frameworks rely on the <code>__autoload()</code> magic method. Another alternative is to build your mechanism to handle all this stuff, probably using an <code>AutoLoader</code> class.</li>
<li>Use a framework. Seriously. Or at least take a framework as an example. I recommend <a href="http://cakephp.org/" rel="nofollow">CakePHP</a> or <a href="http://codeigniter.com/" rel="nofollow">CodeIgniter</a> due to their fil structure simplicity.</li>
</ol>

blocks|key|2838394|text|MVC模式本质上是web应用程序的事实模式，不管语言如何。有几个框架使用这种模式，包括Zend、CodeIgniter和Kohana。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2838395|就像其他人说的那样，__autoload()或spl_autoload_register()是消除遵循包含/需求的需要的方法。|2838396|请记住，OOP的货币是对象。如果您只是简单地将一些后端数据转换为OO模型并将其称为“一天”，那么您将不会获得什么好处。我建议您看Matt的“PHP+5:对象、模式和实践”，以及“四人帮的设计模式:可重用的面向对象软件的元素”，以真正了解如何在整个项目中使用对象。|offset|length|style|BOLD|2838397|entityMap^0|0|0|B|2|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@$F|O|G|P|H|I]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

The MVC pattern is essentially the de facto pattern for web apps, regardless of language. Several frameworks utilize this pattern, including Zend Framework, CodeIgniter, and Kohana.

Like the others have said, __autoload() or spl_autoload_register() is the way to go when it comes to eliminating the need to follow includes/requires.

Remember that the currency of OOP is objects. You're not gaining much if you simply turn some back end data into OO models and calling it a day. I suggest you look at Matt Zandstra's book PHP 5: Objects, Patterns, and Practice as well as the Gang of Four's Design Patterns: Elements of Reusable Object-Oriented Software to really see how to use objects throughout a project.

blocks|key|2838443|text|这是一个非常有趣的问题，它让我们回到了一个由来已久的关于过程编程与面向对象编程的争论。为什么选一个或另一个？is..nobody的答案有一个。软件设计的全部目的是完成一些事情。你怎么到那里有关系吗？那得看情况了。如果你非常草率地到达那里，并且需要进行大量的更新，那就是浪费时间。OO编程能阻止这种情况吗？绝对不是。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2838444|看起来你真正的问题是如何将面向对象集成到一个网站中。这真的不是你应该为它做的事情。你想用这个网站做些什么？它是否包含FSM中有用户交互的许多不同的应用程序状态，还是仅仅是一堆静态页面。这些页面共享了多少信息？|2838445|让我们先回答你的具体问题：|2838446|一个人通常创建什么类型的类？他们想要的任何类型的课程！在键入一个代码字符之前，您应该坐下来为您的应用程序编写一个设计。没有人能告诉你如何做到这一点:编写一些文档、伪代码(即使是在php中，如果你愿意)、绘制一个UML图等等。不要犯基于现实世界(用户、书籍)的逻辑分离来划分对象的错误，除非它是有意义的。为什么你需要一个Book对象？它是如何与用户交互的？|ordered-list-item|2838447|您可以构建一个非常简单的类来显示您的标准网页：|2838448|class+anypage+{
+++public+function+header()+{
++++++return+'<head></head>';
+++}
+++public+function+footer()+{
++++++return+'<br+/>Copyright+&copy;+'+.+date('Y');
+++}
+++public+function+render($body)+{
++++++return+'<html>'+.+$this->header()+.+"<body>$body{$this->footer()}</body></html>";
+++}
}|code-block|syntax|javascript|2838449|然后在任何页面调用：|2838450|$page+=+anypage;
echo+$page->render("My+Page+Content");|2838451|无论如何，我说的不仅仅是PHP，而是一般的OO原则，但这是一个无法回答的问题。您设计了应用程序完成工作所需的类。在PHP中使用对象的一个很好的例子是菲他尔，一种模板语言。您的网页可能如下所示：|offset|length|2838452|$page+=+new+PHPTAL('mytemplate.xhtml');
echo+$page->execute();|2838453|PHPTAL类负责从模板文件构建html。这就是一个对象可能被用来做什么的例子。|2838454|当然，PHPTAL是巨大的，它被分解成很多的隔间。看看源代码，我们看到了Attr、Element、Node等类。这些都是xml文档的一部分，它们有一个类来表示它们。|2838455|OOP的一个重要部分是让对象一起工作。每个对象都应该有一个目的，并做它擅长的事情。我不喜欢像“用户”或“书”这样的名词的模型对象，除非它们能做些什么。PHPTAL在为页面呈现视图方面做得很好，但是如何知道要呈现哪个页面呢？您可以使用一个对象来处理这个问题：|2838456|class+controller+{
+++public+function+__call($_,+$_)+{+return+$this->hello();+}
+++public+function+hello()+{
++++++session_start();
++++++$view+=+new+PHPTAL('hello.xhtml');
++++++return+$view->execute();
+++}
+++public+function+goodbye()+{
++++++session_destroy();
++++++$_SESSION+=+array();
++++++$view+=+new+PHPTAL('goodbye.xhtml');
++++++return+$view->execute();
+++}
}|2838457|在你的主页上，你会：|2838458|$c+=+new+controller;
echo+$c->$_REQUEST['action']();|2838459|如果请求设置了“action”，则控制器通过调用该操作进行相应的响应。hello默认使用，这要归功于神奇的__call()。|style|CODE|2838460|与您熟悉的其他OO语言类似，您甚至可以在PHP中使用事件：|2838461|class+controller+{
+++private+$models+=+array();
+++private+$_listeners+=+array();
+++public+function+__construct()+{
++++++$model+=+new+model;
++++++$this->models[]+=+$model;
++++++$this->_listeners[]+=+$model;
+++}

+++public+function+action($action+=+'hello',+$events+=+array())+{
++++++$this->$action();
++++++foreach+($events+as+$type+=>+$data)+{
+++++++++foreach+($this->_listeners+as+$listener)+{
++++++++++++$event+=+"fire_"+.+$type;
++++++++++++$listener->$event($data);
+++++++++}
++++++}
+++}
}

class+model+{
+++public+function+fire_hello($name)+{
++++++echo+'hello+'+.+$name;
+++}
}|2838462|正如其他答案所暗示的，一个好的开端是看看一个PHP框架。我推荐科哈纳，因为它是一个很好的OO框架。我并不一定建议您从它构建一个网站，但请查看文档和代码，以便更好地理解面向PHP的OO开发。|2838463|2+菲他尔或其他模板引擎是减少html复制的一种很棒的方法。即使是我上面的小型anypage类也是一个例子。您不必有一个html文件，然后使用require()、include()或virtual()将其传递到代码中以供重用。相反，您可以使用一个包装器来存储和构建通用模板html。为此，我再怎么强调我有多爱PHPTAL。XSLT是另一种选择。|2838464|3没有固定的方法去做这件事。其他人则建议“使用一个框架”。我不一定不同意。使用框架在处理一些烦人的设置事务方面有很大帮助。它不是一个神奇的问题解决安慰剂，但它是很好的一些事情。如果你只是试着学习，而且没有时间限制，我想写你自己的框架。这肯定会教你如何用PHP进行OO编程。如果时间是个问题，请使用其他人建议的500,000个框架中的一个。至于如何构造您的网站，我倾向于有一个用于javascript的_js文件夹和一个用于样式表的_stylesheets文件夹。我使用的所有php和xhtml模板文件都放在逻辑上属于它们的文件夹中。这不是火箭科学，而是软件工程！|2838465|entityMap|0|LINK|mutability|MUTABLE|url|http://phptal.org/|1|http://kohanaframework.org/|2^0|0|0|0|0|0|0|0|0|22|3|0|0|0|0|0|0|0|0|0|Z|5|1H|8|0|0|0|V|3|1|0|13|7|1Z|9|29|9|2J|9|2|3|2|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|22|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|23|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|24|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|25|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|26|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|27|8|@]|9|@]|A|$N|O]]|$1|T|3|U|5|6|7|28|8|@]|9|@$V|29|W|2A|1|2B]]|A|$]]|$1|X|3|Y|5|M|7|2C|8|@]|9|@]|A|$N|O]]|$1|Z|3|10|5|6|7|2D|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2E|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2F|8|@]|9|@]|A|$]]|$1|15|3|16|5|M|7|2G|8|@]|9|@]|A|$N|O]]|$1|17|3|18|5|6|7|2H|8|@]|9|@]|A|$]]|$1|19|3|1A|5|M|7|2I|8|@]|9|@]|A|$N|O]]|$1|1B|3|1C|5|6|7|2J|8|@$V|2K|W|2L|1D|1E]|$V|2M|W|2N|1D|1E]]|9|@]|A|$]]|$1|1F|3|1G|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1H|3|1I|5|M|7|2P|8|@]|9|@]|A|$N|O]]|$1|1J|3|1K|5|6|7|2Q|8|@]|9|@$V|2R|W|2S|1|2T]]|A|$]]|$1|1L|3|1M|5|6|7|2U|8|@$V|2V|W|2W|1D|1E]|$V|2X|W|2Y|1D|1E]|$V|2Z|W|30|1D|1E]|$V|31|W|32|1D|1E]]|9|@$V|33|W|34|1|35]]|A|$]]|$1|1N|3|1O|5|6|7|36|8|@]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|37|8|@]|9|@]|A|$]]]|1Q|$1R|$5|1S|1T|1U|A|$1V|1W]]|1X|$5|1S|1T|1U|A|$1V|1Y]]|1Z|$5|1S|1T|1U|A|$1V|1W]]]]

A very interesting question that brings us back to the age-old debate of procedural vs. OO programming. Why pick one or the other? The answer is..nobody has one. The whole purpose of designing software is to get something done. Does it matter how you get there? Well, it depends. If you get there very sloppily and a lot of updates are required, that's a big waste of time. Does OO programming prevent this? Absolutely not.

It seems like your real question is how to integrate OO into a website. This is really not something that you should do for the heck of it. What are you trying to achieve with this website? Does it contain many different application states with user interaction in a FSM or is it just a bunch of static pages. How much information do these pages share?

Let's tackle your specific questions first:

<ol>
<li>What type of classes does one usually create? Whatever type of classes they want! Before you type one character of code, you should sit down and write out a design for your application. No one can tell you how to do this: write up some documentation, pseudo-code (even in php if you like), draw up a UML diagram, etc. Figure out how your application can be compartmentalized. Do not make the mistake of dividing up object based on their logical separation in the real world (User, Book) unless it makes sense to. Why do you need a Book object? How does it interact with a user?</li>
</ol>

You could build a very simple class to display your standard webpage:

<pre><code>class anypage {
 public function header() {
 return '&lt;head&gt;&lt;/head&gt;';
 }
 public function footer() {
 return '&lt;br /&gt;Copyright &amp;copy; ' . date('Y');
 }
 public function render($body) {
 return '&lt;html&gt;' . $this-&gt;header() . "&lt;body&gt;$body{$this-&gt;footer()}&lt;/body&gt;&lt;/html&gt;";
 }
}
</code></pre>

Then on any page call:

<pre><code>$page = anypage;
echo $page-&gt;render("My Page Content");
</code></pre>

Anyway, I'm talking more about general OO principles than just PHP, but this is a question that can't be answered. You design classes that your application needs to get the job done. A good example of using an object in PHP is <a href="http://phptal.org/" rel="nofollow">PHPTAL</a>, a template language. Your webpage may look like this:

<pre><code>$page = new PHPTAL('mytemplate.xhtml');
echo $page-&gt;execute();
</code></pre>

The PHPTAL class takes care of building the html from your template file. That's an example of what an object might be used for.

Of course, PHPTAL is huge, and it's broken down into a lot of compartments. Taking a look at the source code, we see the classes Attr, Element, Node .. these are all pieces of an xml document and they have a class representing them.

An important part of OOP is having objects work together. Each object should serve a purpose and do what it is good at. I don't like objects that are models for nouns like "User" or "Book," unless they do something. PHPTAL does a great job of rendering a view for your page, but how do you know which page to render? You can use an object to handle that:

<pre><code>class controller {
 public function __call($_, $_) { return $this-&gt;hello(); }
 public function hello() {
 session_start();
 $view = new PHPTAL('hello.xhtml');
 return $view-&gt;execute();
 }
 public function goodbye() {
 session_destroy();
 $_SESSION = array();
 $view = new PHPTAL('goodbye.xhtml');
 return $view-&gt;execute();
 }
}
</code></pre>

On you main page, you would have:

<pre><code>$c = new controller;
echo $c-&gt;$_REQUEST['action']();
</code></pre>

If the 'action' is set by the request, the controller responds accordingly by calling that action. <code>hello</code> is used by default thanks to magical <code>__call()</code>.

Similar to the other OO languages you are familiar with, you can even have events in PHP:

<pre><code>class controller {
 private $models = array();
 private $_listeners = array();
 public function __construct() {
 $model = new model;
 $this-&gt;models[] = $model;
 $this-&gt;_listeners[] = $model;
 }

 public function action($action = 'hello', $events = array()) {
 $this-&gt;$action();
 foreach ($events as $type =&gt; $data) {
 foreach ($this-&gt;_listeners as $listener) {
 $event = "fire_" . $type;
 $listener-&gt;$event($data);
 }
 }
 }
}

class model {
 public function fire_hello($name) {
 echo 'hello ' . $name;
 }
}
</code></pre>

As other answers have suggested, a good start is to take a look at a PHP framework. I recommend <a href="http://kohanaframework.org/" rel="nofollow">Kohana</a>, since it is a good OO framework. I'm not necessarily suggesting you build a website from it, but take a look at the documentation and code to get a better understanding of OO development for PHP.

2 <a href="http://phptal.org/" rel="nofollow">PHPTAL</a> or another templating engine is an awesome way to reduce html duplication. Even my miniature <code>anypage</code> class above is an example. You don't necessarily have to have an html file and then use <code>require()</code> <code>include()</code> or <code>virtual()</code> to pass it into your code for reuse. Instead, you can have a wrapper that stores and builds common template html. I cannot stress enough how much I love PHPTAL for this purpose. XSLT is an alternative.

3 There is no set way to do this. Others are suggesting "Use a framework." I don't necessarily disagree. Using a framework helps out a lot in taking care of some of the annoying business of setting things up. It's not a magic problem-solving placebo, but it is nice for some things. If you are just trying to learn and there is no constraint on time, I say write your own framework. That will definitely teach you about OO programming in PHP. If time is a concern, use one of the 500,000 frameworks out there that others are suggesting. As for how to structure your website, I tend to have a _js folder for javascript and a _stylesheets folder for stylesheets. All of the php and xhtml template files I use are just placed in the folders they belong to logically. It's not rocket science, it's software engineering!

I'm very new to PHP so far and have been trying to learn it. A big difficulty I face though is I just can't bend my head around to think about how is a PHP website structured with classes, objects, namespaces.

I'm not entirely new to OOP as I do have a little experience in Python and Java but PHP OOP just got me stumped. Many of the newbie PHP books I saw were on procedural PHP. I followed them made 1--2 small website but when I got to OOP, I'm just stuck and any tips on how you made the transition from procedural to OO PHP would be appreciated. In particular these are the questions on my mind at this moment

<ol>
<li>What are the type of classes one would usually creates? I thought of giving a class for each table in my database (User, Book) as well as maybe a form class, are there any other type of candidates that could be turned into classes too?</li>
<li>Any other way to reduce html code duplication other than the old usual require() and include()?</li>
<li>Any recommended ways to structure a typical PHP website? I currently only knows of having a folder for includes file. But I would like to know more.</li>
</ol>

Thanks.

OOP PHP Confusion, transition from procedural to OO PHP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

到目前为止，我对PHP非常陌生，并且一直在努力学习它。不过，我面临的一个大困难是，我无法低下头来思考PHP网站是如何由类、对象、名称空间构成的。我对OOP并不完全陌生，因为我在Python和Java方面确实有一些经验，但是PHP只是让我感到困惑。我看到的许多新手PHP书籍都是关于过程PHP的。我跟踪他们做了1-2个小网...

问OOP PHP混淆，从过程到OO PHP的过渡
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OOP PHP混淆，从过程到OO PHP的过渡EN