AIO means All-In-One. This term refers to a release package of the Tangra Framework that contains both tangra_lib and tangra_modules as well as all other components. Such releases are named after the pattern tangra_framework_aio_buildYYYYMMDD.zip/tar.gz/bz2. This is sometimes is referred as a "TF aio package" in order to distinguish it from modules aio package.
Similar to interceptor file but instead of intercepting page requests they intercept ajax requests.
A PHP class that represents single database table and encapsulates all operations on it. For more info please see Chapter 11, DBC classes
DSNs provide a universal mechanism to supply connection parameters used to connect to different databases. See the section called “DSNs in TF context” for more information.
See Data Source Name.
.php file, that resides in /htdocs directory and "intercepts" request from the web server. Real page functionality is in WP file) which is require_once() by the interceptor file.
In the "old school" approach, PHP files in the document root contained all the php and html code required for "page" to function. That led to huge files with mixed php and html content that were vary hard to read and especially to maintain. Evolutionary, separation between data / logic / presentation was introduced and that led to splitting those huge files in pure PHP and pure HTML files. Additionally (at least) in older PHP security tutorials was mentioned that in some circumstances it is possible PHP engine to stop working and Apache to sent directly PHP files' content to the browser (i.e. exposing source code). In order to avoid such security breach files in document root dir have to have just minimal set of code, in terms of Tangra framework - they contain just code to initialize the framework and to load actual page functionality (which is "hidden" in /hidden/inc/pages directory).
Example for content of interceptor file:
<?php
require_once('boot.inc.php');
boot('tcc'); // initializing the framework
require_once($WSC->get_site_inc_dir().'pages/sites/sites_wp.class.php'); // including WP file
session_start();
$page = new Sites_WP('sites');
$SITE->run($page, new Web_Context); // executing the page logic
TPL file that contain common HTML parts. Usually Main TPL files are called template_xx.tpl where xx is two letter language code. Such files reside in hidden/tpl/xx/.
Package that contains all Tangra modules. Such packages are named like tangra_modules_aio_buildYYYYMMDD.zip/tar.gz.bz2. Please don't confuse it with "aio package" which is package containing whole Tangra Framework (tangra_lib, tangra_modules, and Tangra Control Center).
in TF context means released package that is managed by modules manager and provides given functionality. Modules reside in tangra_modules directory of TF root.
In TF context means release packaged form (zip/tar.gz/bz2) of some of TF components (TCL, modules, TCC)
Path info parameter. Path info parameters are extracted from $_SERVER['PATH_INFO'] variable (if exist). For example if you have following URL: somedomain123.com/index.php/subpage-about/ and output_add_pi_rewrite_vars is installed and enabled PI parameters will be "injected" automatically in the web context of your page ($this->get__context()) and in this example you will have variable 'subpage' => 'about.
That is the root directory of given site. For example if you created and installed new site using TCC in /var/www/tft that directory is your site root. Often when subdirectory of the site is mentioned , site root is
Site template is predefined collection of modules. Site templates are defined in Tangra Control Center. Different site templates provide different functionality (based on the selected modules). When you create new site you can choose site template that reflects your needs.
SQL injection is a code injection technique that exploits a security vulnerability occurring in the database layer of an application. Tangra framework has built-in protection against such attempts (refuses to execute SQL statements that "look like" injection attempts, i.e. contain comment or EOS characters (;)). More about SQL injection at » http://en.wikipedia.org/wiki/SQL_injection
Array used as data structure for communication between two methods. Such arrays must conform requirements posed by communicating methods about presence of predetermined set of keys. This is fast and dirty way. If you want to be more precise - create simple class that will serve just as a container for the data and pass objects of this class as parameters. That way receiver method can declare its parameters as type of container classes and check for validity will be performed automatically for you by PHP engine.
Application that you create using Tangra Framework. Synonym of "Tangra Site" (see bellow).
directory structure of Tangra application created installing module directory_structure_base-x.x.x. For more information see Chapter 6, Directory structure of Tangra based site / application.
Refers to content of directory /tangra_lib (in aio package, aio release or TCL package), i.e. all classes and raw code that belong to Tangra Code Library. Sometimes TCL is mentioned as TL or tangra_lib.
Web application used for defining and installing new sites, creating pages, grids, forms, etc. Think of it as an "IDE" for Tangra Framework.
Developer that works on developing TF (TCL, modules or TCC). Short forms are “core developer” and even “coredev”.
web developer that uses TF to create applications/sites. Please don't confuse it with Tangra core developer.
tangraframework.net (aka Tangra Framework Home Site).
See Tangra application.
See Tangra Code Library.
Stands for Tangra framework.
root directory of TF. After unpacking aio package, aio release it is the top directory that contains tangra_lib/, tangra_modules/ and tcc/
Template engine - “script” that parses given Tpl file and substitutes special tags with previously exported values. At the outset HTML code is produced.
template file, usually with filename extension .tpl. Such files reside in /hidden/tpl directory and contain HTML code with template engine tags in it.
May refer to template engine or object that implements I_Tple.
Descendant of Web_Page which has Web_Event_Dispather. Such pages don't have usual run() method but methods for different events (defined in init()) or at least default_event method. These methods must return (same as run()) object of type Web_Page_View.
Stands for “Web Page”. Files with filenames that end with _wp.class.php contain class that is descendant of Web_Page. Control to that class is passed from interceptor file (see interceptor file)
may have two meanings: 1. Zend Studio Client - an IDE for PHP; 2. » Zend Framework - PHP library with many different classes/groups of classes.