Open Power Template
| Developer(s) | Invenzzia Group |
|---|---|
| Stable release | 2.0.6
/ September 3, 2010 |
| Preview release | 2.1-beta1
/ September 3, 2010 |
| Written in | Template Engine |
| License | BSD-like |
| Website | www.invenzzia.org |
Open Power Template is a
OPT uses a dedicated XML template language for writing templates. It is not a general-purpose, but a domain-specific language. It was primarily designed to support and simplify template-specific problems with a set of declarative instructions. Instead of implementing the rendering algorithms and statements, like in imperative programming, the template designer specifies the expected result and features. This aims to ease the costs and efforts associated with the software development and further maintenance.
The library provides an object-oriented API based on the solutions from popular frameworks. As it is the first member of a bigger project, Open Power Libs, it is built upon a small OPL core library which provides the basic features.
History
The project started in November 2004, as a template engine for a discussion board project inspired by Smarty. While it later failed, the library became independent. In July 2006, the version 1.0.0 was released. It offered a template language with Smarty-like syntax and a small set of declarative instructions.
In January 2007, the developers release the version 1.1.0 which brings some notable improvements, such as
In January 2008, the developers form an open-source programming team, Invenzzia to develop OPT and other PHP projects. At the same time, the development of Open Power Template 2.0 began.
The last version of the 1.1 branch was released in May 2008 and the group focused on the OPT 2.0 development. The new library went into the beta-stage in December and the first stable version was released in July 2009.
Features
The OPT 2.0 template language is an XML application and allows to manipulate the XHTML document structure. The other features are:
- Template inheritance and other advanced template modularization mechanisms.
- Formrendering support (components)
- Abstract, declarative list generators (sections)
- Automated filtering against cross-site scripting attacks.
- Internationalization support.
- XML manipulation instructions.
- Imperative control structures: conditions and loops.
- Expressionlanguage optimized for XML and an abstraction layer making it independent from PHP data types and application-specific implementation details (data formats).
The built-in XML parser can be reconfigured to parse certain HTML documents or plain text content.
Sample application
Since the templates are separated from the application logic, you need at least two files. The first one contains the presentation code as an XML template:
<?xml version="1.0" ?>
<opt:root escaping="yes">
<opt:prolog version="1.0" />
<opt:dtd template="xhtml10transitional" />
<html>
<head>
<title>{$pageTitle}</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
</head>
<body>
<p>{$introduction}</p>
<!-- display a list -->
<opt:show name="list">
<ol>
<li opt:section="list">{$list.item}</li>
</ol>
</opt:show>
</body>
</html>
</opt:root>
The second one generates the data and configures the library:
require('./libs/Opl/Base.php');
Opl_Loader::setDirectory('./libs/');
Opl_Loader::register();
$tpl = new Opt_Class;
$tpl->sourceDir = './templates/';
$tpl->compileDir = './templates_c/';
$tpl->setup();
$view = new Opt_View('template.tpl');
// Assigning the script data to the template
$view->pageTitle = 'Sample OPT page';
$view->introduction = 'Sample text';
$view->list = array(0 =>
array('item' => 'Item 1'),
array('item' => 'Item 1'),
array('item' => 'Item 1')
);
$view->setFormat('list', 'Array');
$output = new Opt_Output_Http;
$output->render($view);