All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: "Lerner, David M (Wind River)" <dave.lerner@windriver.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: DRY RUN [Review Request] 4299 "recipes: View detailed information about a recipe"
Date: Mon, 13 Jan 2014 16:36:22 +0000	[thread overview]
Message-ID: <CEF9C44F.3AAC4%belen.barros.pena@intel.com> (raw)
In-Reply-To: <011977994B5AE74ABA2BD08E983BAAABA2F5DD5C@ALA-MBA.corp.ad.wrs.com>


On 13/01/2014 15:44, "Lerner, Dave" <dave.lerner@windriver.com> wrote:

>Hi Belen,
>I'm stuck on two issues.
>
>I'm still confused on the navigation, mapping of your view named diagram
>to actual mouse clicks, that you want to get fire views "Design 1.5.1
>Package Details" vs firing the views in "Design 1.1.1 Included Package
>Detail image".
>
>To get to "Design 1.5.1 Package Details" views I assume that from the All
>Builds page:
>In the Target column of the Table, click on an image
>  On the left side click on Packages
>	views per Design 1.5.1
>
>How do I get to the "Design 1.1.1 Package Details" views?

From the All builds page:

1. In the Target column of the table, click on an image
2. On the left side navigation click on a target (image) name (in the
design prototype, core-image-sato)

That will bring you to 1.1 Image information, where the selected tab is
Packages included. Select a package on the table to get to 1.1.1 Included
package details.

This file in the wiki night help:

https://wiki.yoctoproject.org/wiki/images/4/4c/Toaster_1.6_content_structur
e.pdf

It shows the Toaster structure.

Cheers

Belén


>Dave
>
>> -----Original Message-----
>> From: toaster-bounces@yoctoproject.org
>>[mailto:toaster-bounces@yoctoproject.org] On
>> Behalf Of Barros Pena, Belen
>> Sent: Monday, January 13, 2014 9:24 AM
>> To: Damian, Alexandru; Lerner, Dave
>> Cc: toaster@yoctoproject.org
>> Subject: Re: [Toaster] DRY RUN [Review Request] 4299 "recipes: View
>>detailed information
>> about a recipe"
>> 
>> On 13/01/2014 15:10, "Damian, Alexandru" <alexandru.damian@intel.com>
>> wrote:
>> 
>> >Good question, Dave
>> >
>> >
>> >For packages, we have 2 lists, in different parts of the design, that
>> >display a list of packages.
>> >
>> >
>> >- all packages build. This is currently the "bpackage" view which uses
>> >"bpackage.html"; the view/page should be renamed to
>> >"buildpackages/buildpackages.html"
>> >
>> >
>> >- packages for an image. Currently this is "tpackage", and uses
>> >"package.html". This should be renamed to
>> >"targetpackages/targetpackages.html"
>> >
>> >
>> >But we have a single package detail page, and this should be
>> >"package/package.html".
>> 
>> Actually, for packages installed, we have 2 package details pages. The
>> build package details:
>> 
>> 
>>http://www.yoctoproject.org/toaster/package-built-details-included-busybo
>>x.
>> html
>> 
>> is just a stub, a way of redirecting users to the target package details
>> page
>> 
>> http://www.yoctoproject.org/toaster/package-included-details.html
>> 
>> I decided to keep the build package details page for installed packages
>>to
>> avoid disorientation: if you were sent directly from the packages built
>> table to the packages installed details page you could lose track of
>>your
>> location within the application. Keeping the build package details page
>> seemed safer.
>> 
>> Cheers
>> 
>> Belén
>> 
>> 
>> >
>> >Hope this is not too troublesome.
>> >
>> >
>> >Alex
>> >
>> >
>> >
>> >
>> >On Mon, Jan 13, 2014 at 3:01 PM, Lerner, Dave
>> ><dave.lerner@windriver.com> wrote:
>> >
>> >Hi Alex,
>> >
>> >You wrote in a reply to David Reyna (he's David and I'll be Dave)...
>> >
>> >>
>> >> - Indeed, we use the pluralized name for pages showing an object list
>> >>(i.e. tables), and
>> >> the singular for the detail page for the a single object.
>> >>
>> >>
>> >
>> >
>> >Should we rename the exiting package.html to packages.html since
>> >package.html shows the package table for a build?  That's where I
>>picked
>> >up what I thought was the naming convention.
>> >
>> >Dave Lerner
>> >
>> >
>> >
>> >
>> >
>> >
>> >--
>> >Alex Damian
>> >Yocto Project
>> >
>> >SSG / OTC
>> >
>> >
>> 
>> _______________________________________________
>> toaster mailing list
>> toaster@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/toaster



      reply	other threads:[~2014-01-13 16:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12  6:35 DRY RUN [Review Request] 4299 "recipes: View detailed information about a recipe" Reyna, David
2014-01-12 17:55 ` Lerner, Dave
2014-01-12 18:49   ` Reyna, David
2014-01-13 12:42     ` Damian, Alexandru
2014-01-13 13:42       ` Damian, Alexandru
2014-01-13 14:33         ` Reyna, David
2014-01-13 14:40           ` Damian, Alexandru
2014-01-13 14:46           ` Damian, Alexandru
2014-01-13 14:53             ` Barros Pena, Belen
2014-01-13 14:57             ` Reyna, David
2014-01-13 15:04               ` Damian, Alexandru
2014-01-13 15:07                 ` Reyna, David
2014-01-15  6:34         ` Reyna, David
2014-01-15 12:09           ` Ravi Chintakunta
2014-01-15 15:19             ` Reyna, David
2014-01-15 17:21               ` Paul Eggleton
2014-01-15 17:21               ` Ravi Chintakunta
2014-01-15 18:01                 ` Barros Pena, Belen
     [not found]           ` <5E53D14CE4667A45B9A06760DE5D13D055D7A5A8@ALA-MBB.corp.ad.wrs.com>
     [not found]             ` <CAJ2CSBvYkLMde7hu0Zhxk7qwBoNdTCTECQv6SxpBXQ1BVx9m1Q@mail.gmail.com>
     [not found]               ` <5E53D14CE4667A45B9A06760DE5D13D055D7B5BE@ALA-MBB.corp.ad.wrs.com>
2014-01-15 15:36                 ` FW: " Reyna, David
2014-01-13 15:01       ` Lerner, Dave
2014-01-13 15:10         ` Damian, Alexandru
2014-01-13 15:23           ` Barros Pena, Belen
2014-01-13 15:44             ` Lerner, Dave
2014-01-13 16:36               ` Barros Pena, Belen [this message]

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=CEF9C44F.3AAC4%belen.barros.pena@intel.com \
    --to=belen.barros.pena@intel.com \
    --cc=dave.lerner@windriver.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.