From: Joshua Lock <josh@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "Metthey, Mikael" <mikael.metthey@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Hob 1.2 design - visuals
Date: Mon, 06 Feb 2012 13:56:54 -0800 [thread overview]
Message-ID: <4F304CA6.2010800@linux.intel.com> (raw)
In-Reply-To: <CB558AF2.739A%belen.barros.pena@intel.com>
On 06/02/12 05:54, Barros Pena, Belen wrote:
>>> 3. Inherit colour scheme from applied OS theme in host computer
>> Is it to say we use the default colors from OS, and don't specify any
>> color?
>> For example, Jessica wants progress bars to be green but in Ubuntu it
>> should be orange.
>> If so, Belen, I agree with you.
>
> Yes, I think that's what Joshua recommended, and I can see why it makes
> sense. Joshua, could you confirm when you have a chance?
Indeed, that's precisely what I'm recommending. Further, when we need to
colour a widget that isn't usually coloured in the theme (like the
red/green colouring of build items in the hobv1) we should try and use a
colour from the palette defined in the current theme to avoid issues
like #1701[1][2] and another example from the wild[3][4].
I found a reasonable resource on the how and why[5].
> If we decide to implement this way, people will need to understand that
> this applies to all UI elements without exceptions. Any particular
> requests (like Jessica's) could be looked at on a case by case basis.
But should be well justified, and generated from the host theme's palette.
Cheers,
Joshua
1. http://bugzilla.pokylinux.org/attachment.cgi?id=276
2. http://bugzilla.pokylinux.org/show_bug.cgi?id=1701
3. http://itmages.ru/image/view/52705/9663bad0
4. http://redmine.yorba.org/issues/2483
5. http://ometer.com/gtk-colors.html
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-06 21:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 16:58 Hob 1.2 design - Settings dialogue Barros Pena, Belen
2012-02-02 17:24 ` Hob 1.2 design - visuals Barros Pena, Belen
2012-02-02 21:19 ` Joshua Lock
2012-02-03 11:52 ` Barros Pena, Belen
2012-02-03 18:32 ` Joshua Lock
2012-02-06 10:29 ` Barros Pena, Belen
2012-02-06 11:42 ` Wang, Shane
2012-02-06 13:54 ` Barros Pena, Belen
2012-02-06 21:56 ` Joshua Lock [this message]
2012-02-02 21:43 ` Hob 1.2 design - Settings dialogue Saul Wold
2012-02-03 11:55 ` Barros Pena, Belen
2012-02-02 21:51 ` Joshua Lock
2012-02-02 22:01 ` Joshua Lock
2012-02-03 17:04 ` Scott Garman
2012-02-03 14:42 ` Barros Pena, Belen
2012-02-03 18:23 ` Joshua Lock
2012-02-06 10:20 ` Barros Pena, Belen
2012-02-07 14:27 ` Barros Pena, Belen
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=4F304CA6.2010800@linux.intel.com \
--to=josh@linux.intel.com \
--cc=belen.barros.pena@intel.com \
--cc=mikael.metthey@intel.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.