Please don't misquote me. I never said that a Moose-based CGIP was out of the question. I said a non-prototype-Moose base class would not be acceptable.
Yes, that's right. I was typing in a hurry and made an overly general statement. My apology.
All you have to do is use a prototype-Moose base class, which either exists already, or is just a small matter of programming.
I would rather lean on standard Moose
  1. so I can leverage all the Moose extensions that exist
  2. so I dont have to worry about a splinter project and its potential bugs
Or, you can go off and do what you want. Just don't call it CGI::Prototype until it's prototype-based.
  1. You should change your docs. You say that CGIP creates a CGI application by subclassing which implies class-based OOP
  2. You should improve your docs (similar to my fork). When people scan your docs or your Linux magazine articles, they see nothing that cant be done just as easily with class-based OOP or CGI::Application. You need to motivate the unique position of this module with some exemplary sample code SOMEWHERE
  3. Please embrace the multiple concepts of prototype. A CGI prototype could be something which prototypes the CGI request cycle. And CGIP does an excellent job of that, regardless of which object system it uses. There's no need for a separate distribution for something which has largely the same code.

In reply to Re^2: a Moose CGIP shall not receive merlyn's blessing by metaperl
in thread CGI::Prototype leverages objects for web app control by metaperl

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.