in reply to Moving A Template Module Namespace

I vote for DaintyFlower. Names get meanings as people use them. Make a public svn, start a mailing list, write about it for perl publications, meditate on it here. Either, we won't want to switch to it, in which case the name is immaterial. Or, we will like what we read and try it, in which case the name is almost immaterial. Only new people searching for templates might miss it and then only if the docs don't have the word template promonently placed.

The chief advantage of DaintyFlower (or other similar names) is their googlibility. Searching for perl template is likely to work, searching for DaintyFlower is sure to.

Others I might like as more straightforward: Template::Pluggable, Template::Flex, or Template::YATS. Best of all: Template::DaintyFlower.

Phil

The Gantry Web Framework Book is now available.

Replies are listed 'Best First'.
Re^2: Moving A Template Module Namespace
by Rhandom (Curate) on May 23, 2007 at 20:19 UTC
    So if it is to be Template::DaintyFlower style, are there any other good suggestions of random names? DaintyFlower was just a random suggestion. My internal random name generator isn't outputting as much as I'd like.

    Seriously - any random or non-sensical suggestions will be entertained. I think I am looking for short/easy to say/hard to misspell ideas (prefixed with Template:: is fine).

    my @a=qw(random brilliant braindead); print $a[rand(@a)];
      How about HotHouse? It's a little shorter and suggests a broader utility than one fragile flower. Or, for a stronger plant: FlyTrap. Perhaps you could take a tour through a thersarus starting with template and prototype.

      Phil

      The Gantry Web Framework Book is now available.