Free tt2 software for linux

OpenInteract2::TT2::Plugin is a Perl module for custom OpenInteract functionality in templates.

SYNOPSIS

# Create the TT object with the OI plugin

my $template = Template->new(
PLUGINS => { OI => OpenInteract2::TT2::Plugin }, ... );
my ( $output );
$template->process( package::template, %params, $output );

# In the template (brief examples, see below for more)

Here is what the plugin can do:
< ul>< li>[% OI.show_all_actions.join( "n < li>" ) -%]< /ul>

Here are plugins available to you:
[% OI.show_all_plugins.keys.sort.join( , ) %]

Here are all the parameters passed to the request:
[% OI.request_param.sort.join( , ) %]

And the value of a particular parameter:
last name: [% OI.request_param( last_name ) %]

[% OI.action_execute( error_display, error_msg = error_msg ) -%]

# Note that you can also use the MSG function
[% OI.msg( mypage.intro, OI.login.full_name ) %]

# Note that you can also use the LH variable
[% mh = OI.msg_handle %]
[% mh.maketext( mypage.intro, OI.login.full_name ) %]
[% mh.maketext( mypage.learnmore ) %]

[% OI.box_add( contact_tools_box, title = Contact Tools,
weight = 2 ) -%]

[% object_info = OI.object_description( object ) %]
This is a [% object_info.name %] object.

Is the object in the class?
[% OI.class_isa( object, SPOPS::DBI ) ? yes : no %]

Is the SPOPS object writable?
[% IF OI.can_write( object ) %]Youre special![% END %]

[% action = OI.action %]
Action that called this template: [% action.name %]
Security for action:
[% action.security_level %] found,
[% action.security_required %] required

Properties of action:
[% action_prop = action.properties %]
[% FOREACH key = action_prop.keys %]
[% key %] = [% action_prop.$key %]
[% END %]

Parameters of action:
[% action_param = action.param %]
[% FOREACH key = action_param.keys %]
[% key %] = [% action_param.$key %]
[% END %]

Today is [% OI.date_format( now, %Y-%m-%d %l:%M %p ) %] the
[% OI.date_format( now, %j ) %] day of the year

[% d = OI.date_into_object( object.updated_on, %Y-%m-%d ) -%]
[% OI.action_execute( date_select, month_value = d.month,
day_value = d.day,
year_value = d.year, blank = 1,
field_prefix = updated_on ) -%]

[% INCLUDE form_checkbox( name = is_in_print,
value = TRUE,
is_checked = OI.as_boolean( book.is_in_print ) ) -%]

Is in print? [% OI.as_boolean_label( book.is_in_print ) %]

Is in print? [% OI.as_boolean_label( book.is_in_print, You betcha, No way ) %]

[% OI.limit_string( object.description, 30 ) %]

var person_last_name = [% OI.javascript_quote( person.last_name ) %];

[% OI.limit_sentences( news.news_item, 3 ) %]

[% score = grade.score / test.total %]
Your grade is: [% OI.percent_format( score ) %]

You have [% OI.money_format( account.balance ) %] left to spend.

Hello [% OI.uc_first( person.first_name ) %]

You are important so I must speak to you loudly [% OI.uc( person.last_name ) %]



Item: [% OI.html_decode( news.news_item ) %]

# Add parameters to an existing URL
[% display_no_template_url = OI.add_params_to_url( my_path, no_template = yes ) %]

# Works, but not as useful...
[% edit_url = OI.make_url( BASE = /User/show/, user_id = OI.login.user_id,
edit = 1, show_all = yes ) %]

# Preferred way to generate URLs for actions
[% edit_url = OI.make_url( ACTION = user, TASK = show,
user_id = OI.login.user_id,
edit = 1, show_all = yes ) %]

[% image_url = OI.make_url( IMAGE = /images/foo.gif ) %]
[% static_url = OI.make_url( STATIC = /generated/report-q1-2003.pdf ) %]

[% theme = OI.theme_properties %]
Background color of page: [% theme.bgcolor %]

[% new_theme = OI.theme_fetch( 5 ) %]
Background color of page from other theme: [% new_theme.bgcolor %]

[% IF OI.logged_in -%]
Hello [% OI.login.full_name %].
Your groups are: [% OI.login_group.join( , ) -%]
[% ELSE -%]
You are not logged in.
[% END -%]

Your last search: [% OI.session.latest_search %]

< a href="[% OI.return_url %]">Refresh< /a>

[% IF object.tmp_security_level >= OI.security_level.write -%]
you can edit this object!
[% END %]

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::Library::Splash is a template library for building stylish HTML user interfaces.

NOTE: This documentation is incomplete, incorrect and outdated. The Splash! library is still evolving and subject to change. See the examples for a much more recent and accurate demonstration of use.

Introduction:

The Splash template library is distributed as part of the Template Toolkit. It can be found in the templates sub-directory of the installation directory.

/your/tt2/installation
|
+-- docs
| ...
|
+-- images
| ...
|
+-- examples
| ...
|
+-- templates
|
+-- html
| ...
+-- pod
| ...
+-- splash instdir() class method.
use Template;

my $tt2 = Template->new({
INCLUDE_PATH => Template::Config->instdir(templates),
});
Note that you should set the INCLUDE_PATH to the templates directory as shown here and dont be tempted to set the INCLUDE_PATH to templates/splash. Many of the Splash! components use elements in the html directory and contain directives of the form:
[% INCLUDE html/something %].

