NAME ExtUtils::ModuleMaker::TT - Makes skeleton modules with Template Toolkit templates SYNOPSIS use ExtUtils::ModuleMaker::TT; my $mmtt = ExtUtils::ModuleMaker::TT->new ( NAME => 'My::New::Module', TEMPLATE_DIR => '~/.perltemplates' ); $mmtt->complete_build(); DESCRIPTION This module extends ExtUtils::ModuleMaker to use Template Toolkit 2 (TT2) to build skeleton files for a new module. Templates may either be default templates supplied within the module or user-customized templates in a directory specified with the *TEMPLATE_DIR* parameter. Summary of Features/Enhancements: * Supports building full module skeletons with all the functionality of ExtUtils::ModuleMaker * Supports adding a single .pm file (and corresponding .t file) to an existing module distribution tree. * Supports creating skeleton text for a single method (generally to be called via a script from within your favorite editor) * Can create a template directory containing the default templates for subsequent user customization * Templates can access any parameter in the creating object (e.g. $mmtt, above). This supports transparent, user-extensible template variables for use in custom templates * Included script *makeperlmod* provides a command line user interface for module creation. Supports reading default configuration settings from a file and will create a default config file if requested. Can create full distributions, single modules, single methods, or default template directories Notable changes from ExtUtils::ModuleMaker: * *complete_build* now takes arguments that are added to or overwrite the current configuration * Default templates are generally simpler and more compact * Also creates a MANIFEST.SKIP file with reasonable default contents * Tests are named after their corresponding .pm files rather than being sequentially numbered. This change supports the "single .pm" mode more consistently. E.g., for "Sample::Module", a test file "Sample_Module.t" is created * Supports both 'Module::Build and Proxy' and 'Module::Build and proxy Makefile.PL' as *BUILD_SYSTEM* synonyms to cover discrepancy between ExtUtils::ModuleMaker code and pod USAGE Generally, users should just use the included script, makeperlmod. For example, the following command will create a module distribution using default settings: makeperlmod -n Sample::Module See the makeperlmod man page for details on creating a custom configuration file (for setting author details and other ExtUtils::ModuleMaker options). The "CUSTOMIZING TEMPLATES" section below contains other examples. ExtUtils::ModuleMaker::TT can also be used programatically via the object methods defined below. The makeperlmod source provides a practical example of this approach. PUBLIC METHODS new $mmtt = ExtUtils::ModuleMaker::TT->new ( %config ); Uses the same configuration options as ExtUtils::ModuleMaker. Users may also define a *TEMPLATE_DIR* parameter, in which case that directory will be used as the source for all templates. See "CUSTOMIZING TEMPLATES", below. Returns a new ExtUtils::ModuleMaker::TT object. complete_build $mmtt->complete_build(); or $mmtt->complete_build( NAME => 'Sample::Module' ); Builds a complete distribution skeleton. Any named parameters are added to the configuration (overwriting any existing values) prior to building. It returns the distribution directory created. (Helpful in scripts.) build_single_pm $mmtt->build_single_pm( $module ); Creates a new .pm file and a corresponding .t file. The *$module* parameter may be either a hash reference containing configuration options (including *NAME*) or a string containing the name of a module, in which case the default configuration will be used. E.g.: $module = { NAME => 'Sample::Module', NEED_POD => 0 }; or $module = 'Sample::Module'; This method must be able to locate the base directory of the distribution in order to correctly place the .pm and .t files. A *complete_build()* call sets the *Base_Dir* parameter appropriately as it creates the distribution directory. When called on a standalone basis (without a *complete_build()* call), the caller must be in a working directory within the distribution tree. When *Base_Dir* is not set, this method will look in the current directory for both a 'MANIFEST' file and a 'lib' directory. If neither are found, it will scan upwards in the directory tree for an appropriate directory. Requiring both files prevents mistakenly using either a template directory or a unix root directory. The method will croak if a proper directory cannot be found. The working directory in use prior to the method being called will be restored when the method completes or croaks. Returns a true value if successful. build_single_method $mmtt->build_single_method( $method_name ); Returns a string with a skeleton method header for the given *$method_name*. Used internally, but made available for use in scripts to be called from your favorite editor. create_template_directory $mmtt->create_template_directory( $directory ); Creates the named *$directory* and populates it with a file for each default template. These can be customized and the directory used in conjunction with the *TEMPLATE_DIR* configuration options. See "CUSTOMIZING TEMPLATES", below. Returns a true value if successful. INTERNAL METHODS These methods are used internally. They are documented for developer purposes only and may change in future releases. End users are encouraged to avoid using them. Create_Base_Directory Overrides the parent. Same function, but sets the Base_Dir parameter to an absolute file path. (Helpful for single-module builds) process_template $mmtt->process_template( $template, \%data, $outputfile ); Calls TT to fill in the template and write it to the output file. Requires a template name, a hash reference of parameters, and an outputfile (relative to the base distribution directory). If the *TEMPLATE_DIR* parameter is set, templates will be taken from there, otherwise the default templates are used. Returns a true value if successful. default_templates $mmtt->default_templates(); Generates the default templates from <