I'd have to take argument to your model. I would strongly recommend an Apache-style model: the configuration file. This gives the user the benefit of not only being able to centrally view all of the plugins but it allows for the plugins to be wherever the user wants them to be (directory cleanliness). In your current model, to disable a plugin, it is removed from the directory. I'd consider that an unecessary hassle. In the conf file, all you would need to do is comment and uncomment some line.

How about plugin options? These can be easily specified in the configuration file. Your model doesn't provide for this unless you ask the user to hack the plugins directly.

I find it much more comforting if I know exactly which modules and libraries are loaded by a program rather than specifying some arbitrary directory. A central configuration file gives me the control of the program that I need. And remember, the configuration file can be used for more than juts plugin specs! Good luck!

AgentM Systems nor Nasca Enterprises nor Bone::Easy nor Macperl is responsible for the comments made by AgentM. Remember, you can build any logical system with NOR.

In reply to Re: architecture for module API by AgentM
in thread architecture for module API by dash2

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.