[Toaster] [RFC] Image customisation detailed design

[Michael Wood]

Thanks for the video Belén, Looks good.

Couple of bits of feedback

Creating an image recipe:

I find the text in the modal too long, anything more than 2 sentences 
and my attention span is over!

I found it confusing that I entered a name and clicked create but have 
not actually created anything, what about something like suggestion1.png 
(attached) this brings it more into line with import layer/create new 
project/form based activity.

Select a base image recipe:

I was looking for a way to "de/re/select" an image, we don't quite have 
the same concept here as the machines selection that I was expecting, 
where you can always select regardless of whether it's already selected.

Add and delete packages:

'.well' 1

I was expecting the pencil to do the same as other pencils and activate 
text input boxes. Obviously if you're on the Add/Delete packages page 
you can't change the base image like that so maybe not having these 
pencils would be better. I was also unsure as what the change 
version/licence would do.

'.well' 2

If you've selected an image recipe and then remove the layer that 
provides it... what happens?

The Build Image recipe/ Download recipe file / Delete image recipe 
buttons are somewhat easy to miss, they look a bit like progress buttons 
or other tabs. I wonder if they would be better off in '.well' 1. The 
Build button could be more noticeable.

In general if you can avoid having data in a table that for each one 
requires extra data looking up the tables will be much faster/efficient. 
For example we have the dependencies button with total size displayed. 
It should be really quick to count the number of dependences, but much 
slower if we also have to retrieve the objects to get the data in them, 
such as "name" and "size".  If we can do that by making it "on demand" 
that's much better, e.g. you click the button and it fetches this extra 
data.

Thanks,

Michael



On 12/06/15 14:40, Barros Pena, Belen wrote:
> As I mentioned in the Toaster weekly meeting last Wednesday, I've recorded
> a (not so short, sorry) video showing a much more detailed design for the
> image customisation feature. The video is here
>
> https://wiki.yoctoproject.org/wiki/images/a/a1/Image-customisation.webm
>
> Everything that I show in the video is now available in the design
> prototype at
>
> https://yoctoproject.org/toaster
>
>
> Just in case you want to follow along ;)
>
> I think the design addresses pretty much all the feedback the Toaster
> contributors have provided so far (listed below). The only items not
> addressed are 1 (because it would require us to rethink Toaster as a tool
> for absolute beginners and would impose a very specific workflow) and 8
> (because I haven't had time to think about how we can do this, but we can
> definitely come back to it).
>
> Please send any comments and new feedback to the mailing list so that
> Tiago can collect it and we can address it.
>
> This is the feedback we have received so far:
>
> 1. Should this kind of linear process be the main Toaster workflow,
> instead of the non-linear one currently provided by the existing project
> page?
>
> 2. Size is project configuration dependent, so all size information is a
> guess, an approximation. We should probably still show it, but the
> interface needs to present it as such (we need to make sure we don't
> present it as it was 100% accurate information). The same for dependencies.
>
> 3. We need to create states for how the tables will look like when certain
> information is missing (number of packages, sizes, etc)
>
> 4. We need to refine the recipe presentation in the workflow
>
> 5. We need to work on the way we present the actions. Do we really need
> all the ones we have right now?
>
> 6. Replace the builds tab with a less prominent way of accessing build
> information for the custom image recipe.
>
> 7. Provide a way to reenter the image customisation process from the build
> results
>
> 8. Provide a way to 'select all' packages returned by a search
>
> 9. Do we need the reverse dependencies information in the packages table?
>
> 10. Can we add the package size to the visible dependencies information in
> the packages table?
>
> 11. The workflow is still too complex: too many concepts exposed
> (packages, layers, recipes). Should we just require people to build the
> image they want to customise instead?
>
> Cheers
>
> Belén
>
>
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: suggestions1.png
Type: image/png
Size: 146632 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20150623/19fdefbe/attachment-0001.png>