We do something very similiar, but we match run modes, module and templates - run modes rm_XXX is handled by the MyApp::XXX::run(), which pulls in the HTML::Template XXX.tmpl.

I guess if you wanted to handle inheritance, you could write some kind of BEGIN block in the derived modules that builds some kind of register at compile time, that is then used by setup() to build the CGI::App instance from. Then you just need to remember to do that for each derived module...hmmm maybe that just makes a different 'I always forget to ...' problem.

...it is better to be approximately right than precisely wrong. - Warren Buffet

In reply to Re: CGI::Application - A little too lazy? by leriksen
in thread CGI::Application - A little too lazy? by friedo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.