Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

BUU writes:

I will note in passing that there are lots of modules that have a proper name in the title, but mostly these are named after systems of some sort, most notably POE has it's own namespace.

POE components tend to have "POE" in their names because they don't live separate lives from that framework. The implication is "You need POE to use this." In that vein, BUU::IRC implies that some BUU module is necessary to use it.

On the other hand, modules based on POE aren't required to be in POE's namespace. People just feel strongly enough about the association to insist on putting them there. So strongly in fact that the POE::Component namespace was set aside to let them without conflicting with the framework itself. From POE::Component's documentation:

The POE::Component namespace was started as place for contributors to publish their POE-based modules without requiring coordination with the main POE distribution.

Term::Visual is a notable exception. It provides a three- or four-section terminal interface (title line, scrolling terminal region, status bar, input line). To come full-circle, I think japhy has written an actual IRC client using it and POE::Component::IRC.

-- Rocco Caputo - http://poe.perl.org/


In reply to Re: "Vanity Tagging" on CPAN? by rcaputo
in thread "Vanity Tagging" on CPAN? by BUU

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others admiring the Monastery: (2)
As of 2024-04-20 01:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found