In making the distinction between application framework and library framework, I can see the best counter-argument to what I've put forward. However, I still don't particularly see when something "flips the framework bit" from library to application. Had I merely posted something like HTML::TokeParser::Simple and claimed this was an "HTML parsing framework", people would have rightfully laughed at me. That would definitely be something I would call into.

With what I posted, it's clearly a "frame" which constrains code. It seems to me, though, (correct me if I'm wrong) that the key thing you two suggest for what makes a framework is that there is a particular target application type the framework is designed to support. As a result, since my code is designed to usefully constrain Perl 5's somewhat simplistic OO model in predetermined manner, are you saying that someone unlimited scope of the code is what makes it not a framework? I would think that flexible constraints are what is desirable in a framework. After all, how many times do people complain that their framework of choice limits them too much?

Mine (again, being a toy example), satisfies BrowserUK's definition "that it provides the structure of an application and leaves the application programmer to fill in the details of the specific application." I'm just stepping back and a bit and widening the class (no pun intended) of applications for this this structure is provided. As I asked elsewhere, if someone else adds integrated exception handling, someone else adds multi-method dispatch, someone else adds persistence, at what point can we call it a "framework"?

(I see where this is going, though. Most people seem to think that if I don't have a specific target application type in mind, I'm not allowed to use the word "framework".)

Update: And no worries. I didn't take the "idiot" comment as a personal attack :)

Cheers,
Ovid

New address of my CGI Course.

In reply to Re^4: Tiny Frameworks by Ovid
in thread Tiny Frameworks by Ovid

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.