Template::Alloy is a TT2/3, HT, HTE, Tmpl, and Velocity Engine.

SYNOPSIS

Template::Toolkit style usage
my $t = Template::Alloy->new(
INCLUDE_PATH => [/path/to/templates],
);

my $swap = {
key1 => val1,
key2 => val2,
code => sub { 42 },
hash => {a => b},
};

# print to STDOUT
$t->process(my/template.tt, $swap)
|| die $t->error;

# process into a variable
my $out = ;
$t->process(my/template.tt, $swap, $out);

### Alloy uses the same syntax and configuration as Template::Toolkit
HTML::Template::Expr style usage
my $t = Template::Alloy->new(
filename => my/template.ht,
path => [/path/to/templates],
);

my $swap = {
key1 => val1,
key2 => val2,
code => sub { 42 },
hash => {a => b},
};

$t->param($swap);

# print to STDOUT (errors die)
$t->output(print_to => *STDOUT);

# process into a variable
my $out = $t->output;

### Alloy can also use the same syntax and configuration as HTML::Template
Text::Tmpl style usage
my $t = Template::Alloy->new;

my $swap = {
key1 => val1,
key2 => val2,
code => sub { 42 },
hash => {a => b},
};

$t->set_delimiters(#[, ]#);
$t->set_strip(0);
$t->set_values($swap);
$t->set_dir(/path/to/templates);

my $out = $t->parse_file(my/template.tmpl);

my $str = "Foo #[echo $key1]# Bar";
my $out = $t->parse_string($str);


### Alloy uses the same syntax and configuration as Text::Tmpl
Velocity (VTL) style usage
my $t = Template::Alloy->new;

my $swap = {
key1 => val1,
key2 => val2,
code => sub { 42 },
hash => {a => b},
};

my $out = $t->merge(my/template.vtl, $swap);

my $str = "#set($foo 1 + 3) ($foo) ($bar) ($!baz)";
my $out = $t->merge($str, $swap);

Catalyst::Manual::Tutorial::BasicCRUD is a Catalyst Tutorial - Part 3: Basic CRUD.

Include a Create Action in the Books Controller

Edit lib/MyApp/Controller/Books.pm and enter the following method:

=head2 url_create

Create a book with the supplied title, rating, and author

=cut

sub url_create : Local {
# In addition to self & context, get the title, rating, &
# author_id args from the URL. Note that Catalyst automatically
# puts extra information after the "/ / model(MyAppDB::Book)->create({
title => $title,
rating => $rating
});

# Add a record to the join table for this book, mapping to
# appropriate author
$book->add_to_book_authors({author_id => $author_id});
# Note: Above is a shortcut for this:
# $book->create_related(book_authors, {author_id => $author_id});

# Assign the Book object to the stash for display in the view
$c->stash->{book} = $book;

# This is a hack to disable XSUB processing in Data::Dumper
# (its used in the view). This is a work-around for a bug in
# the interaction of some versions or Perl, Data::Dumper & DBIC.
# You wont need this if you arent using Data::Dumper (or if
# you are running DBIC 0.06001 or greater), but adding it doesnt
# hurt anything either.
$Data::Dumper::Useperl = 1;

# Set the TT template to use
$c->stash->{template} = books/create_done.tt2;
}

Notice that Catalyst takes "extra slash-separated information" from the URL and passes it as arguments in @_. The url_create action then uses a simple call to the DBIC create method to add the requested information to the database (with a separate call to add_to_book_authors to update the join table). As do virtually all controller methods (at least the ones that directly handle user input), it then sets the template that should handle this request.

Template::Plugin::Digest::SHA1 is a TT2 interface to the SHA1 Algorithm.

SYNOPSIS

[% USE Digest.SHA1 -%]
[% checksum = content FILTER sha1 -%]
[% checksum = content FILTER sha1_hex -%]
[% checksum = content FILTER sha1_base64 -%]
[% checksum = content.sha1 -%]
[% checksum = content.sha1_hex -%]
[% checksum = content.sha1_base64 -%]

The Digest.SHA1 Template Toolkit plugin provides access to the NIST SHA-1 algorithm via the Digest::SHA1 module. It is used like a plugin but installs filters and vmethods into the current context.

CGI::Expand is a Perl module that can convert flat hash to nested data using TT2s dot convention.

SYNOPSIS

use CGI::Expand;
use CGI; # or Apache::Request, etc.

$args = expand_cgi( CGI->new(a.0=3&a.2=4&b.c.0=x) );
# $args = { a => [3,undef,4], b => { c => [x] }, }

# Or to catch exceptions:
eval {
$args = expand_cgi( CGI->new(a.0=3&a.2=4&b.c.0=x) );
} or log_and_exit( $@ );

#-----
use CGI::Expand qw(expand_hash);

$args = expand_hash({a.0=>77}); # $args = { a => [ 77 ] }

Converts a CGI query into structured data using a dotted name convention similar to TT2.

expand_cgi works with CGI.pm, Apache::Request or anything with an appropriate "param" method. Or you can use expand_hash directly.

If you prefer to use a different flattening convention then CGI::Expand can be subclassed.