unity-design team mailing list archive

[Dub <dubcanada@xxxxxxxxx>]

Not really Nick, it's actually pretty standard. On Windows if you go to a
folder Blah for example in Programs. Every single doesn't have
C:/Programs/Blah/ before it. It's just "Program".

Same goes for email for example, if you go to a folder called Junk Spam not
every email begins with "Junk Spam/Email Name". And there is a ton of other
examples I can provide.

It's pretty standard to assume a single path indicates that all the sub
items (regardless of display) are part of that path.

I like it, 1+

On Mon, Feb 27, 2012 at 6:37 PM, nick rundy <nrundy@xxxxxxxxxxx> wrote:

>  I don't know that it really counts as clutter though. You have to display
> the "original" path at least once. Repeating it for other entries doesn't
> really seem to me like it clutters anything.
>
> Plus having the actual entry shift to the left margin makes it difficult
> to "scan a column" of differing entries. I have to read the original path
> to its end, then shift focus to the beginning again. Seems like some users
> might be confused by this.
>
> > Date: Mon, 27 Feb 2012 19:02:49 +0100
> > From: joerlend.schinstad@xxxxxxxxx
> > To: unity-design@xxxxxxxxxxxxxxxxxxx
> > Subject: [Unity-design] HUD: reduce clutter by removing repeated
> information
>
> >
> > Please look at this screenshot:
> http://ubuntuone.com/501RQqrOW1fh89fsIWhx4z
> >
> > When accessing deep command structures (previously known as menus :)),
> > most of the information in HUD is repeated many times. This creates
> > unnecessary clutter.
> >
> > It would be better to display the submenu as a header and then only
> > lists the menu items under that header. I'm not a great Gimp artist, so
> > I'll use text to illustrate how I think it should be, compared to what
> > you see in the screenshot. [more encodings] represents the search field
> > with input.
> >
> > Current:
> >
> > [more encodings]
> > View > Character Encodings > More Encodings > User Defined
> > View > Character Encodings > More Encodings > Unicode (UTF-16)
> > View > Character Encodings > More Encodings > Middle Eastern
> > View > Character Encodings > More Encodings > SE & SW Asian
> > View > Character Encodings > More Encodings > East Asian
> >
> >
> > My proposal:
> >
> > [more encodings]
> > View > Character Encodings > More Encodings (Non-clickable)
> > User Defined
> > Unicode (UTF-16)
> > Middle Eastern
> > SE & SW Asian
> > East Asian
> >
> >
> > Of course, this was just a quick example I found in the application I
> > was currently using. (Thunderbird) I can imagine scenarios where you
> > have much deeper hierarchies. In those cases, the actual command might
> > have to be shortened because the path is too long. But the command is
> > more important than the path leading to it. I think that needs
> > consideration as a pure usability issue.
> >
> > In any case, I think this would be cleaner than repeating the entire
> > path over and over.
> >
> > Thoughts?
> >
> > --
> > Jo-Erlend Schinstad
> >
> >
> > --
> > Mailing list: https://launchpad.net/~unity-design
> > Post to : unity-design@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~unity-design
> > More help : https://help.launchpad.net/ListHelp
>
> --
> Mailing list: https://launchpad.net/~unity-design
> Post to     : unity-design@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~unity-design
> More help   : https://help.launchpad.net/ListHelp
>
>