Re: Template oriented module
On Mon, Jun 16, 2008 at 6:44 AM, Ivan Wills [EMAIL PROTECTED] wrote: Hi, I have been working on converting a script that I have been using for my self for a while which I use as a templating engine in vim and for creating whole new files (and soon creating whole directory trees from templates). It uses template toolkit for the actual templates. I have several questions about this before I try to put the module on CPAN first what should I call this (my current script is called itemplate but that doesn't seem to fit with CPAN naming conventions). The next question is should I include the templates I use with the module? I have templates that generate perl scripts and packages that follow PBP as well as XHML skelitons etc. If I include these template files, how do I make Module::Build install them and how do I determine where the templates have been installed so that I can create the Template toolkit path correctly? Finally I have been thinking of creating a module to handle svn (or cvs, net etc) like commandline parameters (ie cmd subcmd -parms ...) which I will use with this module (and also sick on CPAN). It will use Getopt::Long for most of its functionality but will be able to do work of finding what parameters each sub command accepts. So again what would be a good name I imagine Getopt::something (SubCommand?) Any suggestions would be helpful Thanks Ivan Wills -- email/jabber: [EMAIL PROTECTED] / / _ _ / \ / | | | | / \/ \_| | | I'm now thinking of calling the module Template::CMD or possibly Template::CLI depending on weather I use App::CMD or App::CLI does this make sense? -- email/jabber: [EMAIL PROTECTED] / / _ _ / \ / | | | | /\/ \_| | |
Re: Template oriented module
[Quoting Ivan Wills, on June 16 2008, 09:54, in Re: Template oriente] As for App::CLI it could do with some documentation to describe what it does and how to use it. That would be a most welcome contribution. -- Johan
Re: Template oriented module
* Ivan Wills [EMAIL PROTECTED] [2008-06-15T19:54:57] App::Cmd looks interesting but I'm not sure it does exactly what I need but will check it out further. As for App::CLI it could do with some documentation to describe what it does and how to use it. App::Cmd was largely written to do just what App::CLI does, but with more testing, documentation, and extensibility. -- rjbs
Template oriented module
Hi, I have been working on converting a script that I have been using for my self for a while which I use as a templating engine in vim and for creating whole new files (and soon creating whole directory trees from templates). It uses template toolkit for the actual templates. I have several questions about this before I try to put the module on CPAN first what should I call this (my current script is called itemplate but that doesn't seem to fit with CPAN naming conventions). The next question is should I include the templates I use with the module? I have templates that generate perl scripts and packages that follow PBP as well as XHML skelitons etc. If I include these template files, how do I make Module::Build install them and how do I determine where the templates have been installed so that I can create the Template toolkit path correctly? Finally I have been thinking of creating a module to handle svn (or cvs, net etc) like commandline parameters (ie cmd subcmd -parms ...) which I will use with this module (and also sick on CPAN). It will use Getopt::Long for most of its functionality but will be able to do work of finding what parameters each sub command accepts. So again what would be a good name I imagine Getopt::something (SubCommand?) Any suggestions would be helpful Thanks Ivan Wills -- email/jabber: [EMAIL PROTECTED] / / _ _ / \ / | | | | / \/ \_| | |
Re: Template oriented module
On Mon, Jun 16, 2008 at 06:44:53AM +1000, Ivan Wills wrote: Finally I have been thinking of creating a module to handle svn (or cvs, net etc) like commandline parameters (ie cmd subcmd -parms ...) which I will use with this module (and also sick on CPAN). It will use Getopt::Long for most of its functionality but will be able to do work of finding what parameters each sub command accepts. So again what would be a good name I imagine Getopt::something (SubCommand?) I don't have suggestions on the rest, but don't reinvent this wheel; look at App::Cmd and App::CLI (and there are probably others on CPAN that I don't know of). hdp.
Re: Template oriented module
On Jun 15, 2008, at 5:27 PM, Hans Dieter Pearcey wrote: I don't have suggestions on the rest, but don't reinvent this wheel; Unless you can make a better wheel. -- Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Re: Template oriented module
On Mon, Jun 16, 2008 at 8:27 AM, Hans Dieter Pearcey [EMAIL PROTECTED] wrote: On Mon, Jun 16, 2008 at 06:44:53AM +1000, Ivan Wills wrote: Finally I have been thinking of creating a module to handle svn (or cvs, net etc) like commandline parameters (ie cmd subcmd -parms ...) which I will use with this module (and also sick on CPAN). It will use Getopt::Long for most of its functionality but will be able to do work of finding what parameters each sub command accepts. So again what would be a good name I imagine Getopt::something (SubCommand?) I don't have suggestions on the rest, but don't reinvent this wheel; look at App::Cmd and App::CLI (and there are probably others on CPAN that I don't know of). hdp. App::Cmd looks interesting but I'm not sure it does exactly what I need but will check it out further. As for App::CLI it could do with some documentation to describe what it does and how to use it. Ivan -- email/jabber: [EMAIL PROTECTED] / / _ _ / \ / | | | | / \/ \_| | |
