[Toaster] DRY RUN [Review Request] 4299 "recipes: View detailed information about a recipe"

Barros Pena, Belen belen.barros.pena at intel.com
Mon Jan 13 08:36:22 PST 2014


On 13/01/2014 15:44, "Lerner, Dave" <dave.lerner at 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 at yoctoproject.org
>>[mailto:toaster-bounces at yoctoproject.org] On
>> Behalf Of Barros Pena, Belen
>> Sent: Monday, January 13, 2014 9:24 AM
>> To: Damian, Alexandru; Lerner, Dave
>> Cc: toaster at 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 at 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 at 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 at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/toaster



More information about the toaster mailing list