in reply to color crazyness and CSS

If you have requests for changes to the site to support some aspect that you can't control via CSS right now make them in reply to this node here

As mentioned before in the Recently Active Threads announcement: a new div tag arround the top section would be cool, and special span's and class names for the various codes would help make the page extremely configurable.

Replies are listed 'Best First'.
Re^2: color crazyness and CSS
by demerphq (Chancellor) on Oct 25, 2004 at 08:12 UTC

    Ok, this was actually mostly done when you posted this, you didn't check silly hacker :-) Anyway, I added the top and bottom sections today and heres a list of what you can use:

    Im open to specific requests to change or enhance things if people can provide that. For instance I'm hoping that what I've done for the codes meets your requirements.


    ---
    demerphq

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

      Flux8


      this was actually mostly done when you posted this, you didn't check silly hacker

      I checked, i just didn't check very closely. :)

      nodethreads-head and nodethreads-foot are extremely appreciated. The classes you've added are also very cool for tweaking the way the individual elements look (I've started using a few, but i'm sure i'll find ways to use/tweak the others over time), but there was one part of my initial suggestion that I think you missed (and looking at it now, would probably be the most usefull)...

      It would also be handy if the information about your vote, front paged, and approved was used in making class names for a span tag arround the whole line -- so that people can highlight nodes that have cetain properties.

      For example, someone might want all nodes that they have down voted to be striken, all nodes that have been front paged to be in a bigger font size, all nodes that are not approved to be blinking, the number of descendents of each node in italics, and the number of nodes in the selected set to be shown in plain font (instead of bloded as it is now)

      For example, given the list of classes that exist the individual pieces of data, imagine a corrisponding version of (most of) them that includes "-line-" for use on the whole "p" of the line (I orriginally thought it would make sense on the "li", but you don't want it to apply to the subtree)...
      <!-- suppose this node is unapproved, and i downvoted it --> <li id='li999999' class='nnt-depth-1 nnt-auth-123291'> <p class='nnt-p-title nnt-p nnt-line-unapproved nnt-line-minusminus' align='left'> ... <!-- all of the existing stuff per node --> ... </p> ... <!-- the subtree of the node (if any) --> ... </li> <!-- suppose this node is frontpaged, and i upvoted it --> <li id='li888' class='nnt-depth-1 nnt-auth-123291'> <p class='nnt-p-title nnt-p nnt-line-approved nnt-line-fplink nnt-line-plusplus' align='left'> ... <!-- all of the existing stuff per node --> </p> <!-- the subtree of the node (if any) --> </li>

      And then people can setup CSS like this...

      .nnt-noderep { font-style: normal; font-weight: bold; color: red; } .nnt-line-minusminus { text-decoration: line-through; } .nnt-line-unapproved { text-decoration: blink; } .nnt-line-fplink { font-size: larger; }

        See what you think now. For some reason the extra div has altered the whitespace behaviour of root nodes (at least on IE). I haven't worked out why yet. Anway,im not sure if I hate it or not so it might change a bit, but I think it is pretty much what you had in mind no?