Or just add on an extra class (e.g. class="reply new") and augment rather than replace the existing ones. That way you don't screw over someone with existing styling by making the underlying class "disappear".

We already have this in a way. It marks nodes that are on newest nodes. Here is my CSS

      .reply    { background-color: rgb(180, 180, 255); }
      .reply-new { background-color: rgb(255, 180, 180); }
[download]

When viewing a node, replies that are on your newest nodes will be marked with .reply-new.

Update: After rereading i thin this is exactly what you where asking for.

It is! You've just made my day :-)


holli, /regexed monk/

Perhaps you should have done more research before posting then, and will now donate your XP to a good cause.

This feature was written by eric256 and applied back in 2004-09-09. So it can pay to look first, even if you didn't think the feature existed.

- tye        

Wholy molly, three years ago? I fear i'm the only one who's used it for those three years!! ;) Oh well I enjoy it.


___________
Eric Hodges

Monktastic!!! Thanks eric256. Have a very belated++

++ holli.  Just yesterday I had the same thought when reading what would you like to see in perl5.12?... IOW, being able to highlight nodes that are new since last visiting the thread would definitely be a great feature!

new since last visiting the thread

Note that that wasn't what was proposed. It is also not likely to ever be implemented. Tracking "time of last visit" for every thread for every user is too much overhead. The proposed feature would trigger only based on the "I've checked all of these" buttons found in Newest Nodes and Recently Active Threads.

- tye        

Although.... we could cheat.

My typical usage of the site is to find the new posts on Recently Active Threads and then click through to them (or their parents).

We could do the same as Holli suggested for RAT/NN and, if the user has a "time of last visit" set, add a class to the posts on that page that are newer.

It clearly wouldn't work for older threads found on (eg) Seekers of Perl Wisdom, but it wouldn't hurt either. For common usage, it would be fine. And cheap.

Clint

Ah... thanks for clearing this up, tye. Obviously, my reading of holli's suggestion was strongly influenced by what I would like to see implemented... :) Sorry for the confusion.

Anyhow, any improvement along these lines would be greatly welcome, as what I currently typically do to handle such high-traffic threads is to click on the (assumably new) "Re^N:"-subthreads in Recently Active Threads, and then - because I need some more context - click on the parent node link once or twice. Presuming I'm not the only one doing it this way, this is not only cumbersome to handle, but also creates a lot of unnecessary requests to the server. — But of course, I respect the decisions of whoever would have the trouble implementing the changes.

Tracking time of last visit on the server side would be hefty, but as I say below if there were a thread last updated item hidden in the HTML javascript could be used to handle this in a cookie on the browser side. Even if just using greasemonkey.

                - Ant
                - Some of my best work - (1 2 3)

Actually... if on pages like newest nodes the html held the last updated thread time then it would be easy to either have javascript on the PM or use GreaseMonkey to store the last time you visited a node... then highlight those that have been updated since you last visit. Should be almost no extra work on the server side. Would be a nice option.

                - Ant
                - Some of my best work - (1 2 3)

That's what I was thinking. Every time you visit a node, couldn't you store the nodes below it locally and if you revisit a node base your CSS on your own data of read nodes? Seems like something that could be hacked together using GreaseMonkey or a Firefox extention.

---

Revolution. Today, 3 O'Clock. Meet behind the monkey bars.

I would love to change the world, but they won't give me the source code

Read before you speak ;-)


holli, /regexed monk/

Read before you speak ;-)

Sorry Holli, but could you please explain what you mean by this?

Maybe Gavin understands (or not), but as one of the gallery following along, I do not see any context in this thread that explains what he should have read before speaking?

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

RAT emphasizes posts younger than one hour with bold. Is that the sort of thing you're thinking of? If so, perhaps something similar could be done in NN.

No.
What I am thinking of is to make it possible to "visually emphasize" those nodes that are listed in Recent Threads or Newest Nodes when you look at/read a thread.


holli, /regexed monk/

I am thinking that we could inherit the age indication CSS classes, for each node, from Recently Active Threads. The user could then decide for himself exactly how he wants it to look.

So far your only choices are to open the OP, read over the replies and mentally parse "did I already read that?", or to open the new nodes one after another.

Since I no longer use "I've checked all of these", it'd be nice to have a user setting for how recent is considered "fresh"¹ when your "last checked" timestamp is unset. But trying to pick the default for such a setting I vacillate between "1 hour" and "12 hours", then think something more complex is called for, and finally come back to just a simple "1 hour" default for a simple user setting.

¹ which is the name I'd give to the style that would be applied to notes that are "new enough"

I'd have the user setting be measured in hours but allow decimal values such as 0.1. No, FYI, I'm not writing any of this. If there ends up being a user setting, then there should also be some default CSS. But maybe none of that should be in the first version implmented.

Couldn't we have twenty different classes for the twenty age categories in RAT? Then, anyone could decide what they'd like to highlight in their user CSS.