unity-design team mailing list archive

["frederik.nnaji@xxxxxxxxx" <frederik.nnaji@xxxxxxxxx>]

in other words, we close windows more often than we identify them by
their title-bar-text, since most windows we close are in the front,
top-of-z-stack, and we already know what we're about to close.
so all we care about is finally hittilng that button via Fitt's worst law.

aim, shoot. No "read". LTR is perhaps until today the explanation for
why an object will first print "title" and only then close or cancel
button, but indeed we started sorting items after frequency of use,
selected items after relevance to the supposed workflow and suppressed
items that overloaded information on the UI.

i'd say i'd rather do away with the titles in tab-titlebars altogher,
before letting them break a newly won overall consistent logic

On 2011-02-01, frederik.nnaji@xxxxxxxxx <frederik.nnaji@xxxxxxxxx> wrote:
> but action speaks louder than words, and a document who'se identity
> predominantly defines the content of the screen, needs not be
> identified by reading the titlebar text. looking at the screen alone
> suffices to know, what window i'm closing.
>
> To show the document title is orthogonal to the interaction syntax of
> hitting the window-close control of a document which is in the front.
>
> since that is the case, left-close is our spacial memory already:
> because all windows have this control on the top-left (even window
> previews in the future).
>
>
> On 2011-02-01, Remco <remco47@xxxxxxxxx> wrote:
>> On Tue, Feb 1, 2011 at 12:51, Matthew Paul Thomas <mpt@xxxxxxxxxxxxx>
>> wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Paul Sladen wrote on 27/01/11 12:24:
>>>>
>>>> On Thu, 27 Jan 2011, Matthew Paul Thomas wrote:
>>>>>
>>>>> Chromium and Chrome have close buttons on the right of their tabs
>>>>> because it's faster to use than having them on the left.
>>>>> <http://www.theinvisibl.com/2009/12/08/chrometabs/>
>>>>
>>>> I fear that the "open in middle" tab behaviour rather killed that
>>>> advantage.  You now (Firefox default) have to hunt for the tab to
>>>> close, rather than the most recent tab being at the end.  :)
>>>>...
>>>
>>> On the contrary, it means that tabs relating to the same task are
>>> grouped together (because they were opened from the same parent tab), so
>>> they can be closed together when you are done.
>>>
>>> Meanwhile, Firefox is adopting the same fast-tab-closing scheme, which
>>> means Firefox's close buttons will stay on the right too.
>>> <http://frankyan.wordpress.com/2010/07/30/making-tab-closing-easy/>
>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=465086#c183>
>>
>> There is no causal relation between buttons on the right and the fast
>> closing scheme. As the blog post acknowledges, everything could be
>> mirrored, and it would still work. The justification for buttons on
>> the right is that LTR languages read from left to right. The same
>> could be said for window closing buttons, so why not put those on the
>> right, too?
>>
>> --
>> Remco
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~ayatana
>> Post to     : ayatana@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~ayatana
>> More help   : https://help.launchpad.net/ListHelp
>>
>