All the talk ive heard is to put identical data in multiple nodeletss. My preference is to remove said data from both nodelets and put it in its own place. I dont think a slim nodelet with this data is a bad idea. Especially if it reduces the complexity of other nodes. Consider that corion posted the base link text patch only to one of the nodelets, wheras it would be useful for both. But there isnt much call for non developers/gods from having both enabled at the same time. Thus we have at minimum a serious target for refactoring.

As for type, i believe this could be easily triggered by such things as membership in SDC or PMDev (both which have good reason to know the type of a node). But to be honest i dont think its a bad thing to expose the common user to this information. After all we are a learning site, and learning about PM represents some form of education. Even if in the worse case its a lesson in how not to do things. (Something I obviously dont believe, but im taking the worst case perspective here.)


---
demerphq

    First they ignore you, then they laugh at you, then they fight you, then you win.
    -- Gandhi

In reply to Re^3: node info in title bar by demerphq
in thread node info in title bar by ysth

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!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            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.