Re: [Usability] Modified Documents

[Kirk Bridger <kbridger shaw ca>]

I'm not convinced that all symbols have to be cryptic.  If implemented
(i.e. chosen) carefully, a simple symbol (or icon) can nicely point out
to the user that the document is read-only.  The emblems in
Gnome/Nautilus work similarly, and frankly I think they work well.  It
also maintains the consistency of the interface, to use the same icons
as the file manager (if that's what we're calling it).

What other states/info would we want to portray for the document?  It
seems we're only talking about read-only status.  Is there anything else
we should include?

Kirk
  



On Thu, 2004-09-16 at 16:39, Iain * wrote:
> > It was a guideline that was only introduced in the 2.0 version of the
> > guide, and unfortunately we haven't yet done a very good job of
> > highlighting to developers the key changes/additions that they should be
> > aware of (Seth told me he'd written such a document, but I didn't see it
> > published anywhere).  This is certainly something we need to do better.
> 
> Marlin puts "(modified)"after the file name because really what does * mean?
> 
> (Actually, Marlin will put (modified) and/or (read-only) after the
> filename depending on the circumstances)
> 
> I think cryptic symbols should be consigned to yester-year or else I
> want ⑃ to be the symbol for Read only...
> 
> iain
> _______________________________________________
> Usability mailing list
> Usability gnome org
> http://mail.gnome.org/mailman/listinfo/usability