I think you mean File::Finder vs File::Find::Rule. And in fact, that's true. I looked at the prior art in File::Find::Rule, even the implementation, and decided I could do better. And I both acknowledge that in the docs (about FFR), I also embrace the existing FFR plugins with my own "ffr" method in File::Finder.
But everyone seems uppity that I'm trying to do the same thing with CGI::Application. No, please, no. I looked at everything out there for what I needed for my client. Nothing worked. I didn't set out to define a "better CGI::Application". I set out to define a generic MVC metacontroller that would easily subclass to be the controllers I needed for a few of my clients. Nobody has done that. CGI::Application isn't it, nor does it pretend to be it.
So, please stop comparing this to CGI::Application, any more than you'd compare Template Toolkit to Embperl. They're not the same class of framework. They have different goals.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.