Free template toolkit software for linux

Template::Tools::ttree module can process entire directory trees of templates.

SYNOPSIS
ttree [options] [files]

The ttree script is used to process entire directory trees containing template files. The resulting output from processing each file is then written to a corresponding file in a destination directory. The script compares the modification times of source and destination files (where they already exist) and processes only those files that have been modified. In other words, it is the equivalent of make for the Template Toolkit.

It supports a number of options which can be used to configure behaviour, define locations and set Template Toolkit options. The script first reads the .ttreerc configuration file in the HOME directory, or an alternative file specified in the TTREERC environment variable. Then, it processes any command line arguments, including any additional configuration files specified via the -f (file) option.

The .ttreerc Configuration File

When you run ttree for the first time it will ask you if you want it to create a .ttreerc file for you. This will be created in your home directory.

$ ttree

Do you want me to create a sample .ttreerc file for you?

(file: /home/abw/.ttreerc) [y/n]: y
/home/abw/.ttreerc created. Please edit accordingly and re-run ttree

The purpose of this file is to set any global configuration options that you want applied every time ttree is run. For example, you can use the ignore and copy option to provide regular expressions that specify which files should be ignored and which should be copied rather than being processed as templates. You may also want to set flags like verbose and recurse according to your preference.

A minimal .ttreerc:

# ignore these files
ignore = b(CVS|RCS)b
ignore = ^#
ignore = ~$

# copy these files
copy = .(gif|png|jpg|pdf)$

# recurse into directories
recurse

# provide info about whats going on
verbose

In most cases, youll want to create a different ttree configuration file for each project youre working on. The cfg option allows you to specify a directory where ttree can find further configuration files.

cfg = /home/abw/.ttree

The -f command line option can be used to specify which configuration file should be used. You can specify a filename using an absolute or relative path:

$ ttree -f /home/abw/web/example/etc/ttree.cfg
$ ttree -f ./etc/ttree.cfg
$ ttree -f ../etc/ttree.cfg

If the configuration file does not begin with / or . or something that looks like a MS-DOS absolute path (e.g. C:etcttree.cfg) then ttree will look for it in the directory specified by the cfg option.

$ ttree -f test1 # /home/abw/.ttree/test1

The cfg option can only be used in the .ttreerc file. All the other options can be used in the .ttreerc or any other ttree configuration file. They can all also be specified as command line options.

Remember that .ttreerc is always processed before any configuration file specified with the -f option. Certain options like lib can be used any number of times and accumulate their values.

For example, consider the following configuration files:
/home/abw/.ttreerc:

cfg = /home/abw/.ttree
lib = /usr/local/tt2/templates

/home/abw/.ttree/myconfig:

lib = /home/abw/web/example/templates/lib

When ttree is invoked as follows:

$ ttree -f myconfig

the lib option will be set to the following directories:

/usr/local/tt2/templates
/home/abw/web/example/templates/lib

Any templates located under /usr/local/tt2/templates will be used in preference to those located under /home/abw/web/example/templates/lib. This may be what you want, but then again, it might not. For this reason, it is good practice to keep the .ttreerc as simple as possible and use different configuration files for each ttree project.

Template::TT2Site is a Perl module to create standard web sites with the Template Toolkit.

SYNOPSIS

$ mkdir NewSite
$ cd NewSite
$ tt2site setup
... make your pages ...
$ tt2site build
... point your browser at html/index.html ...

tt2site is just a wrapper program. tt2site setup is equivalent to perl -MTemplate::TT2Site -e setup, and so on.

Template::TT2Site is a framework to create web sites using the Template Toolkit.

The technical structure of the site is patterned after the method described in chapter 11 of The Badger Book. The structure has been slightly simplified for ease of use, and a couple of neat features are added:

The resultant site is position independent, i.e., it only uses relative URLs to the extent possible. This makes it easy to build partial sites, and to relocate the contents.

The necessary means are provided to create multi-language sites, where each page gets a link to its translations.
The site.map hash, required for site navigation, is created automatically using minimal, position independent, directions.

