tighten it up... a couple suggestions...

[Guest]

i suggest we lose the author, views and replies columns.

widen up the column with the topic title so it doesn't wrap (unless it's really long).

and replace the word "(updated)" to indicate an updated thread with the little red flags we all know and love.

if the system is smart enough to dynamically insert the character string "(updated)" it's smart enough to post the character string "<img src="lilredflag.gif">"

maybe tweak the new vs visited vs updated link colors a bit so there's more differentiation. rather than light blue, little less lighter blue, and bolder light blue.

... 😉

dave

[Michael D Sullivan]

Or at least put the (updated) in (BIG BOLD RED) instead of (tiny light blue).

[Guest]

Michael D Sullivan wrote:

Or at least put the (updated) in (BIG BOLD RED) instead of (tiny light blue).

... and not tight up against the link to the poster's profile.

I don't want to see most of them once, let alone every time my trembling cursor strays over that damned link

[D__McCahill]

Michael D Sullivan wrote:

Or at least put the (updated) in (BIG BOLD RED) instead of (tiny light blue).

Or we could use a little red flag ... oh, wait ... nevermind.

[Guest]

bump!

[Eric16]

Stylish fix is in. #f00 was just too red for me, so I took it down to #600.

See Adobe Jive Forums: Red (Updated) to install.

[Ramón_G_Castañeda]

Thank you, Eric.  This is a HUGE help!

More reason for the Jive folks to hang their head in abject shame.

[Eric16]

No problem!

Because these fixes only work in FireFox, I only have to target one browser, which means I never hit the myriad compatibility issues *cough*Explorer*cough* that they have to test for. Which means I can release a fix in minutes or days instead of days or weeks. (Which is to say, I bet it's not entirely their fault they can't respond as quickly as they might like.)

[Ramón_G_Castañeda]

Eric @ MCA wrote:

No problem!

Because these fixes only work in FireFox, I only have to target one browser, which means I never hit the myriad compatibility issues *cough*Explorer*cough* that they have to test for. Which means I can release a fix in minutes or days instead of days or weeks. (Which is to say, I bet it's not entirely their fault they can't respond as quickly as they might like.)

Any chance you might be able to adapt something like dave milbut's afplonk script for use here?  That would be phenomenal.

  http://www.milbut.org/afPlonk.html