sharepoint templates
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1066
Label Templates 1.0
Label Templates are Free Opendocument Format Label Templates in over 50 sizes. more>>
Label Templates are free Opendocument Format label templates for Openoffice.org, KOffice or any other Office suite ODF ready for making labels.
Collection includes CD, DVD, address, mailing, round, media label templates, Avery sizes and more. US Letter size and 14 size paper formats available.
Setup time is quick with these templates and printing labels from these templates is easy.
<<lessCollection includes CD, DVD, address, mailing, round, media label templates, Avery sizes and more. US Letter size and 14 size paper formats available.
Setup time is quick with these templates and printing labels from these templates is easy.
Download (0.50MB)
Added: 2006-10-23 License: GPL (GNU General Public License) Price:
1116 downloads
SmartTemplate 1.2.1
SmartTemplate is a Template Engine that was designed to support large scale, web based applications. more>>
SmartTemplate is a Template Engine that was designed to support large scale, web based applications.
Whats so special about it?
Common template engines work like the following: Your PHP script specifies an HTML template and assigns some dynamic content to display. The template parser replaces all placeholders within the template with the assigned content and displays it to the user. This means a lot of string processing and regular expression work each time you want to display some content.
SmartTemplate works like a template compiler that converts templates into executable PHP code and stores it for later reuse. The first time a new template is processed, all placeholders in the template are replaced by small PHP code elements that print the assigned content. The HTML template fragment < H3 >{TITLE}< /H3 >, for example, is converted into something like < H3 >< ?php echo $TITLE; ? >< /H3 >. If you have assigned your content to the right variables, there is no need for any template parsing anymore. The only thing that has to be done is to include and execute the compiled template. This usually increases the execution time of the template engine dramatically.
SmartTemplate supports:
- Simple Scalar Substitution (Strings, etc.)
- Block Iterations (nested Arrays / BEGIN..END)
- Basic Control Structures (IF..ELSEIF..ELSE)
- Custom Extension (Output filters, uppercase, sprintf, etc.)
- Template Compilation (HTML templates are converted to executable PHP Code)
- SubTemplate System (HTML templates can be included on other templates)
- Output Caching (Accelerates your applications by reusing page output)
<<lessWhats so special about it?
Common template engines work like the following: Your PHP script specifies an HTML template and assigns some dynamic content to display. The template parser replaces all placeholders within the template with the assigned content and displays it to the user. This means a lot of string processing and regular expression work each time you want to display some content.
SmartTemplate works like a template compiler that converts templates into executable PHP code and stores it for later reuse. The first time a new template is processed, all placeholders in the template are replaced by small PHP code elements that print the assigned content. The HTML template fragment < H3 >{TITLE}< /H3 >, for example, is converted into something like < H3 >< ?php echo $TITLE; ? >< /H3 >. If you have assigned your content to the right variables, there is no need for any template parsing anymore. The only thing that has to be done is to include and execute the compiled template. This usually increases the execution time of the template engine dramatically.
SmartTemplate supports:
- Simple Scalar Substitution (Strings, etc.)
- Block Iterations (nested Arrays / BEGIN..END)
- Basic Control Structures (IF..ELSEIF..ELSE)
- Custom Extension (Output filters, uppercase, sprintf, etc.)
- Template Compilation (HTML templates are converted to executable PHP Code)
- SubTemplate System (HTML templates can be included on other templates)
- Output Caching (Accelerates your applications by reusing page output)
Download (0.008MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1216 downloads
Blitz templates 0.5.1
Blitz templates is a fast template engine written in C and compiled as a PHP module. more>>
Blitz templates is a fast template engine written in C and compiled as a PHP module. It started as a php_templates replacement, but developed into much more.
The project is based on extensible template controllers (custom view classes in PHP) and weakly-active templates (simple logic in HTML).
Enhancements:
- Lot of code cleanup was done.
- The "parse" and "include" methods were improved, and their "vars" argument is not a globals array anymore; now its just an arbitrary iteration set and both methods comply with set/block/fetch.
- Templates included by the "include" method from PHP code inherit globals from the caller automatically.
- Corresponding tests were updated.
- A new article was added to the documentation: "Quick Geek Blitz Tutorial", which is addressed to those professionals who want to learn API basics in a minimum of time.
<<lessThe project is based on extensible template controllers (custom view classes in PHP) and weakly-active templates (simple logic in HTML).
Enhancements:
- Lot of code cleanup was done.
- The "parse" and "include" methods were improved, and their "vars" argument is not a globals array anymore; now its just an arbitrary iteration set and both methods comply with set/block/fetch.
- Templates included by the "include" method from PHP code inherit globals from the caller automatically.
- Corresponding tests were updated.
- A new article was added to the documentation: "Quick Geek Blitz Tutorial", which is addressed to those professionals who want to learn API basics in a minimum of time.
Download (0.10MB)
Added: 2007-08-14 License: BSD License Price:
803 downloads
HCKit::Template 0.02
HCKit::Template is a Perl module with a template system for HTML construction. more>>
HCKit::Template is a Perl module with a template system for HTML construction.
This module constructs an HTML page from a template. The conversion proceeds with the help of rewrite rules and data sources. Rewrite rules can be specified in the template file itself, or in the Perl script. Data sources can be XML files, or dynamically constructed in the Perl script.
<<lessThis module constructs an HTML page from a template. The conversion proceeds with the help of rewrite rules and data sources. Rewrite rules can be specified in the template file itself, or in the Perl script. Data sources can be XML files, or dynamically constructed in the Perl script.
Download (0.011MB)
Added: 2006-09-20 License: Perl Artistic License Price:
1129 downloads
kmail templates 20061018
kmail templates is a patch for current 3.5 branch of kdepim package. more>>
kmail templates is a patch for current 3.5 branch of kdepim package which replaces Phrases configuration with more rich templates engine.
Templates use template syntax of well-known Thebat! mail client and allow construct a little more complicated messages than now.
<<lessTemplates use template syntax of well-known Thebat! mail client and allow construct a little more complicated messages than now.
Download (MB)
Added: 2006-10-19 License: GPL (GNU General Public License) Price:
1112 downloads
HTML::Template 2.9
HTML::Template module attempts to make using HTML templates simple and natural. more>>
HTML::Template module attempts to make using HTML templates simple and natural.
HTML::Template library extends standard HTML with a few new tags for variables, loops, if/else blocks and includes.
A file written with HTML and these new tags is called a template. Using this module you fill in the values for the variables and loops declared in the template.
This allows you to seperate design (the HTML) from the data, which you generate in the Perl script. While there are many other HTML template systems available, this module is simple and fast.
It doesnt try to reinvent Perl CGI, it just augments HTML with a few new and very useful abilities.
Enhancements:
- A new option was added to enforce Taint mode for unescaped variables.
- Several long-standing bugs were fixed.
- The enhanced tests produced by the Phalanx project are now part of the module.
<<lessHTML::Template library extends standard HTML with a few new tags for variables, loops, if/else blocks and includes.
A file written with HTML and these new tags is called a template. Using this module you fill in the values for the variables and loops declared in the template.
This allows you to seperate design (the HTML) from the data, which you generate in the Perl script. While there are many other HTML template systems available, this module is simple and fast.
It doesnt try to reinvent Perl CGI, it just augments HTML with a few new and very useful abilities.
Enhancements:
- A new option was added to enforce Taint mode for unescaped variables.
- Several long-standing bugs were fixed.
- The enhanced tests produced by the Phalanx project are now part of the module.
Download (0.061MB)
Added: 2007-01-31 License: GPL (GNU General Public License) Price:
998 downloads
Pod::Template 0.02
Pod::Template is a Perl module for building pod documentation from templates. more>>
Pod::Template is a Perl module for building pod documentation from templates.
SYNOPSIS
### As a module ###
use Pod::Template;
my $parser = new Pod::Template;
$parser->parse( template => documentation.ptmpl );
print $parser->as_string
### As a script ###
$ podtmpl -I dir1 -I dir2 documentation.ptmpl
### A simple module prepared to use Pod::Template ###
package My::Module;
=Template print_me
=head2 print_me( $string )
Prints out its argument.
=cut
sub print_me { print shift; return 1 }
### A simple pod file named Extra/Additional.pod ###
=pod
=Template return_vals
This subroutine returns 1 for success and undef for failure.
=cut
### A simple Pod::Template template ###
=Include My::Module
=Include Extra/Additional.pod as Extra
=pod
=head1 SYNOPSIS
use My::Module
My::Module::print_me(some text);
=head2 Functions
=Insert My::Module->print_me
=Insert Extra->return_vals
=cut
Writing documentation on a project maintained by several people which spans more than one module is a tricky matter. There are many things to consider:
Location
Should pod be inline (above every function), at the bottom of the module, or in a distinct file? The first is easier for the developers, but the latter two are better for the pod maintainers.
Order
What order should the documentation be in? Does it belong in the order in which the functions are written, or ordered by another principle, such as frequency of use or function type? Again, the first option is better for the developers, while the second two are better for the user.
References
How should a function in another file be mentioned? Should the documentation simply say see Other::Module, or should it include the relevant section? Duplication means that the documentation is more likely to be outdated, but its bad for a user to have to read numerous documents to simply find out what an inherited method does.
Headers & Footers
What should be done with standard headers and footers? Should they be pasted in to every file, or can the main file be assumed to cover the entire project?
Pod::Template offers a solution to these problems: documentation is built up from templates.
<<lessSYNOPSIS
### As a module ###
use Pod::Template;
my $parser = new Pod::Template;
$parser->parse( template => documentation.ptmpl );
print $parser->as_string
### As a script ###
$ podtmpl -I dir1 -I dir2 documentation.ptmpl
### A simple module prepared to use Pod::Template ###
package My::Module;
=Template print_me
=head2 print_me( $string )
Prints out its argument.
=cut
sub print_me { print shift; return 1 }
### A simple pod file named Extra/Additional.pod ###
=pod
=Template return_vals
This subroutine returns 1 for success and undef for failure.
=cut
### A simple Pod::Template template ###
=Include My::Module
=Include Extra/Additional.pod as Extra
=pod
=head1 SYNOPSIS
use My::Module
My::Module::print_me(some text);
=head2 Functions
=Insert My::Module->print_me
=Insert Extra->return_vals
=cut
Writing documentation on a project maintained by several people which spans more than one module is a tricky matter. There are many things to consider:
Location
Should pod be inline (above every function), at the bottom of the module, or in a distinct file? The first is easier for the developers, but the latter two are better for the pod maintainers.
Order
What order should the documentation be in? Does it belong in the order in which the functions are written, or ordered by another principle, such as frequency of use or function type? Again, the first option is better for the developers, while the second two are better for the user.
References
How should a function in another file be mentioned? Should the documentation simply say see Other::Module, or should it include the relevant section? Duplication means that the documentation is more likely to be outdated, but its bad for a user to have to read numerous documents to simply find out what an inherited method does.
Headers & Footers
What should be done with standard headers and footers? Should they be pasted in to every file, or can the main file be assumed to cover the entire project?
Pod::Template offers a solution to these problems: documentation is built up from templates.
Download (0.008MB)
Added: 2006-09-21 License: Perl Artistic License Price:
1128 downloads
Smarty PHP template engine 2.6.18
Smarty PHP template engine is a template engine for PHP. more>>
Smarty project is a template engine for PHP. Many other template engines for PHP provide basic variable substitution and dynamic block functionality.
Smarty takes a step further to be a "smart" template engine, adding features such as configuration files, template functions, and variable modifiers, and making all of this functionality as easy as possible to use for both programmers and template designers.
Smarty also converts the templates into PHP scripts, eliminating the need to parse the templates on every invocation. This makes Smarty extremely scalable and managable for large application needs.
Main features:
- Caching: Smarty provides fine-grained caching features for caching all or parts of a rendered web page, or leaving parts uncached. Programmers can register template functions as cacheable or non-cachable, group cached pages into logical units for easier management, etc.
- Configuration Files: Smarty can assign variables pulled from configuration files. Template designers can maintain values common to several templates in one location without intervention from the programmer, and config variables can easily be shared between the programming and presentation portions of the application.
- Security: Templates do not contain PHP code. Therefore, a template designer is not unleashed with the full power of PHP, but only the subset of functionality made available to them from the programmer (application code.)
- Easy to Use and Maintain: Web page designers are not dealing with PHP code syntax, but instead an easy-to-use templating syntax not much different than plain HTML. The templates are a very close representation of the final output, dramatically shortening the design cycle.
- Variable Modifiers: The content of assigned variables can easily be adjusted at display-time with modifiers, such as displaying in all upper-case, html-escaped, formatting dates, truncating text blocks, adding spaces between characters, etc. Again, this is accomplished with no intervention from the programmer.
- Template Functions: Many functions are available to the template designer to handle tasks such as generating HTML code segments (dropdowns, tables, pop-ups, etc.), displaying content from other templates in-line, looping over arrays of content, formatting text for e-mail output, cycling though colors, etc.
- Filters: The programmer has complete control of template output and compiled template content with pre-filters, post-filters and output-filters.
- Resources: Templates can be pulled from any number of sources by creating new resource handlers, then using them in the templates.
- Plugins: Almost every aspect of Smarty is controlled through the use of plugins. They are generally as easy as dropping them into the plugin directory and then mentioning them in the template or using them in the application code. Many user-community contributions are also available. (See the plugins section of the forum and wiki.)
- Add-ons: Many user-community contributed Add-ons are available such as Pagination, Form Validation, Drop Down Menus, Calander Date Pickers, etc. These tools help speed up the development cycle, there is no need to re-invent the wheel or debug code that is already stable and ready for deployment. (see the Add-ons section of the forum and wiki.)
- Debugging: Smarty comes with a built-in debugging console so the template designer can see all of the assigned variables and the programmer can investigate template rendering speeds.
- Compiling: Smarty compiles templates into PHP code behind the scenes, eliminating run-time parsing of templates.
- Performance: Smarty performs extremely well, despite its vast feature set. Most of Smartys capabilities lie in plugins that are loaded on-demand. Smarty comes with numerous presentation tools, minimizing your application code and resulting in quicker, less error-prone application development/deployment. Smarty templates get compiled to PHP files internally (once), eliminating costly template file scans and leveraging the speed of PHP op-code accelerators.
<<lessSmarty takes a step further to be a "smart" template engine, adding features such as configuration files, template functions, and variable modifiers, and making all of this functionality as easy as possible to use for both programmers and template designers.
Smarty also converts the templates into PHP scripts, eliminating the need to parse the templates on every invocation. This makes Smarty extremely scalable and managable for large application needs.
Main features:
- Caching: Smarty provides fine-grained caching features for caching all or parts of a rendered web page, or leaving parts uncached. Programmers can register template functions as cacheable or non-cachable, group cached pages into logical units for easier management, etc.
- Configuration Files: Smarty can assign variables pulled from configuration files. Template designers can maintain values common to several templates in one location without intervention from the programmer, and config variables can easily be shared between the programming and presentation portions of the application.
- Security: Templates do not contain PHP code. Therefore, a template designer is not unleashed with the full power of PHP, but only the subset of functionality made available to them from the programmer (application code.)
- Easy to Use and Maintain: Web page designers are not dealing with PHP code syntax, but instead an easy-to-use templating syntax not much different than plain HTML. The templates are a very close representation of the final output, dramatically shortening the design cycle.
- Variable Modifiers: The content of assigned variables can easily be adjusted at display-time with modifiers, such as displaying in all upper-case, html-escaped, formatting dates, truncating text blocks, adding spaces between characters, etc. Again, this is accomplished with no intervention from the programmer.
- Template Functions: Many functions are available to the template designer to handle tasks such as generating HTML code segments (dropdowns, tables, pop-ups, etc.), displaying content from other templates in-line, looping over arrays of content, formatting text for e-mail output, cycling though colors, etc.
- Filters: The programmer has complete control of template output and compiled template content with pre-filters, post-filters and output-filters.
- Resources: Templates can be pulled from any number of sources by creating new resource handlers, then using them in the templates.
- Plugins: Almost every aspect of Smarty is controlled through the use of plugins. They are generally as easy as dropping them into the plugin directory and then mentioning them in the template or using them in the application code. Many user-community contributions are also available. (See the plugins section of the forum and wiki.)
- Add-ons: Many user-community contributed Add-ons are available such as Pagination, Form Validation, Drop Down Menus, Calander Date Pickers, etc. These tools help speed up the development cycle, there is no need to re-invent the wheel or debug code that is already stable and ready for deployment. (see the Add-ons section of the forum and wiki.)
- Debugging: Smarty comes with a built-in debugging console so the template designer can see all of the assigned variables and the programmer can investigate template rendering speeds.
- Compiling: Smarty compiles templates into PHP code behind the scenes, eliminating run-time parsing of templates.
- Performance: Smarty performs extremely well, despite its vast feature set. Most of Smartys capabilities lie in plugins that are loaded on-demand. Smarty comes with numerous presentation tools, minimizing your application code and resulting in quicker, less error-prone application development/deployment. Smarty templates get compiled to PHP files internally (once), eliminating costly template file scans and leveraging the speed of PHP op-code accelerators.
Download (0.14MB)
Added: 2007-03-11 License: LGPL (GNU Lesser General Public License) Price:
962 downloads
HTML::Template::Set 1.009
HTML::Template::Set is a HTML::Template extension that adds set support. more>>
HTML::Template::Set is a HTML::Template extension that adds set support.
SYNOPSIS
in your HTML:
< TMPL_SET NAME="handler" >apples_to_oranges< /TMPL_SET >
< TMPL_SET NAME="title" >Apples Are Green< /TMPL_SET >
< HTML >
< HEAD >
< TITLE >< TMPL_VAR NAME="title" >< /TITLE >
< /HEAD >
< BODY >
< H1 >< TMPL_VAR NAME="title" >< /H1 >
< HR >
< BR >
< B >You authenticated as: < /B > < TMPL_VAR NAME="ENV_REMOTE_USER" >< BR >< BR >
< TMPL_IF NAME="oranges" >You prefer oranges< /TMPL_IF >
< /BODY >
< /HTML >
in your script:
use HTML::Template::Set;
my $tmpl = new HTML::Template::Set(
filename => foo.tmpl,
associate_env => 1
);
my $handler = $tmpl->param(handler);
if ($handler and $handler eq apples_to_oranges) {
$tmpl->param(oranges => 1);
}
print $tmpl->output();
<<lessSYNOPSIS
in your HTML:
< TMPL_SET NAME="handler" >apples_to_oranges< /TMPL_SET >
< TMPL_SET NAME="title" >Apples Are Green< /TMPL_SET >
< HTML >
< HEAD >
< TITLE >< TMPL_VAR NAME="title" >< /TITLE >
< /HEAD >
< BODY >
< H1 >< TMPL_VAR NAME="title" >< /H1 >
< HR >
< BR >
< B >You authenticated as: < /B > < TMPL_VAR NAME="ENV_REMOTE_USER" >< BR >< BR >
< TMPL_IF NAME="oranges" >You prefer oranges< /TMPL_IF >
< /BODY >
< /HTML >
in your script:
use HTML::Template::Set;
my $tmpl = new HTML::Template::Set(
filename => foo.tmpl,
associate_env => 1
);
my $handler = $tmpl->param(handler);
if ($handler and $handler eq apples_to_oranges) {
$tmpl->param(oranges => 1);
}
print $tmpl->output();
Download (0.009MB)
Added: 2007-08-16 License: Perl Artistic License Price:
799 downloads
MAT Template Library 0.1.7
MAT is a C++ mathematical template class library. more>>
MAT Template Library is a C++ mathematical template class library. The library contains classes and routines for working with:
matrices
vectors
finding roots of polynomials
solving equations
and more...
<<lessmatrices
vectors
finding roots of polynomials
solving equations
and more...
Download (0.068MB)
Added: 2006-09-28 License: MIT/X Consortium License Price:
1122 downloads
MfGames.Template 1.1.0
The MfGames.Template library is a C# native library for creating template libaries. more>>
The MfGames.Template library is a C# native library for creating template libaries.
MfGames.Template was inspired by NVelocity, but was designed from the ground up to use the CIL internals, such as System.CodeDom and internal compliation to handle the template language.
Because of this, it supports C# code as the template "language". In addition, compiled templates are actually compiled down into bytecode, using the built-in compiler.
<<lessMfGames.Template was inspired by NVelocity, but was designed from the ground up to use the CIL internals, such as System.CodeDom and internal compliation to handle the template language.
Because of this, it supports C# code as the template "language". In addition, compiled templates are actually compiled down into bytecode, using the built-in compiler.
Download (0.017MB)
Added: 2006-04-07 License: LGPL (GNU Lesser General Public License) Price:
1295 downloads
Piffle::Template 0.3.1
Piffle::Template is a Perlish templating language. more>>
Piffle::Template is a Perlish templating language.
SYNOPSIS
use Piffle::Template;
use Piffle::Template qw{template_to_perl expand_template};
# OO syntax, with output stored and returned:
print Piffle::Template->expand(source_file => foo/fish.xml,
include_path => [foo/inc,foo]);
# Immediate: OO syntax: output goes directly to STDOUT:
Piffle::Template->expand(source_file => foo/fish.xml,
output_file => *STDOUT);
# Procedural syntax, data from a string
$string =
< ?perl } ? >
< ?include std_disclaimer.txt? >
__END__
expand_template(source => $string,
output_file => *FILE);
This is a simple Perl-embedding syntax for template code which is geared towards allowing authors to validate their templates directly against schemas or DTDs. The embedded language is Perl itself, which allows great flexibility at the expense of having to be disciplined about the barrier between template code and module code.
In operation, the source template is transformed to an in-memory Perl script which is then run using Perls eval operator. Errors can be redirected to files or subroutines, and the output can be either caught in a variable or written to a file or open filehandle.
<<lessSYNOPSIS
use Piffle::Template;
use Piffle::Template qw{template_to_perl expand_template};
# OO syntax, with output stored and returned:
print Piffle::Template->expand(source_file => foo/fish.xml,
include_path => [foo/inc,foo]);
# Immediate: OO syntax: output goes directly to STDOUT:
Piffle::Template->expand(source_file => foo/fish.xml,
output_file => *STDOUT);
# Procedural syntax, data from a string
$string =
< ?perl } ? >
< ?include std_disclaimer.txt? >
__END__
expand_template(source => $string,
output_file => *FILE);
This is a simple Perl-embedding syntax for template code which is geared towards allowing authors to validate their templates directly against schemas or DTDs. The embedded language is Perl itself, which allows great flexibility at the expense of having to be disciplined about the barrier between template code and module code.
In operation, the source template is transformed to an in-memory Perl script which is then run using Perls eval operator. Errors can be redirected to files or subroutines, and the output can be either caught in a variable or written to a file or open filehandle.
Download (0.009MB)
Added: 2006-09-13 License: Perl Artistic License Price:
1136 downloads
CGI::FastTemplate 1.09
CGI::FastTemplate is a Perl extension for managing templates, and performing variable interpolation. more>>
CGI::FastTemplate is a Perl extension for managing templates, and performing variable interpolation.
SYNOPSIS
use CGI::FastTemplate;
$tpl = new CGI::FastTemplate();
$tpl = new CGI::FastTemplate("/path/to/templates");
CGI::FastTemplate->set_root("/path/to/templates"); ## all instances will use this path
$tpl->set_root("/path/to/templates"); ## this instance will use this path
$tpl->define( main => "main.tpl",
row => "table_row.tpl",
all => "table_all.tpl",
);
$tpl->assign(TITLE => "I am the title.");
my %defaults = ( FONT => "",
EMAIL => jmoore@sober.com,
);
$tpl->assign(%defaults);
$tpl->parse(ROWS => ".row"); ## the . appends to ROWS
$tpl->parse(CONTENT => ["row", "all"]);
$tpl->parse(CONTENT => "main");
$tpl->print(); ## defaults to last parsed
$tpl->print("CONTENT"); ## same as print() as "CONTENT" was last parsed
$ref = $tpl->fetch("CONTENT");
<<lessSYNOPSIS
use CGI::FastTemplate;
$tpl = new CGI::FastTemplate();
$tpl = new CGI::FastTemplate("/path/to/templates");
CGI::FastTemplate->set_root("/path/to/templates"); ## all instances will use this path
$tpl->set_root("/path/to/templates"); ## this instance will use this path
$tpl->define( main => "main.tpl",
row => "table_row.tpl",
all => "table_all.tpl",
);
$tpl->assign(TITLE => "I am the title.");
my %defaults = ( FONT => "",
EMAIL => jmoore@sober.com,
);
$tpl->assign(%defaults);
$tpl->parse(ROWS => ".row"); ## the . appends to ROWS
$tpl->parse(CONTENT => ["row", "all"]);
$tpl->parse(CONTENT => "main");
$tpl->print(); ## defaults to last parsed
$tpl->print("CONTENT"); ## same as print() as "CONTENT" was last parsed
$ref = $tpl->fetch("CONTENT");
Download (0.013MB)
Added: 2006-08-01 License: Perl Artistic License Price:
1179 downloads
Template::Ast 0.02
Template::Ast is a Perl module to process ASTs for Perl Template Toolkit. more>>
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.
<<lessSYNOPSIS
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.
Download (0.020MB)
Added: 2007-06-29 License: Perl Artistic License Price:
847 downloads
OpenSharePoint 0.4.20070126
OpenSharePoint is an intra/extranet portal server similar to SharePoint. more>>
OpenSharePoint is an intra/extranet portal server similar to SharePoint.
OpenSharePoint project provides a place on the Web where a team can communicate, share documents, and work together on a project.
A separate team Website can be created for every project that is being worked on.
OSP is alternative groupware that provide a place on the web where your team can communicate,share documents and work together.You can contribute to the team website using nothing more than a web browser!, OSP provide more tool to communicate like News, Forum, Webbase E-Mail and etc. You can install new modules/block with easy way via using your web browser.
Enhancements:
- Installation problems were fixed and the core APIs were updated.
<<lessOpenSharePoint project provides a place on the Web where a team can communicate, share documents, and work together on a project.
A separate team Website can be created for every project that is being worked on.
OSP is alternative groupware that provide a place on the web where your team can communicate,share documents and work together.You can contribute to the team website using nothing more than a web browser!, OSP provide more tool to communicate like News, Forum, Webbase E-Mail and etc. You can install new modules/block with easy way via using your web browser.
Enhancements:
- Installation problems were fixed and the core APIs were updated.
Download (3.2MB)
Added: 2007-03-22 License: GPL (GNU General Public License) Price:
950 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above sharepoint templates search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed