comment on

Top down:

XP Nodelet ~ i'm a whore after all

Approval Nodelet ~ I am level 6+, and I do my best to help clean up the monastery

Tick Tock Nodelet ~ it's good to know what the time is

PmDev Nodelet ~ I'm a pmdev member, and I need the perks

Chatterbox ~ constant communication

Other Users ~ it's practically tied to the Chatterbox's hip

Keyword Nodelet ~ i'm adding *meaningful* keywords, in hopes, that eventually ( and i've got a magical hunch ), it will lead to better search results.

The cpan nodelet i don't have cause I'm a cpantester, and I get plenty of email ;)

The everydevel nodelet I don't have because I'm a god on javajunkies, and I visit everydevel quite often (i'm not clueless)

The personal nodelet I gave up a long time ago, ever since I added the custom node title's (tastier to manage for me)

A few other nodelets just link to stuff I know exists, and I know my way around the monastery.

______crazyinsomniac_____________________________
Of all the things I've lost, I miss my mind the most.
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

In reply to Re: Nodelet types, uses, and (relative) usefulness by crazyinsomniac
in thread Nodelet types, uses, and (relative) usefulness by atcroft

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.


Don't ask to ask, just ask
	PerlMonks