Display the determined uncompressed size on the "too small for image" warning

[jviotti]

We should make sure the user understands why the drive is not large enough, which can be a bit confusing in the case of compressed images, where the compressed package is usually smaller than the drive.

[Shou]

Something like this? Although maybe "image size too big" "actual image size too big" or some such?

[lurch]

Might also be worth having an option to display the exact byte-sizes of both the uncompressed image and the drive in that scenario too, since with the units currently being always-rounded to GB, a "7.5GB" image may not actually fit on a "7.5GB" drive, if the image is even a few kilobytes larger than the drive.

[lurch]

Hmm, looking at @Shou 's screenshot I guess we need to be careful to try and keep the "warning label" small - maybe @konmouz has some ideas?

[Shou]

@lurch yeah, good call. Perhaps "Image Size Bigger By x units" and we just display in the appropriate human readable unit?

[jviotti]

Let's bring @konmouz here.

[konmouz]

2 options:

• we can have a 'insufficient space' label and on hover a tooltip with details (what @lurch suggested)
• avoid the label and have just an the alert/ danger icon with the explanation, all in red - no tooltip

BTW, @Shou why the above element has two labels? System and boot? It would be better to stick to 1 label per drive. Also, boot drives should be greyed out and have a dark grey label.

[jviotti]

I think I like the second option more, given that a tooltip might not be very discoverable unless the user however on the badge. In order to continue the brainstorm session: what about displaying the size that doesn't fit instead? E.g: You need 300 more MBs for the image.

[konmouz]

@jviotti this sounds even better. So using the label font size and the alert icon, we can display such a message. - Or, 300 MBs more are required for the selected image. -

[lurch]

BTW, @Shou why the above element has two labels? System and boot?

It's actually System and Source ;-) But yeah, it probably makes sense to only show one warning-label-per-drive, and I guess in this instance Source is 'more important' than System (a system drive may be writable, but a source drive (where the image is being read from) never will be).

With regards to the "too small" label message, what about "Drive is 300MB smaller than image" ?

[konmouz]

Sounds good to me, we should probably add the word 'selected' though, just to help user understand.

[alexandrosm]

The "source" label doesn't sound like something I'd understand, nevermind my mother. Shouldn't we find a better name for it?

…

-- *Alexandros Marinos* Founder & CEO, Resin.io +1 206-637-5498 @alexandrosm

On Mon, Feb 27, 2017 at 9:35 AM, Konstantinos Mouzakis < ***@***.***> wrote: Sounds good to me, we should probably add the word 'selected' though, just to help user understand. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1136 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLUCEAJF6dY0Sb7TMqWzVbRls4lD-Zkks5rgwlngaJpZM4MMJEA> .

[lurch]

I guess Source was chosen, as it's the logical-opposite of Destination, but you're right that it doesn't make much sense when seen in isolation. Difficult to thing of a more meaningful label though... what about something like "Image source" or "Image location" instead of "Source Drive"?

[jviotti]

I created new issues to track some of the suggestions mentioned here:

• Don't show System Drive and Source Drive badges at the same time #1143
• Improve "Source Drive" drive selector badge wording  #1144