This module, Template::TT2Site, provides the necessary methods to setup and maintain a site. It is used by the wrapper program, tt2site.

The Program Database Toolkit (PDT) is a powerful tool infrastructure that provides access to the high-level interface of source code for analysis tools and applications.
Many tasks in an integrated programming environment require access to program information for their implementation. Program Database Toolkit (PDT) is a framework for analyzing source code written in several programming languages and for making rich program knowledge accessible to developers of static and dynamic analysis tools.
PDT implements a standard program representation, the program database (PDB), that can be accessed in a uniform way through a class library supporting common PDB operations. Software tools can use this library to accomplish tasks such as
- documentation of program components
- creation of graphic program browsers that show class hierarchies, function call graphs, and template instantiations
- insertion of instrumentation for performance profiling and tracing; andgeneration of interface details for calling library routines or buildinginterlanguage bindings.
Enhancements:
- Assorted minor bugfixes.

The Kiwi Toolkit project is a foundation class library containing many useful classes that complement the Java Foundation Classes (JFC).
It includes many classes and components that were not provided with the JFC, such as a TreeTable component, a DateChooser, an MVC charting package (bar charts, line charts, pie charts), a plugin framework for Java, an application resource manager (for loading images, icons, HTML pages, audio clips, and other resources from JAR files), a better internationalization API, and much more.
Enhancements:
- This release adds some new classes and includes various bugfixes.

OSP Toolkit project is a client side implementation of the ETSI OSP VoIP Peering protocol (ETSI TS 101 321).

The OSP Toolkit project was begun in 1998 and the code has been incorporated into many commercial and open source VoIP products.

VP Toolkit is an Internet client/server C++ library, with support for object threads, stream based socket I/O, a multi-threaded server socket framework, a multi-process fault tolerant server framework, XML, HTTP, etc.

VP Toolkit software is now deprecated in favor of UDK.

To build the documentation you will need SDF, and HTMLDOC. SDF can be downloaded freely from the SDF home page at http://www.mincom.com/mtr/sdf/, and HTMLDOC can be had from
http://www.easysw.com/htmldoc/.

Template::Ast is a Perl module to process ASTs for Perl Template Toolkit.

SYNOPSIS

use Template::Ast;

# Rebuild AST stored in file:
$ast = Template::Ast->read(foo.ast) or
die Template::Ast->error();

# Writing existing AST to file:
$ast = { Marry => [24, F], John => [21, M] };
Template::Ast->write($ast, foo.ast) or
die Template::Ast->error();

$ast = Template::Ast->merge([1,2,3], undef); # [1,2,3]
$ast = Template::Ast->merge(undef, [1,2,3]); # [1,2,3]
$ast = Template::Ast->merge(undef, undef); # undef

$ast = Template::Ast->merge({A=>1,B=>2}, [C]); # [C]
$ast = Template::Ast->merge([1,2,3], [5,6]); # [5,6]
$ast = Template::Ast->merge([{A=>1},2], 5); # 5

$ast = Template::Ast->merge({A=>1,B=>2}, {C=>3}); # {A=>1,B=>2,C=>3}
$ast = Template::Ast->merge({A=>1,B=>2}, {B=>3}); # {A=>1,B=>3}

# {A=>1,B=>2}
$ast = Template::Ast->merge({A=>1,B=>undef}, {A=>undef,B=>2});

Template::Ast->merge(
{A=>1,B=>{C=>1,D=>2}},
{B=>{C=>1,D=>3,E=>4}}
); # {A=>1,B=>{C=>1,D=>3,E=>4}}

Template::Ast->merge(
{A=>1,B=>{C=>[1,2]}},
{B=>{C=>[3,4]}}
); # {A=>1,B=>{C=>[3,4]}}

print Template::Ast->dump([$vars], [vars]);

ASTs are essential in the programming model based on Perl Template Toolkit. This module provides some easy interface to do the dirty work involved in AST handling. The term AST used here are referred to any Perl referece pointed to a complex data structure, such as a nested hash, a nested array, or such.