All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Joshua Lock <josh@linux.intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"Wang, Shane" <shane.wang@intel.com>
Subject: Re: RFC: Hob 1.2 design
Date: Tue, 7 Feb 2012 11:23:28 +0000	[thread overview]
Message-ID: <CB56B9C2.7503%belen.barros.pena@intel.com> (raw)
In-Reply-To: <4F3046F3.80102@linux.intel.com>

Hi Joshua,

Additional package details appear on clicking the package name using an
information bubble. The bubble is also dismissed on click using a 'close'
button. This functionality is shown on the first video (not on the second
one: I skipped it to keep it short).

Cheers

Belen

On 06/02/2012 21:32, "Joshua Lock" <josh@linux.intel.com> wrote:

>On 31/01/12 17:39, Wang, Shane wrote:
>> Hi, all,
>>
>> Belen has a new video for Hob2 workflow and design.
>>
>> https://wiki.yoctoproject.org/wiki/File:Hob1.2-screencast2.mov
>
>It just came to my attention through another channel that the
>description column of the packages table is no longer present.
>
>There had been some discussion about how to show relevant description
>information in that column, so I'm surprised to see it go.
>
>Belen, I assume from a design perspective this field was removed as it
>didn't show anything particularly useful? If we have useful data to
>include in that field is there a more appropriate way to integrate it
>into the UI? Perhaps a tooltip? Or an information overlay as has been
>used in other areas of the design?
>
>I'm concerned that if we give the user a list of packages without any
>more information we aren't making it easy for them to build an OS image
>without already understanding exactly all of the components they need -
>thoughts?
>
>Cheers,
>Joshua
>-- 
>Joshua Lock
>         Yocto Project "Johannes factotum"
>         Intel Open Source Technology Centre

---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



  reply	other threads:[~2012-02-07 11:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  1:39 RFC: Hob 1.2 design Wang, Shane
2012-02-01  3:15 ` Stewart, David C
2012-02-02 10:36   ` Barros Pena, Belen
2012-02-01 17:28 ` RFC: " Scott Garman
2012-02-02 10:12   ` Jack Mitchell
2012-02-06 21:32 ` Joshua Lock
2012-02-07 11:23   ` Barros Pena, Belen [this message]
2012-02-07 16:17     ` Joshua Lock
2012-02-08 10:23       ` Barros Pena, Belen
     [not found] <3AB6CE7F274E534CAFD089D127A8A1FC0FCE9F5F@SHSMSX102.ccr.corp.intel.com>
     [not found] ` <CB4F0427.6A93%belen.barros.pena@intel.com>
2012-02-02 12:48   ` Wang, Shane
2012-02-02 22:29     ` Joshua Lock
2012-02-03  0:25     ` Wang, Shane
2012-02-03  0:56       ` Xu, Dongxiao
2012-02-03  5:29         ` Wang, Shane
2012-02-03 15:01           ` Barros Pena, Belen
2012-02-06 11:53           ` Barros Pena, Belen
2012-02-03  0:35     ` Xu, Dongxiao

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=CB56B9C2.7503%belen.barros.pena@intel.com \
    --to=belen.barros.pena@intel.com \
    --cc=josh@linux.intel.com \
    --cc=shane.wang@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.