Just my 2 cents but I agree mostly with Katrinska's usability assessments except for this one. I feel like the current distinction between view-modes is exactly what it needs to be. Any other type of visual distinction added such as borders could affect certain themes. Such as someone could create a theme so that when a guest views it the look is totally different from when a user or admin views it. It would be a misrepresentation of the guest view if other UI elements were added for the disctinction. Again, just my 2 cents. Thanks for your hard work.
--Shocksll 07:52, 19 April 2006 (PDT)
I also thought about this a long time. But there is also the possibility to change the view of the admin to get a better visual feedback, like a red border or heading, when your in admin mode. Then the concept of the guest view mode would not be broken. The guideline is carefully worded, so that for themes where a hint in the guest view mode would not be disturbing, could also be possible. But also putting the view-mode-links on a more prominent position would even be a better visual feedback. Do you better agree with this? Perhaps I should give a hint that there is this danger to disturb the guest-view mode benefit with too much changing the theme-layout.
--Katrinska 16:19, 20. April 2006
Yea, I kind of see what you are saying. So if for instance where it says
display mode: userid | Guest
there would be a red background on that or colored border around that particular box better differentating the two views. I guess the only problem I have with that is it's another thing to change in the css of the theme or colorpack. I can see someone that creates a colorpack putting in the wrong color for this then there wasn't any distinction between the two views, and then users are confused when switching that it doesn't show the extra distinction they are used to with the old colorpack, etc. I guess I just feel like it could cause more confusion than better distiction between modes. But the G2 dev's are awesome and i'm sure they can come up with a slick solution. Thanks for hearing me out.
--Shocksll 08:52, 20 April 2006 (PDT)
as I do understand you are talking about two different use cases and reasons of confusion:
So we have to trade off, which confusion state is worse for the user, and then try to change this. In my opinion it would be better to change the interface for that case, which occurs more often. I would guess it is the first one. What do you think? Or did I get you wrong?
--Katrinska 17:47, 8. May 2006
You got me correctly. I guess for me it boils down to two things.
It's not a big deal, I originally just wanted to speak my piece about it. I guess I feel like your other suggestions are very good and out of all of them this is probably the lowest priority in my mind. But I'm not against the change if it will benefit other people, I just don't think it needs to be changed. Thanks for hearing me out.
--Shocksll 11:14, 8 May 2006 (PDT)
