As a general tip for anyone that might be listening, one thread per
proposed module seems best (with a more specific subject line.)
Providing docs and example code usually helps clarify what the
module/app does if you're looking for feedback on naming.
# from Jim Schneider
# on Sunday 12 March 2006 03:44 pm:
>3) Well, I'm currently calling it TemplateLoader, but that's too
> horrible for words. Your provide some particulars on the module
> "use" line, and it creates a method in the calling class that loads
> the template. Any suggestions for this one would definitely be
> appreciated.
What kind of templates does it load? What sort of API does it provide?
It seems (in my fuzzy "application model") that it works something like:
use MakeMethod::TemplateLoader (
new_template => {param => "foo"}
);
...
my $tmpl = $self->new_template(val => $bar);
In which case it has something in common with Class::Accessor and other
OO functionality modules, but it relies on template toolkit or ...?
But it isn't a base class although it injects methods into your
namespace? If so, it sounds a bit like a Trait, though
Trait::TemplateLoader isn't quite right.
The fact that template has meaning in the context of methods (e.g. the
C++ meaning and the more general prototype meaning) isn't going to
help. Template::LoaderMethod?
--Eric
--
The opinions expressed in this e-mail were randomly generated by
the computer and do not necessarily reflect the views of its owner.
--Management
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
