public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chris Rivera" <chrismrivera@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Add an ellipsis to the preferences menu item
Date: Thu, 25 Oct 2007 19:22:23 -0400	[thread overview]
Message-ID: <5f84803c0710251622g64559cai7e09e657f9c78665@mail.gmail.com> (raw)
In-Reply-To: <1193352257.6184.282.camel@violet>


[-- Attachment #1.1: Type: text/plain, Size: 1172 bytes --]

Agreed.  We need to follow the HIG.  According to:

http://developer.gnome.org/projects/gup/hig/hig-diff/menus-design.html

the ellipsis should be in place only if it _requires_ further input from the
user.  I guess the ellipsis isn't necessary.

Chris

On 10/25/07, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Chris,
>
> > Since the Preferences menu entry in the applet opens a new window it
> > should probably have an ellipsis in the label.  Attached is a trivial
> > patch to add this.
>
> what does the HIG recommend for applet menus. I wanna follow the HIG.
> Currently I simply did what all other applets do that I have running.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #1.2: Type: text/html, Size: 1800 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-10-25 23:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 19:20 [Bluez-devel] [PATCH] Add an ellipsis to the preferences menu item Chris Rivera
2007-10-25 22:44 ` Marcel Holtmann
2007-10-25 23:22   ` Chris Rivera [this message]
2007-10-26  0:29   ` Bastien Nocera
2007-10-31 16:33     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f84803c0710251622g64559cai7e09e657f9c78665@mail.gmail.com \
    --to=chrismrivera@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox