Free video script template software for linux

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.

Movie2XviD is a script for encoding a DVD or other movie to AVI (XviD).
Auto computing bitrate and hight quality, but it is a little slowly.
Enhancements:
- Add options
- video filter
- help
- new computing bitrate

News Script allows you to write articles for your website. News Script features a WYSIWYG editor which makes writing an article easy and it supports search engine friendly URLs.
Main features:
- Write, edit and delete text articles
- Use the built-in WYSIWYG editor for formatting
- Create search engine friendly URLs
- List and search in existing articles
- Completely template driven
- Installation routine
How the script works
As the admin you can write new articles and list, edit, delete and search in existing ones.
News script features a WYSIWYG editor that gives you full control over the format of an article. JavaScript is required, though. The script allows you to choose an article date and the date when the article is to be published.
The title of an article appears as part of the URL which is good for search engine optimization. In case your server supports mod_rewrite the article URL looks like a normal URL of an HTML page.
On the front end the visitor will be provided with a list of published articles. As admin you can set the number of articles per page which results in several result pages which can be browsed by the visitor.

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.

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.

SILVERCODERS T-Script is a scripting language which primary purpose is to generate text files.

It can be useful for processing template files based on some additional data retrieved from data sources like sql databases or other text files. T-Script can be easly embedded into your application and work with its internal data.

SILVERCODERS T-Script library is now being intergrated into the LMS project.

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.