++ hacker for making an excellent point.
My suggestions:
- Associate keywords with the modules.
- Voting mechanism for module by perlmonks.
- Search CPAN with google like mechanism for keywords.
- Apply the sort orders. (Latest, Depend on, VoteRank, RefereceRank)
Notes:
Keywords will provide a very good search mechanism. Voting is not absolutely necessary. Sorting would keep latest/useful/obscure module within reach. It will also take care for the definition of better module for a given task as the time passes.
New Section - "I use this new module for":
We say that 90% code is written in terms of modules. May be we should establish a formal mechanism to introduce useful modules here. Perlmonk can say that I use such and such modules for this purpose(s) which will require lot less effort than module review section, but would be immediately helpful to us. Practical examples would serve an added value for modules to the documentation, tutorials and reviews.
artist
-
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.
|
