Besides, do we really want hundreds of different Javascript and/or CSS tweaks floating around in free nodelets? [And if we do then maybe another nodelet should be created for these.] That would certainly make it harder for the pmdevs to test against.

And if someone tweaks e.g. ikegami's code (to make it work with IE) then how do we make sure everyone updates their copy in their respective free nodelet? We might as well have a display tweaks repository and let people check off on the ones they want. Which of course in effect makes them setting changes anyway.

I'm inclined to say if it's something several people will potentially use then it should be added in (assuming it doesn't require a massive rewrite). And in this case, maybe nodelets on the left should even be the default for anoynmmous monks since then they too would benefit from a reduction in code wrapping issues.

Anyway, thanks for listening to me rambling on.

Update: I think all of the browser compatiblity issues and how we still do not have a good IE solution underscores why this would be better implemented as a setting (where modifying the DOM would not be necessary).

Update2: Or perhaps patience is in order as we do have a working code snippet now! :-)


In reply to Re^6: Nodelets on the left? by Argel
in thread Nodelets on the left? by Argel

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.