Free template plugin mp3 tag software for linux

Template::Plugin::MP3::Tag is a Perl interface to the MP3::Tag Module.

SYNOPSIS

[% USE tag = MP3("path_to_mp3_file") %]

[% tag.title %]
[% tag.album %]

# perldoc MP3::Tag for more ideas

Template::Plugin::MP3::Tag provides a simple wrapper for using MP3::Tag in object oriented mode; see MP3::Tag for more details.

Although Template::Plugin::MP3 can fetch MP3 files, but it Supports only ID3v1. When you have to fetch MP3 files ID3v2, I recommend you to use this module.

Template::Plugins is a Perl module with plugin provider.

SYNOPSIS

use Template::Plugins;

$plugin_provider = Template::Plugins->new(%options);

($plugin, $error) = $plugin_provider->fetch($name, @args);

The Template::Plugins module defines a provider class which can be used to load and instantiate Template Toolkit plugin modules.

Template::Plugin::SumOf is a Perl module to calculate the sum with VMETHODS.

SYNOPSIS

# in your script
use Template;
use Template::Plugin::SumOf;
my $tt = Template->new;
$tt->process(
template.html,
{
ary => [
{ date => 2006-09-13, price => 300 },
{ date => 2006-09-14, price => 500 }
]
}
)
or die $tt->error;

# in your template.
[% USE SumOf -%]
[%- FOR elem IN objects -%]
[% elem.date %],[% elem.price %]
[% END -%]
,[% objects.sum_of(price) %]

# result.
2006-09-13,300
2006-09-14,500
,800

You can easy to calcurate sum of array, with VMETHODS.

Template::Plugin::Java is a Perl module that can generate Java Classes from XML description files and templates.

SYNOPSIS

From an xml file such as:
< aBean >
< java: option1="value1" >
< option2 >value2< /option2 >
< /java: >
< foo >10< /foo >
< bar >String< /bar >
< container >
< baz >20< /baz >
< /container >
< /aBean >

Through the program "tjava":

tjava [options] [file.xml ...]

Via a template, such as:

[% USE Java %]
package $package;

public class $class {

[% FOREACH Java.variables %]
$type $name = $initializer;
[% END %]

//... etc
}

To generated Java source code in the appropriate directory as determined by the package of the .xml files directory, specified package option if any, and CLASSPATH.

OPTIONS

Any options may be given besides those listed, these are passed directly to the Templates being processed in the stash (the variable table at time of processing). They can be given in the < java: > ... < /java: > section of an XML file (in which case, dont use the -- dashes) as attributes or elements, or on the command line.

--template

Name of the template to process. No extension is assumed by default unlike in the previous version.

--package

Destination package to put the generated classes, otherwise will be determined from how the current directory relates to the CLASSPATH.

--class

Class name to use, otherwise will infer from the root tag of the XML file.

--templatePath

Colon separated path where the templates can be found, overrides the environment variable TEMPLATEPATH. This doesnt work right now, so use the TEMPLATEPATH environment variable.

--genContainers

If set to 0, classes for subcontainers will not be generated. This is generally not useful.

--containerTemplate

By default set to Container, this is the default template, as well as the template used for sub-containers.

--containerNamePrefix

By default, if generating class Foo that needs to have a sub container wrapped in tag < bar >, its name will be FooBar. This is safe and wont cause collisions with different classes having sub containers of the same name (until some sort of dependency checking code is introduced). To turn this off, set it to the empty string "".

--interface

Interface to add to list of implemented interfaces, can be supplied multiple times. Make sure you append any necessary code to implement any of these interfaces.

--append

Text to insert in the generated class body.

--appendFile

Will insert text read from the file specified into the generated class body. This option and the --append option are mutually exclusive.

--file[s]

The XML file(s) to parse. This is useful for when the Plugin is instantiated from a custom script, not via tjava or inside a template.

Any other option will be placed into the stash for the templates to use, making tjava very useful with your custom templates.

Anything thats not an option will be assumed to be a file.

Template::Plugin::XML::Simple is a plugin interface to XML::Simple.

SYNOPSIS

# load plugin and specify XML file to parse
[% USE xml = XML.Simple(xml_file_or_text) %]

This is a Template Toolkit plugin interfacing to the XML::Simple module.

Template::Plugin::Datum is a Perl module with TT2 plugin that converts international date format to German date format.

SYNOPSIS

[% USE Datum %]

von: [% 20030101 | datum %] -> 01.01.2003
bis: [% 2003-12-31 | datum %] -> 31.12.2003

Zeitstempel: [% 20031212143000 | datum %] -> 12.12.2003 14:30:00

This plugin converts international date format (year-month-day) to German date format (day.month.year).

Recognized formats are:

yyyy-mm-dd (2003-12-31)
yyyymmdd (20031231)
yyyymmddHHMMSS (20031231143000) date and time

Template::Plugin::ASCIITable is a Perl module that allows you to use Text::ASCIITable in your templates.

SYNOPSIS

[% USE ASCIITable %]
blah
[% ASCIITable.cols(a, b, c);
ASCIITable.rows([1,2,3],[one,two,three]);
ASCIITable.draw() %]

A plugin object will be instantiated with the directive:

[% USE ASCIITable %]

You can pass a number of parameters to the constructor, for example:

[% USE ASCIITable(cols => [a,b,c], show=>rowline) %]

See "Parameters" for details.

To obtain the table, you invoke the draw method, to which you can pass the same parameters:

[% ASCIITable.draw(rows=>[[1,2,3],[one,two,three]]) %]

METHODS

new

This is the plugin construtor. You should never call it directly: use the USE directive.

draw

This method invokes Text::ASCIITable to obtain the textual representation of the table, and returns it.

You can pass various parameters to it, see "Parameters".

Template Lite is a smaller, faster alternative to the Smarty template engine.
For the most part, it is a drop in replacement for Smarty but uses around half of the memory and is considerably faster and far less CPU intensive when compiling and displaying templates.
Template lite was originally created by Paul Lockaby as a smaller replacement for Smarty. The original package was called Smarty Light. Even though Smarty is an Open Source project the creators of Smarty decided to trademark the name Smarty. Because of this trademarking of the name they contacted Paul Lockaby and told him he could nolonger use Smarty in the name for the package.
Paul Lockaby gave me permission to fork the project if I wanted as he was closing down support and developement for Smarty Light. The initial release of Template Lite contains a few minor bug fixes and some extra features.
I plan on adding more features to Template Lite over the next few months. For the most part Template Lite is a drop in replacement for Smarty. The nice thing about this package is how it uses around half of the memory of Smarty and it is considerably FASTER and far less CPU intensive when compiling and displaying templates.
Enhancements:
- register_resource and unregister_resource support was added.
- Different resources are supported by everything except for cached template output.
- The _get_resource internal function was added for processing "file:" and absolute tag resources.
- The resize_image plugin was added.
- Support for absolute paths to template files was fixed.