comment on

I'd like to suggest an update to all nodelets that contain lists. The PMDev and SiteDocClan nodelets have all their links bunched up whereas other nodlets (like Find Nodes) have one link per line. I'd like to make that adjustable on a user's style sheet.

Here's how:

All nodelets with lists become lists:

<div id=nodelet-list>
   <ul>
      <li>Nodes you wrote</li>
      <li>Super Search</li>
      ...
   </ul>
</div>
[download]

Now anyone with a default style sheet will see:

Nodes you wrote
Super Search

And, with just a little tweak to one's stylesheet like so:

#nodelet-list li {
   display:       inline;
   border-left:   1px solid black;
   padding-left:  8px;
   padding-right: 8px;
}
[download]

Our list looks like:
| Nodes you wrote | Super Search | ...
(Faked because I'm not allowed to put a style tag here)

What do people think? I've volunteering for this one too if it's something people want. It could also be possible to have different nodelets with different styles... although I'd have to play.

Cheers!
Rick
If this is a root node: Before responding, please ensure your clue bit is set.
If this is a reply: This is a discussion group, not a helpdesk ... If the discussion happens to answer a question you've asked, that's incidental.

In reply to Nodelet CSS/Format changes by BigLug

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.


go ahead... be a heretic
	PerlMonks