Kohana PHP5框架入门教程：简化Web开发

需积分: 3 175 浏览量更新于2024-08-02 收藏 319KB PDF 举报

"Kohana101 是一份关于Kohana PHP5框架的入门教程，它基于CodeIgniter开发，提供社区化的支持。本教程旨在帮助初学者理解和掌握Kohana框架的核心概念和用法。" 在Kohana框架中，开发者可以体验到PHP5的纯面向对象编程特性。Kohana的独特之处在于其轻量级、灵活且高效的设计，这使得它对那些已经使用过其他框架但觉得它们过于复杂或限制过多的开发者特别有吸引力。对于那些从未使用过框架，或者正在寻找替代现有框架（如Django、Rails、ASP.NET或Java）的开发者来说，Kohana也是一个值得考虑的选择。教程的章节包括： 1. **Overview**：这部分介绍Kohana是一个开源的PHP框架，用于构建Web应用。它强调了框架如何通过减少重复工作来提高开发效率，并概述了Kohana为何值得学习。 2. **Setup**：这部分指导读者如何安装和配置Kohana环境，包括设置服务器环境和下载框架的必要文件。 3. **Configuration**：详细讲解Kohana的配置文件和设置，如何自定义框架的行为以适应项目需求。 4. **ShowMe**：这部分可能会展示Kohana的基本用法，通过示例代码帮助理解框架的工作原理。 5. **Kohana Magic**：这部分深入讨论Kohana的一些核心特性，比如自动加载类、依赖注入以及其独特的MVC实现。 6. **The Kohana Way**：这部分可能涵盖了Kohana的开发哲学和最佳实践，教导如何按照Kohana的方式进行高效开发。 7. **What Next?**：这部分为初学者提供了进一步学习和提升的建议，包括扩展阅读材料、社区资源和进阶教程。 Kohana框架以其模块化设计和强大的安全特性著称，它支持ORM(Object-Relational Mapping)系统，使得数据库操作更加简单。此外，Kohana的错误处理和日志记录功能也相当完善，有利于调试和优化代码。通过学习Kohana101，开发者能够快速掌握这个框架，从而高效地开发出高质量的PHP Web应用。

#3: Configuration

Kohana favours convention over configuration. What does this mean? Kohana expects that certain things

be named in a certain way, and certain resources to be located in a specific place. That allows Kohana to

“Just Work” if normal conventions are followed. To change conventional behaviour, you need to tell Kohana

about it, by configuration.

One important convention is that every Kohana application must have a configuration file called

application/config/config.php It may not be renamed or relocated.

Navigate to /htdocs/kohana/application/config and open file config.php in a text editor.

Note that all

Kohana configurations are maintained as PHP array entries. The first entry is the site_domain which

defaults to a path:

$config['site_domain'] = '/kohana/';

Note the trailing / on the path.

In development, it's often easier to create your Kohana projects as sub-folders like www/html/

project_folder which would be configured as /project_folder/. If you specify a domain, then a full URL will

be used eg. http://domain.tld/kohana/. In production, the config entry would include the domain and look

like:

$config['site_domain'] = 'www.domain.tld/';

We will want to use a full URL and not just a path, so change the site_domain as follows:

$config['site_domain'] = 'localhost/kohana/';

Save the changes, and we are finished configuration, for now.

So it's Kohana time!

1. Kohana files are UTF-8 encoded, without a Byte Order Mark.

2. We will make some configuration changes later on.

Kohana 101

#4: Show me. Don't tell me.

Let's learn by doing here. Point your browser back at http://localhost/kohana and reload the page, so you

should see the Kohana welcome page.

So what is happening, that makes this work? First, take a look in your project folder:

index.php

example.htaccess

application

-- cache

-- config

-- controllers

-- helpers

-- hooks

-- libraries

-- logs

-- models

-- views

modules

system

Every Kohana application has a front controller, index.php which must be located within the document root

of your webserver. It can be in a sub-folder, but it must be publicly accessibly via a browser. index.php is

processed every time you access your website from a URI such as http://localhost/kohana

When PHP processes index.php the Kohana framework is invoked, system files are loaded, and the URI is

inspected to determine what actions need to be taken. These actions correspond to Controllers and their

associated methods.

Let's revist URIs. You will be familar with Google search, you enter some keywords and hit the search

button. I'm looking for information on PHP, so I enter “PHP”. Look at the URI in your browser. It has

http://www.google.com/search?hl=en&q=php&btnG=Search&meta= When you hit the search button,

information is passed to the google server, asking it to execute a search and providing a search term.

To use Kohana, it is fundamental to understand that your application will be built around the URIs that

correspond to resources and operations your application provides. How does Kohana use the URI?

Everything after index.php is a segment.

|domain information | front | segments 1/2/3/...

URI: http://localhost/kohana/index.php/welcome/search/php

^ ^ ^ ^

| 1 2 3

[Front Controller] [ segments ]

1 [Controller]

2 [Method]

3 [Arg 1]

In the first example the URI was http://localhost/kohana. So where are the segments? Once again, Kohana

conventions explain:

• http://localhost/kohana : No segments, so a default controller is used.

• http://localhost/kohana/index.php : Still no segments, so same as before.

• http://localhost/kohana/index.php/welcome : Only one segment, which is segment 1. This

corresponds to a controller called "Welcome"

• http://localhost/kohana/index.php/welcome/search/php : Three segments given:

Segment 1 is "welcome" and corresponds to controller "Welcome"

Segment 2 is "search" and corresponds to method "search()" in controller "Welcome"

Segment 3 is "php" and corresponds to argument 1 passed to method "search()" in controller

"Welcome"

The default controller is named "Welcome" It is possible to configure this differently.

The default method is called index() and is assumed if no segment, or only segment 1 is given.

Kohana 101

剩余32页未读，继续阅读

sky8652

粉丝: 0
资源: 1

Kohana PHP5框架入门教程：简化Web开发

kohana3.3.1框架教程 -

kohana编程框架

Kohana框架入门教程：构建高效PHP应用

appServ搭建php环境及kohana框架学习资料

kohana框架整合FCKeditor

kohana-blade:用于Kohana框架的Laravel刀片模板引擎

Kohana框架入门：安全、轻量级的PHP开发工具

Kohana3.0中文维基翻译：PHP框架入门指南

Kohana PHP 框架开发指南

Kohana：PHP开发框架入门详解与优势

最新资源