[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Ayatana] Design problem: Menus hidden by default in Unity
- To: Conscious User <conscioususer@xxxxxxx>
- Subject: Re: [Ayatana] Design problem: Menus hidden by default in Unity
- From: Remco <remco47@xxxxxxxxx>
- Date: Thu, 17 Mar 2011 17:45:01 +0100
- Cc: ayatana <ayatana@xxxxxxxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=m9UWvZjmdaBirfO/wgESGzBXMpsLGSuNCwkl4eZ+g5I=; b=k1MrmEPzOXdjD1KRCzajqv7+68O5aboYvnr44zO8VTpx9CIz0InYQ/remngt2uXvQy D6RjiY6/iSnlTg+81DkVmOywH0NAxm4mCEV4DKBSjwS3xWavjt9qt1bbfy3xqhKkBNUR LFkVOXRtEykXQUU4SIaldD10yeeAWOhJs2ekc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=fASJMrkOfCUFafZqdx3bh5N/IMjd8eqaPJg/LpcUahFxd9M4oOqeFHlQjTT3k7ZU/C aDBvmmazg9S0YHTOgAd22Yhc/vcOlXJ3U8/gxRMCNd5TCJW9dzqC/x6zV8xOhRqxHyDn aTNi7JNjV8lJPjGf6LWLHy7trc8FaH1kIIxeg=
- In-reply-to: <1300378492.15278.44.camel@laptop>
- List-archive: <http://lists.launchpad.net/ayatana>
- List-help: <https://help.launchpad.net/ListHelp>
- List-id: <ayatana.lists.launchpad.net>
- List-owner: <https://launchpad.net/~ayatana>
- List-post: <mailto:ayatana@lists.launchpad.net>
- List-subscribe: <https://launchpad.net/~ayatana>
- List-unsubscribe: <https://launchpad.net/~ayatana>
- References: <1300378492.15278.44.camel@laptop>
On Thu, Mar 17, 2011 at 17:14, Conscious User <conscioususer@xxxxxxx> wrote:
> My personal suggestion would be dropping the title in the panel as
> mpt suggested, but keeping the idea of merging the titlebar and the
> panel. This means dropping the title entirely in the maximized
> case, yes. I don't think anyone would really care.
>
> For fixing the gap, I'm going to suggest something controversial,
> but that I wanted to suggest for a long time anyway: dropping the
> minimize and maximize buttons, following Gnome3's direction and
> under their same arguments.
>
> This would leave only the space of a single close button to worry
> about and this could be addressed by something with a fixed size
> that does not need to be truncated: AN ICON.
Awesome. Just awesome. This fixes everything, doesn't it?
> Matter of fact, I WOULD suggest placing this icon even when the
> window is maximized and storing a menu with window management
> options in it, just like you already have depending on your
> metacity settings. Close *is* a destructive function you
> don't want near "File", after all... But I won't seriously
> support this second suggestion for the moment, because I
> suspect that would make closefests of maxmized windows too
> inneficient, and this is bad for netbook users.
>
> Thoughts?
I do see a problem with that last one: how is a user going to figure
out how to close the window? An (X) button has familiar meaning, but
an application specific icon is probably not the first place a user
would look. Also, now your icon menu and File menu are located next to
each other and have the same item at the end: Close.
--
Remco