All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wood <michael.g.wood@intel.com>
To: toaster@yoctoproject.org
Subject: Re: [RFC] Toaster UI visual identity
Date: Tue, 21 Jul 2015 11:29:03 +0100	[thread overview]
Message-ID: <55AE1EEF.6090001@intel.com> (raw)
In-Reply-To: <D1C2C089.509F%vitor.levi.da.silveira@intel.com>

Hi Levi,

The icons for "edit" field that you can see here 
https://wiki.yoctoproject.org/wiki/images/0/03/2.2.BitBake_Variables.jpg 
don't quite seem obvious as to what they do to me.

In

https://wiki.yoctoproject.org/wiki/images/9/91/1.1.Build_Dashboard.jpg
https://wiki.yoctoproject.org/wiki/images/d/d9/1.1.1.2.Directory_Structure.jpg

We have the left navigation appearing as a white block and kind of 
cutting into the secondary navigation area. Personally I find this a bit 
jarring, I wonder if it would be better to have the top bar full width 
as you have in
https://wiki.yoctoproject.org/wiki/images/9/9b/1.0.Project_Builds.jpg ?

Otherwise everything else is looking really good. Thanks for your work 
on this.

Michael

On 08/07/15 15:56, Levi Da Silveira, Vitor wrote:
> Hello all,
>
> As I mentioned on last weekly I was compiling all the screens and components I’ve designed until now for Toaster tool.
> I’m designing some components and documenting yet. However, you can see template screens and many components already on this link: https://wiki.yoctoproject.org/wiki/Toaster_1.9_design#Visual_Design
>
> It’s very important to get your comments and feedback at this point once through it I could achieve the best visual to regard the functionalities.
>
> Cheers,
> Victor Levi



  reply	other threads:[~2015-07-21 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 14:56 [RFC] Toaster UI visual identity Levi Da Silveira, Vitor
2015-07-21 10:29 ` Michael Wood [this message]
2015-07-22 14:01   ` Levi Da Silveira, Vitor

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=55AE1EEF.6090001@intel.com \
    --to=michael.g.wood@intel.com \
    --cc=toaster@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.