It's largely a matter of personal preferences. My template files end in ".tmpl" for example. Also I would want to include some extra files, like certain template files, a minimal CSS files, a .png that I always use etc etc. I got the impression that your module was simply an expression of your personal preferences and I could not see a point in requesting changes based on personal preferences. Nor could I see any value in trying to derive from such a class. So it needs to be a lot more flexible to be useful to me (though of course the defaults can reflect your personal preferences). I suppose philosophically, a Module::Starter::CGIApp
has gone too far by its very choice of name. A module that was sufficiently flexible to be of use to me in this context, could be used for things that were not related to CGI::Application
. This is why I am drawn to the module that simply tries to derive from Module::Starter::Plugin::Template
by filling in the abstract methods with a choice of templating engine. True it is not my favourite templating engine, but this sounds a better bet than any other option.