Allow long sentences on scan example onboarding page

[jasmeet0817]

[monsieurtanuki]

Hi @jasmeet0817!
I'm not convinced by the use of Flexible, I guess a Column with MainAxisAlignment.spaceBetween would be safer, but anyway you've fixed the bug, so congratulations!

[jasmeet0817]

Hi @jasmeet0817! I'm not convinced by the use of Flexible, I guess a Column with MainAxisAlignment.spaceBetween would be safer, but anyway you've fixed the bug, so congratulations!

depends on your definition of safe :)

You can achieve the column spaceBetween behavior with flex as well, so it's not whether flex is safer or not, but rather the usage of it. I think we are fine now, and flex allows us a lot of device agnoustic layout building capabilities.

[monsieurtanuki]

@jasmeet0817 The problem this PR was about was precisely because of Flexible being not 100% agnostic: you have to set a value.
With spaceBetween you would just say: I want the same space between the items, and the items will be 100% displayed and not at all truncated (unless the items are too big and don't fit on the screen, but that's another story, that Flexible wouldn't have dealt with successfully either).

[jasmeet0817]

@jasmeet0817 The problem this PR was about was precisely because of Flexible being not 100% agnostic: you have to set a value.
With spaceBetween you would just say: I want the same space between the items, and the items will be 100% displayed and not at all truncated (unless the items are too big and don't fit on the screen, but that's another story, that Flexible wouldn't have dealt with successfully either).

Yeah but spaceBetween is going to give an equal spacing between the elements, which we may or may not want depending upon the UX design. Flex has it's uses, of course we still have to ensure is that each element gets enough space to be rendered on all devices without any clipping.