-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[google_sign_in] Use a transparent image as a placeholder for the GoogleUserCircleAvatar
#4391
Changes from 5 commits
dd83135
4ffd27f
8008688
8048451
75725ef
a54232d
9a9d6d4
b18a8e2
d25857f
316afbf
166822e
03c48da
bf0f524
1d2638a
4d17090
6c69b63
3291d1b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -106,10 +106,59 @@ class GoogleUserCircleAvatar extends StatelessWidget { | |
FadeInImage.memoryNetwork( | ||
// This creates a transparent placeholder image, so that | ||
// [placeholder] shows through. | ||
placeholder: Uint8List((size.round() * size.round())), | ||
placeholder: _transparentImage, | ||
image: sizedPhotoUrl, | ||
) | ||
]), | ||
)); | ||
} | ||
} | ||
|
||
/// This is an transparent 1x1 gif image | ||
final Uint8List _transparentImage = Uint8List.fromList( | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You should check in a script that generates this code and add a comment here pointing to it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm sorry, I'm a bit confused and I don't understand what you want me to do? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Why? Under what circumstance would the bytes of a static image need to be re-generated? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Presumably a script was already written to generate it. Who knows, maybe there is a bug where the pixel is #000000FF but we need #FFFFFFFF, depending on alpha blending that can make a difference. Plus it means people don't need to execute the code to know it is correct. I don't know the gif header format. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alternately, we could compare it byte by byte to the source, which would be significantly less work than reviewing (and then maintaining) a script. @ValentinVignal Can you add a comment with the URL of the source gif you used? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good idea. So let's land the gif (maybe in a new package-level directory with a README explaining why it's there), and reference it in a comment in the code. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hello, I'm sorry again, I'm still not clear on what I should do exactly. Let me try to reformulate and you tell me if I'm wrong? I should:
Did I miss something? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, you just need to add the source GIF to this PR. My suggestion is that it be in a subdirectory (e.g., There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @stuartmorgan @gaaclarke I couldn't remember where I took the image in the first place. In 4d17090, I used this one: from this wikimedia page. I added the image in the repo as I got the bytes by doing: final bytes = await File('resources/transparentImage.gif').readAsBytes(); Is it what you were requesting? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, that sounds good to me, thanks! |
||
[ | ||
71, | ||
73, | ||
70, | ||
56, | ||
57, | ||
97, | ||
1, | ||
0, | ||
1, | ||
0, | ||
128, | ||
0, | ||
0, | ||
255, | ||
255, | ||
255, | ||
0, | ||
0, | ||
0, | ||
33, | ||
249, | ||
4, | ||
1, | ||
0, | ||
0, | ||
0, | ||
0, | ||
44, | ||
0, | ||
0, | ||
0, | ||
0, | ||
1, | ||
0, | ||
1, | ||
0, | ||
0, | ||
2, | ||
2, | ||
68, | ||
1, | ||
0, | ||
59, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nit: data bytes are generally written as fixed-width hex (e.g., There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've changed it in a54232d |
||
], | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: should have a "." at the end of the comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added the "." in 03c48da