Posts Unread|Read|All Unread | Site Feedback

mVPstar
I'm white because I smelt an onion.

Instead of showing 3 different statuses, can you only show an icon if a thread has new posts?
No icon to distinguish all read, from partially read, and no icon for read.

I noticed it made it easier to check for new threads when the post read icon hadn't loaded immediately.

TommyCarlier
Trust me, I'm from the Internets

Doesn't the boldness of the title indicate whether a thread has new posts?

Bas
It finds lightbulbs.

In reply to TommyCarlier

#Oct 6th @ 11:20 PM

It does. Except when that new post is your own, in which case it stays bold. Which, along with the fact that your new post doesn't show up unless you refresh the page, are the two most annoying bugs on this forum, for me.

Oh wait, the "Read page 2, reply, have to login, logged in, returned to page one, click next page, lol, you're logged out again" bug is pretty bad too.

mVPstar
I'm white because I smelt an onion.

In reply to TommyCarlier

#Oct 6th @ 11:20 PM

Icon vs no icon is easier to make out than normal text -> bold text.

HumanCompiler
Compiling humans...and code

In reply to mVPstar

#Oct 7th @ 10:36 AM

The model we looked to for read/unread was Outlook. We have a 3rd state since we're sort of different in structure from Outlook, but you'll notice Outlook doesn't make the icon go away...it just changes the icon.

mVPstar
I'm white because I smelt an onion.

In reply to HumanCompiler

#Oct 7th @ 11:41 AM

Just because Outlook uses the model doesn't make the idea any better. Smiley

HumanCompiler
Compiling humans...and code

In reply to mVPstar

#Oct 8th @ 1:16 PM

Maybe not, but if it's something lots of people will recognize it tends to be easier to pick up on. It definitely doesn't make it worse to follow the pattern of a commonly used piece of software.

mVPstar
I'm white because I smelt an onion.

In reply to HumanCompiler

#Oct 9th @ 9:40 AM

Yeah, but C9 does introduce a lot of changes that are unconventional in forum world. I can understand keeping some elements of the site familiar, but will elements such as these change for the better in the future?

HumanCompiler
Compiling humans...and code

In reply to mVPstar

#Oct 12th @ 3:04 PM

You've given me no details to answer your question. It's like you instantiated a new Question<T> but didn't include T. Tongue Out

What things are unconventional that you're wondering about?

mVPstar
I'm white because I smelt an onion.

In reply to HumanCompiler

#Oct 13th @ 12:18 AM

T = The elements that are conventional and are kept there for the sake of familiarity, but not so much because said elements are "better", specifically the status icons this thread is about, not excluding any other elements fitting in this category,...will those see change in the future?

Unconventional = Next/last vs Jump to page #, ajax might be considered one too

Question<T> myQuestionForErik = new Question<T>(QState.Answerable);
try{
myQuestionForErik.Ask();
}
catch(UnanswerableException e)
{
myQuestionForErik.AskAgain();
e.Dispose();
}

spivonious

I'd like to show my support for this idea, if only to keep some consistency between this forum and other (vBulletin-based) forums on the web.

Turbodad

In reply to HumanCompiler

#Oct 9th @ 9:40 AM

Maybe not, but if it's something lots of people will recognize it tends to be easier to pick up on.

This is the kind of thinking that resulted in Windows Mobile being an unusable mess. You need to invent new better ways of interaction, or at least copy the best, which Outlook is not, as far as a message board is concerned.