[Toaster] Image customisation implementation plan

[Barros Pena, Belen]

Hi Dave!

Good to hear from you :)

I am bit confused by your email. You replied to an email about the image
customisation feature, but your comments seem to be about this document

https://bugzilla.yoctoproject.org/attachment.cgi?id=2504

Which is attached to this Bugzilla entry

https://bugzilla.yoctoproject.org/show_bug.cgi?id=7329

And is about changes to the navigation in projects. I have added some
comments below: I hope they make sense.

On 22/07/2015 15:52, "Lerner, Dave" <dave.lerner at windriver.com> wrote:

>Hi Belen,
>Been off
>til today.  Here are some comments, perhaps already addressed by others.
> 
>On Navigation Refactoring :
>https://www.yoctoproject.org/project-builds.html you left out "toaster/"
>in the
>url.

Well spotted! Will change that.

> 
>Page 4 of 15: 
>"Compatible software recipes" , would it be better to use the "package"
>instead of "software"? That is the terminology that I'm more familiar
>with in the
>wrs distros.

"software recipes" are not packages: they are recipes that do not produce
a rootfs file at the end of the build process (i.e. they are not image
recipes). I gave them a name because they are called simply 'recipes' in
the Yocto Project world, but I am not sure that helps explaining how they
are different to image recipes.

> 
>It is also consistent with "Edit packages".

This is where I get a bit confused. Which "edit packages" are you
referring to?

> 
>Page 5 item 2 and 3
>(2) doesn't point to anything and (3) points to a file name, but is
>described differently.

I am also a bit confused by this. In the document, page 5 provides an
overview of the navigation changes. There are no links to anything in that
page, so when you say "point to anything" and "points to a file name", I
am not sure what exactly you are referring to.

> 
>Page 11
>https://www.yoctoproject.org/project-configuration.html and
>http://www.yoctoproject.org/project-new-
>configuration.html you left out "toaster/" in the
>url.

Ah, yes: will change that.

> 
>Page 12: 
>has two identical screen shots, was one supposed to be the cancelled
>screen?

The screenshots are not identical, although the do look very similar: the
first one shows how the page looks like after you click the "cancel"
button on a build you just started. The second one shows how the page
looks like if you click the 'x' button on the right hand side of the
notification shown in the first screenshot. I do agree this is not very
well explained in the document, though. But you can see what I meant by
visiting

http://www.yoctoproject.org/toaster/project-new-configuration.html

Select 'core-image-base' in the build form in the top right hand corner of
the screen. Then click 'build'. When the "build queued" notification comes
up, click the 'cancel' button, then click the 'x' on the right side of the
'build cancelled' notification.

>http://www.yoctoproject.org/project-new-
>configuration.html missing "toaster/"

Yes: will update that

> 
>Page 13:
>
>When you close (click X) on a notification that has hidden an earlier
>notification, does the close, reveal the hidden notification
> in notification time sequence?

Not really: the notifications are not a stack. They are deleted and
replaced by new ones, so there is only one shown at any given time. If I
click x on a notification, the notification alert disappears from the
screen.

> 
>add "toaster/" to
>url. 

Will do. It looks like I made the same omission across the whole document
:/

> WHen I went to
>url and changed machine added a layer, a drop down notification appeared
>which didn't quite look like the notification but instead looked like.
>Is that what you wanted to show?

Well, if you add a layer that has dependencies, you will see that modal
dialog, which is telling you that the layer you are adding requires other
layers that you should also add to your project. You will see the standard
notification when you click the 'add layers' button in that modal dialog.

Cheers

Belén


> 
>Thanks,
>Dave
> 
>> -----Original Message-----
>> From:
>toaster-bounces at yoctoproject.org
>[mailto:toaster-bounces at yoctoproject.org] On
>> Behalf Of Barros Pena, Belen
>> Sent: Friday, July 17, 2015 11:32 AM
>> To:
>toaster at yoctoproject.org
>> Subject: [Toaster] Image
>customisation implementation plan
>>
>
>> I've been looking into breaking down the image
>customisation feature into
>> small chunks.
>>
>
>> We have currently 2 features in Bugzilla that are needed for this work:
>>
>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7571
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7329
>>
>
>> I have then identified 10 additional features that could be created in 6
>> upstream drops:
>>
>
>> [DROP 1]
>> Feature 1. Changes to the Import layer page
>>
>
>> [DROP 2]
>> Feature 2. Create the Image recipe details page
>>
>
>>
>
>> [DROP 3 - the biggest one]
>> Feature 3. Create the New custom image page
>> Feature 4. Implement creating custom images (involves creating new
>>custom
>> image details page)
>> Feature 5. Implement add / remove packages functionality
>>
>
>> Feature 6. Create the Custom images page
>> Feature 7. Changes to the Basic configuration page
>>
>
>> [DROP 4]
>> Feature 8. Implement building new custom images
>>
>
>> [DROP 5]
>> Feature 9. Implement downloading custom image recipe files
>>
>
>> [DROP 6]
>> Feature 10. Implement deleting custom images
>>
>
>> If you would rather see the feature broken down in a different way, let
>>me
>> know before next Tuesday.
>>
>
>> Thanks!
>>
>
>>
>Belén
>>
>
>> --
>> _______________________________________________
>> toaster mailing list
>>
>toaster at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/toaster
>