Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

About the Personal Nodelet

by SiteDocClan
on Dec 15, 2006 at 19:42 UTC ( #590101=sitefaqlet: print w/replies, xml ) Need Help??

The Personal Nodelet provides a place to store small snippets of HTML (including PerlMonks-specific markup). (Currently, each snippet is limited to a length of 1024 characters.) Each time you fetch a page from PerlMonks, these snippets of html are rendered in your Personal Nodelet (assuming you've enabled it in your Nodelet Settings). A line break (<br>) is inserted between each one.

General management of the your Personal Nodelet contents is provided by your Personal Nodelet Settings. On that page, the raw html of each item is shown (and editable) in the text fields on the right, and the way PerlMonks will render each one is shown in the middle.

Although it is of more general usefulness now, the original idea of this nodelet was as a mini bookmark list and "link collector"; and its current design shows that heritage. Notice these several links at the bottom of the nodelet:
                                             
Edit | Add current node
Add to public / private pad
If, while viewing any node, you click the Add link, a link to that node will be added to the end of your Personal Nodelet list. Click Edit to jump directly to your Personal Nodelet Settings page.

The other two links add a link to the node currently being viewed to your public or private scratchpad, in case you like the idea of using those places as bookmark collectors.

Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
[haukex]: I think you're right, I think Pod::Simple is the preferred parser now
[haukex]: But I was just using it as an author test anyway
[Corion]: haukex: Aaah - I thought you were still running these tests on every machine, but you only run these as author or Devel::Cover tests
[Corion]: haukex: Yeah, I think back then I used Test::Inline, which used a pod parser that was going through some changes and I didn't want to cater for all the various versions and thus stopped testing the Pod completely
[choroba]: I usually do this with presentations
[Corion]: But now I think statically (re)generating the Pod tests is a saner approach, and likely I'll regenerate the tests either in Makefile.PL or from xt/ but have them live below t/
[choroba]: I keep the snippets in files of their own, and use a Makefile to syntax highlight them and insert them into slides, while also running them and inserting the output if required
[Corion]: choroba: Ooooh - I didn't think of that! I write my presentations as POD and if it "roughly" looks like Perl code, I should also syntax-check that...
[haukex]: Yes sorry I don't run them all the time, my POD tests are only run as author tests (and are excluded when I'm using Devel::Cover)
[Corion]: choroba: Hmm - no, I keep the snippets inline, but as my framework also has support for capturing output etc., maybe I should do the same...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (6)
As of 2017-02-27 12:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Before electricity was invented, what was the Electric Eel called?






    Results (385 votes). Check out past polls.