PHP open source software 'Personal Management System' - Technical Specifications

Introduction

To make this open source system, I have never made development documents. I feel sorry for everyone. Today I will write down the technical specifications.

Directory structure

Access method

http://localhost/index.php?r=module name_controller name_method or http://localhost/index.php?module=module name&c/ p>

The default value is: module name: Default, controller name: Page, method name: index

Naming convention

1) Class files are all suffixed with .class.php, named using camel case, and the first letter capital.

2) The class name should reflect the file path

3) The core file should be placed under the lib/Core/ directory. At this time, you do not need to require the files in it, just use it directly.

4) Use lowercase letters and underscores when naming functions

5) Use camel case when naming methods, such as validClientIp, and use underscore '_' for private methods, such as _insertIP().

6) Constants are named with uppercase letters and underscores, such as DB_HOST.

7) There is no mandatory standard for naming internal variables, you can name them according to personal preference. However, I personally recommend that we use the camel case method for method parameter variables, and use lowercase letters and underscores to name internal parameters.

For example:

<ol>
<li><span><span>public</span><span> </span><span>function</span><span> validAcount(</span><span>$userName</span><span>){  </span></span></li>
<li><span> </span></li>
<li>
<span>$user_name</span><span> = </span><span>$userName</span><span>;  </span>
</li>
<li><span>} </span></li>
</ol>

8) The template file has the .tpl suffix.

9) Data tables and fields are named in lowercase and underlined. For example, the field create_date of hh_ip

Development requirements

1) It is best to use PDO for MySQL operations because of its higher security and performance.

2) Every database read operation is expected to be verified using explain to confirm that it hits the index.

Open the log

Check the log

Check whether the index is hit

3) For inner join, it is recommended to use up to 2 tables. If there are more than 2, it is recommended to use multiple short select statements.

4) Try to write comments in English. One is to cultivate everyone’s English ability; the other is to improve everyone’s naming ability.

Summary

Welcome everyone to come and develop together. In addition to creating good products, developing this project is mainly for technical exchanges and to see everyone's good technology. If you have better specifications or methods, you might as well tell me one or two.

QQ group: 152448006

Address:

Original link: http://www.cnblogs.com/baochuan/archive/2012/09/09/2677214.html

【Editor recommendation】

1. PHP "Personal Management System" hopes everyone can work together to develop the perfect login module for PHP "Personal Management System"
2. A French programmer living in China talks about Python and PHP
3. What do you need to become a programmer? Skills
4. What kind of changes has programming given us
The above introduces the technical specifications of the PHP open source software "Personal Management System", including the content of open source software and management systems. I hope it will be helpful to friends who are interested in PHP tutorials.