Home » Archive

Articles in the Smarty Category

PEAR, Smarty »

[21 Jul 2008 | No Comment | 516 views]

For uploading files, you need to install a package of PEAR called ‘HTTP_Upload’ along with the installation of PEAR and Smarty.

PEAR, Smarty »

[20 Jul 2008 | 3 Comments | 279 views]

First of all, you need to install PEAR in your web server. Then you need to install Smarty. After that, you need to install a package in PEAR. It’s called ‘Pager’.

PEAR, Smarty »

[18 Jul 2008 | One Comment | 48 views]

For using database, you need to install a package of PEAR called ‘MDB2’ along with the installation of PEAR and Smarty.
MDB2 provides a common API for all support RDBMS.

Smarty »

[16 Jul 2008 | One Comment | 323 views]

In this article, I will be illustrating and explaining about foreach and section loop used in Smarty. I will be using these loops for creating a selection list.

Smarty »

[14 Jul 2008 | 2 Comments | 39 views]

You can also include other smarty template files in one smarty template. This brings the use of template function available in Smarty.
You may want to make a constant header and footer for your entire website. For this purpose, you can use the ‘include’ tag. Include tags are used for including other templates in the current template. Any variables available in the current template are also available within the included template. The include tag must have the attribute “file”, which contains the template resource path.

Smarty »

[11 Jul 2008 | 2 Comments | 155 views]

At first you need to download Smarty from http://smarty.php.net/download.php or you can download it directly from http://chapagain.googlecode.com/files/smarty.zip. Extract the zip file. Rename the extracted folder as ‘smarty’. Then, copy the folder ‘smarty’ to your working directory present inside the root directory of your web server.

Smarty »

[29 Jun 2008 | No Comment | 137 views]

Smarty is a template engine for PHP. More specifically, it facilitates a manageable way to separate application logic and content from its presentation. This is best described in a situation where the application programmer and the template designer play different roles, or in most cases is not the same person.