Introduce icons for status reporting of users/posts/comments

I am sorry to say, but this is not very good (well done, but not effective...). For me, "Published" and "Active" is not equal to "checkmark". I see checkmark. What does it mean? Same with "Not published" and "Blocked". The red X will make users panic. What is wrong with this thing? Why this red X on my screen?

I have to admit that I am with kobus in this. I really think teh work you did is very nice. But I think replacing information with icons is a bad thing. Icons can be used next to that information, o enhance it, not replace it.

Bèr

i like this sort of candy. if user hates images, he shuts them off and sees the alt text. no problem. also, less of a translation burden.

I like these too (if done right).

What about moving these into the admin thelme occy is worknig on? There is load of niftyness in there, that could be considered to be ported to core.

Do these follow the guidelines for Use of icons? :)

Instead of using x/checkmark, how about using an icon of a page.. and for published overlay a globe on it, and for unpublished overlay the red circle with a slash through it?

Lullabot made some icons, http://www.lullabot.com/articles/free_gpl_icons_lullacons_pack_1. I'd like to see the icons in that style.

I'm not sure how much published/not published and active/blocked maps to check/x.

Personally, I think the overall goal is to make the tables smaller and less intimidating for fitting into page layouts and making them more usable. There are currently two options for each status, and one of them is usually much more common than the other. My idea was to remove the whole status icon and add '(not published)' after those posts and '(blocked)' after those users.

moving from x.y.z to 6.x-dev version queue

Although I don't know the difference between a task and feature request, this appears to be a feature request to me. But there may be a fine line that I'm missing about the difference between the two.

Looking at the last patch being submitted over a year ago, it's almost safe to say that it needs to be ported to be compliant with a newer version.

I incorrectly used the new "patch (to be ported)" status.

tasks are usually:
1. feature requests with patches attached ;)
2. usability fixes that aren't strictly bugs.

This patch is very old now, worth revisiting for D6?

Too late to revisit this... moving to D7.

tagging