David Golden wrote:
Jim Schneider wrote:
I have three modules I am preparing to submit to CPAN, and I was
hoping to get some input on the names.
The modules are:
1) DBIx::Class::Simple - a simpler alternative to DBIx::Class, but
alas, not compatible (not even a little bit). It takes a collection
of data structures that describe your tables, and turns it into a
collection of classes that can be used to access them. I'm also open
to the name DBIx::Simple::Class or DBIx::Simple::Object
[...]
I think you may be best if you come up with your own DBIx::* name that
captures what you feel is distinctive about your module -- beyond it
just being "simple".
Seconded. Simple modules never are. I'm not trying to be flippant. If
the documentation isn't equally simple (for instance, fits on a
screenful with no additional provisos or exceptions) then the person
using it spends as much time learning how to use it as a supposedly more
"complex" module.
2) WWW::Scraper::Zip4 - a simple web scraper to retrieve address
information from the USPS website.
Again, there is already an unrelated WWW::Scraper, so I'd avoid that.
There seems to be an emerging style for these kinds of web interfaces
that is site-first, task-second, so how about this (with the additional
clarity of the proper name of a nine-digit zip):
WWW::USPS::ZipPlus4
Again, seconded. I was going to say the same thing (although I suppose
the Zip4/ZipPlus4 distinction refers some sort of regional context that
is lost on me).
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.
This is far too generic a description to offer help. Given the myriad
templating systems already out there, can you describe what your module
does that is distinctive? That's usually a good place to start when
thinking about names.
Or a snippet showing how the module (?:sh|c|w)ould be used.
David
--
"It's overkill of course, but you can never have too much overkill."
