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
Given that DBIx::Class is an alternative/replacement for Class::DBI and
thus is a fairly substantial project in its own right, I'd rather see
you find a different name -- a noncompatible ::Simple is more confusing
than helpful.
Likewise, there's already a well-known DBIx::Simple -- which has nothing
do with object-relational mapping, so an unrelated
DBIx::Simple::Class/Object is similarly confusing.
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".
DBIx::Objects is taken, but DBIx::ORM is available, so maybe something
like DBIx::ORM::Simple (or replace "Simple" with a better adjective)
would work for you.
If you really want "simple" in there, there are several modules of the
compound type DBIx::SimpleNoun, so maybe DBIx::SimpleObjects or
DBIx::SimpleORM would work for you. Replace Simple with Easy likewise.
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
As a side note, a quick CPAN search on "USPS" reveals
Scrape::USPS::ZipLookup -- so you might want to address how your module
is different/better.
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.
Regards,
David Golden
