Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

NOTE: This node is in the early stages of development. The outline and contents will suffer significant changes as time goes by. Your input is welcome via: '/msg dvergin' or email 'dvergin at igc dot org'.

So Now You Are A PmDev...
     
Read and Explore

Procedures
      Proposing Changes
      Submitting a Patch

Concepts
      Code Chunked into Nodes
      Code vs. HTML Nodes
      Containers

Standard Subroutines, Objects, and Vars
      $query object
      $USER scalar
      $AUTHOR scalar
      $NODE href
      $VARS href
      %HTMLVARS hash
      getVars()
      htmlcode()
      [% ... %],   [{ ... }],   and   [" ... "]

Tools and Resources
      The PmDev Nodelet
      The Everything Nodelet
      pmdevil's cave map by Aristotle



So Now You Are A PmDev...
top

Read and Explore
If you have not yet done so, go to Nodelet Settings or your User Settings page and check the PmDev Nodelet item. You may also want to move it up to a convenient place near the top. This will expose two resources that can help you get an initial feel for how PmDev work gets done: the PmDev Nodelet, and the PmDev Wiki (link in the PmDev Nodelet).

Feel free to browse the various links in the PmDev Nodelet. As long as you don't hit "Submit" on any of the pages, you cannot harm anything. Take your time. Have fun.


Procedures
top

Proposing Changes
After a while, when you have gotten a sense of needs and priorities, you can

top

Submitting a Patch
Go to the page where you will be making your changes. Click on "Source code" in the PmDev Nodelet, and enter your changes in the text box provided. Each time you update that source page, your changes will appear, color-coded in the code listing at the top.

As a side effect of entering your changes, the code node in question will appear on the Patch Lister (linked in the PmDev Nodelet).

Concepts
      Code Chunked into Nodes
Not all reachable via "Source code" link.
      Code vs. HTML Nodes
      Containers

Standard Subroutines, Objects, and Vars
      $query object
      $USER scalar
      $AUTHOR scalar
      $NODE href
      $VARS href
      %HTMLVARS hash
      getVars()
      htmlcode()
      [% ... %],   [{ ... }],   and   [" ... "]
(see 'sub parseCode')

Tools and Resources
      The PmDev Nodelet
      The Everything Nodelet
      pmdevil's cave map by Aristotle


In reply to PmDev HowTo by dvergin
in thread dvergin by dvergin

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!
  • 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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

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

    How do I use this? | Other CB clients
    Other Users?
    Others avoiding work at the Monastery: (8)
    As of 2014-07-30 05:17 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      My favorite superfluous repetitious redundant duplicative phrase is:









      Results (229 votes), past polls