From: Darren Hart <dvhart@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Hob implementation: vanilla or branded?
Date: Thu, 31 May 2012 11:08:35 -0700 [thread overview]
Message-ID: <4FC7B3A3.4030706@linux.intel.com> (raw)
In-Reply-To: <CBED6054.10464%belen.barros.pena@intel.com>
On 05/31/2012 09:55 AM, Barros Pena, Belen wrote:
> Hi all,
>
> As part of the Hob work for the 1.3 release it looks like we need to make
> a visual design and implementation decision: do we want a 'vanilla' or a
> 'branded' look for Hob? Sorry if the choice of words is not the best.
> Neither 'vanilla' nor 'branded' are meant in any negative way.
>
> We did have this conversation when we started work on the 1.2 release of
> Hob, but somehow we settled for a middle way that is not working well and
> is causing issues like bug 1701. From my conversations with UI engineers
> and people with lots of experience in building applications using the GTK
> toolkit, the middle way just doesn't work.
>
> What I mean by 'vanilla' is an implementation that takes the visual
> appearance from the theme installed in the Hob host. The main advantage of
> vanilla implementations is they guarantee that Hob will play nicely with
> its host computer.
This would be very much preferred in my opinion. Having applications
that ignore the preferences I have set for theme, colors, fonts, etc. is
very annoying. Applications that ignore the GNOME HIG are even more
irritating as the button layout and general workflow is enough different
from the rest of the applications in my desktop that they become awkward
to use and break the continuity of the desktop experience.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-05-31 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CBED5FA2.10462%belen.barros.pena@intel.com>
2012-05-31 16:55 ` Hob implementation: vanilla or branded? Barros Pena, Belen
2012-05-31 17:08 ` Tomas Frydrych
2012-05-31 17:55 ` Jack Mitchell
2012-05-31 18:08 ` Darren Hart [this message]
2012-05-31 18:58 ` McClintock Matthew-B29882
2012-05-31 19:01 ` Burton, Ross
2012-06-08 14:28 ` Barros Pena, Belen
2012-06-08 14:40 ` Darren Hart
2012-06-08 16:41 ` Joshua Lock
2012-06-08 20:24 ` Burton, Ross
2012-06-08 20:26 ` Joshua Lock
2012-06-08 20:31 ` Burton, Ross
2012-06-08 20:42 ` Stewart, David C
2012-06-08 20:56 ` Burton, Ross
2012-06-11 9:31 ` Barros Pena, Belen
2012-06-11 9:30 ` 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=4FC7B3A3.4030706@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=belen.barros.pena@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.