Request for naming help (templating module)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,

I have recently written a templating module and released it to
CPAN. There are approximately aleph-null templating modules already
on CPAN, but I honestly believe that there is a niche for this new
one. Its niche is "simplicity"; it is fairly minimalist, easy to
use, fast, and (I'd like to think) easy to learn.

[Side note: I think that the Template Toolkit, Text::Template,
and Mason are *fantastic*, but when you need something simple, like
for a couple of one-liners, they can be unwieldy and cumbersome,
imho]

I have tentatively named my module Text::QuickTemplate, and you
can find it on CPAN under that name. I asked the Naming Gods to
bless this name into the official registry, and brian d foy
hesitated. He brought up some objections to the name, and I
reluctantly admit he has some valid points.

You can follow the whole discussion in the modules@perl.org
archive for last month at

http://www.xray.mpe.mpg.de/mailing-lists/modules/2005-08/thr eads.html
(search for "QuickTemplate")
But the gist of it is: brian d foy feels that the name is not
suggestive enough of what the module's about. It doesn't say to the
programmer what separates it from the other templating modules. He
suggests that the module's name should perhaps focus on its
printf-like behavior; on that point, I disagree. But hey -- in
general, I agree with him.

So help me come up with a better name, please. I think it should
go in the Text:: top-level hierarchy. I also think that it should
have Template somewhere in its name. That doesn't leave a lot of
room for anything else, unfortunately. Here are some other
templating module names, for reference:

Template dTemplate Text::FastTemplate Text::FillIn Text::Macros
Text::MetaText Text::Template Text::TagTemplate Text::Templet

Here are some possiblities, to get the suggestions started:

Text::EasyTemplate
Text::StupidTemplate
Text::Overlay
Text::StringMaker
Text::ExpandPlaceholders (awfully long, don't you think?)
String::Template
String::Substitution (sounds too much like an RE
module...)

Here are what I consider to be the module's strengths, as compared to
other templating modules:

1. Simplicity; only one pure-perl module file.

2. Safety: no variable interpolation or executable content.

3. Ease of learning (I hope! ;-) and use.

4. Separation of content from computation (yeah, every template
module does that).

5. One-stop shopping (template + fill-in values) in the *printf
functions.

6. Printf-like formatting in the template placeholders, whether
the
*printf functions are used or not.

7. Speed. Text::FastTemplate blows my module away, but my module
blows away Template and Text::Template.

I welcome all suggestions, and I thank you all in advance.

- --
Eric
`$=`;$_=\%!;($_)=/(.)/;$==++$|;($.,$/,$,,$\,$",$;,$^,$#,$~,$ *,$:,@%)=(
$!=~/(.)(.).(.)(.)(.)(.)..(.)(.)(.)..(.)......(.)/,$"),$=++; $.++;$.++;
$_++;$_++;($_,$\,$,)=($~.$"."$;$/$%[$?]$_$\$,$:$%[$?]",$"&$~ ,$#,);$,++
;$,++;$^|=$";`$_$\$,$/$:$;$~$*$%[$?]$.$~$*${#}$%[$?]$;$\$"$^ $~$*.>&$=`
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32) - WinPT 0.7.96rc1

iD8DBQFDIRE0Y96i4h5M0egRAg1vAJ9AihnxoY+MlKZTPicBd4+J0GgNBgCg 6crV
H70ZzkGLehPRCPtHgR+evvE=
=n33P
-----END PGP SIGNATURE-----

Re: Request for naming help (templating module)

"Eric J. Roode" wrote:

> I have tentatively named my module Text::QuickTemplate, and you
> can find it on CPAN under that name. I asked the Naming Gods to
> bless this name into the official registry, and brian d foy
> hesitated. He brought up some objections to the name, and I
> reluctantly admit he has some valid points.

Mine would be: Quick = Speed, I would read that as speed of execution.

Lean? Simple?

> Here are some possiblities, to get the suggestions started:
>
> Text::EasyTemplate


Text::LeanTemplate
Text::SimpleTemplate

> Text::StupidTemplate
> Text::Overlay
> Text::StringMaker

bad names

> Text::ExpandPlaceholders (awfully long, don't you think?)
> String::Template
> String::Substitution (sounds too much like an RE
> module...)
>
> Here are what I consider to be the module's strengths, as compared to
> other templating modules:
>
> 1. Simplicity; only one pure-perl module file.

Text::SimpleTemplate

--
John Small Perl scripts: http://johnbokma.com/perl/
Perl programmer available: http://castleamber.com/
Happy Customers: http://castleamber.com/testimonials.html

Re: Request for naming help (templating module)

Template maybe should be a top-level namespace it is so common...

> "Eric J. Roode" wrote:
>
>> I have tentatively named my module Text::QuickTemplate, and you
>> can find it on CPAN under that name. I asked the Naming Gods to
>> bless this name into the official registry, and brian d foy
>> hesitated. He brought up some objections to the name, and I
>> reluctantly admit he has some valid points.
>
> Mine would be: Quick = Speed, I would read that as speed of execution.
>
> Lean? Simple?
>
>> Here are some possiblities, to get the suggestions started:
>>
>> Text::EasyTemplate
>
>
> Text::LeanTemplate
> Text::SimpleTemplate
>
>> Text::StupidTemplate
>> Text::Overlay
>> Text::StringMaker
>
> bad names
>
>> Text::ExpandPlaceholders (awfully long, don't you think?)
>> String::Template
>> String::Substitution (sounds too much like an RE
>> module...)
>>
>> Here are what I consider to be the module's strengths, as compared to
>> other templating modules:
>>
>> 1. Simplicity; only one pure-perl module file.
>
> Text::SimpleTemplate
>
> --
> John Small Perl scripts: http://johnbokma.com/perl/
> Perl programmer available: http://castleamber.com/
> Happy Customers: http://castleamber.com/testimonials.html
>

--
Carter's Compass: I know I'm on the right track when,
by deleting something, I'm adding functionality.

Re: Request for naming help (templating module)

John Bokma wrote in
news:Xns96CC54A36E26Ccastleamber@130.133.1.4:

> "Eric J. Roode" wrote:
>
>> I have tentatively named my module Text::QuickTemplate, and you
>> can find it on CPAN under that name. I asked the Naming Gods to
>> bless this name into the official registry, and brian d foy
>> hesitated. He brought up some objections to the name, and I
>> reluctantly admit he has some valid points.
>
> Mine would be: Quick = Speed, I would read that as speed of execution.
>
> Lean? Simple?
>
[...]
>>
>> 1. Simplicity; only one pure-perl module file.
>
> Text::SimpleTemplate


Hmm, that's not bad...

--
Eric
`$=`;$_=\%!;($_)=/(.)/;$==++$|;($.,$/,$,,$\,$",$;,$^,$#,$~,$ *,$:,@%)=(
$!=~/(.)(.).(.)(.)(.)(.)..(.)(.)(.)..(.)......(.)/,$"),$=++; $.++;$.++;
$_++;$_++;($_,$\,$,)=($~.$"."$;$/$%[$?]$_$\$,$:$%[$?]",$"&$~ ,$#,);$,++
;$,++;$^|=$";`$_$\$,$/$:$;$~$*$%[$?]$.$~$*${#}$%[$?]$;$\$"$^ $~$*.>&$=`

Re: Request for naming help (templating module)

Terrence Brannon wrote in
news:6mek7yuilz.fsf@Abulafia.hcoop.net:

> Template maybe should be a top-level namespace it is so common...
>

That might be nice.. but Template.pm is the Template Toolkit, and it has
many sub-modules in the Template::* namespace hierarchy, so I think it
would be confusing if anyone else (eg me) were to put any non-TT modules
into Template::*.

--
Eric
`$=`;$_=\%!;($_)=/(.)/;$==++$|;($.,$/,$,,$\,$",$;,$^,$#,$~,$ *,$:,@%)=(
$!=~/(.)(.).(.)(.)(.)(.)..(.)(.)(.)..(.)......(.)/,$"),$=++; $.++;$.++;
$_++;$_++;($_,$\,$,)=($~.$"."$;$/$%[$?]$_$\$,$:$%[$?]",$"&$~ ,$#,);$,++
;$,++;$^|=$";`$_$\$,$/$:$;$~$*$%[$?]$.$~$*${#}$%[$?]$;$\$"$^ $~$*.>&$=`

Re: Request for naming help (templating module)

"Eric J. Roode" writes:

> programmer what separates it from the other templating modules. He
> suggests that the module's name should perhaps focus on its
> printf-like behavior; on that point, I disagree.

I think I agree with Brian on this one - the other aspects you list are
rather common in regards to other template modules. The printf formatting
is the most unique standout feature your module offers.

With that in mind, I suggest:

Text::Template::Format
Text::Template::Printf

sherm--

--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org