Tong Mu

@jpohhhh The transparent pixels are interesting. I’ll greatly appreciate it if you open an issue on Github with a reproduction app!

Started using flutter's superellipse a few days ago. Got a weird bug that's visible at heights ~4K+. After a couple hours "fixing" it and grokking code...TL;DR, I wouldn't use it. c.f. 200 dp height. halfway up on border vertically, you're getting transparent pixels

@jezell @jpohhhh Thank you very much for tagging!

@jpohhhh @DKWmt

@jpohhhh This bug looks like the one fixed by github.com/flutter/flutte…, which has been landed in 3.42. (not on stable yet)

bug at tall heights looks like this (8K height here)

@imadetheseworks The merging shape is amazing!

Time to play with Liquid Glass in your #FlutterDev app! I've pushed a prerelease to pub, check it out here: pub.dev/packages/liqui… It is obviously a first version, so don't expect this to work perfectly, and the API might change a lot still 🥃🥛🥂🍑

@mahersafadii @imadetheseworks @sethladd Yep! Feel free to drop me a DM on X or discord.

@imadetheseworks @sethladd @DKWmt is the team member that worked on implementing it. github.com/flutter/flutte…+

@mahersafadii Slightly correction: It’s not because the PR is massive, but the project is massive. Sometimes changes of small LOC can have massive impact and thus must be discussed thoroughly, for example bumping the minimal version of Android. Similar for this one.

update: the Flutter team responded, nothing negative so far, they asked him for a design doc because the PR is massive, and the mad lad just finished writing a entire design doc docs.google.com/document/d/1Lf…

@jezell @mahersafadii the PR out of agreement instead of tiredness.

@jezell @mahersafadii Splitting into smaller PRs and steps is also for the convenience of reviewing. Writing something new is hard, and reviewing them is even harder, because reviewers are the last guardians of code correctness. It’s important that reviewers really approve (cont.)

@jezell @mickrich384 @mahersafadii We had to write pages of design docs as well. And it’s becaude they really help. I wrote design docs for almost all big projects of mine, and I only regret the cases when I did not write enough - the keyboard was not discussed thoroughly and admittedly it didnt turn out well

@mickrich384 @mahersafadii @DKWmt Props to anyone who can get through the process for significant changes. I don’t like the process, but I can respect anyone who puts in the extra work that core team members usually get to skip.

@luckythehusky 很显然审核代码是比编写代码要更难、更基础、更核心的

想象中的 AI 编程助手: 帮我调试代码. 实际上的 AI 编程助手: 我帮它调试代码.

@RydMike @mahersafadii @luke_pighetti In my algorithm, assume it has equal x radii and y radii, if 2 r_x >= width, then the width sides are circular arcs. The y sides continue to be continuous rounded borders. (Basically the x and y sides are separated/stitched together.) I'm pretty sure this is how Swiftui works.

@mahersafadii @luke_pighetti Also any radius between 0.5x to 1x of stadium border (half of shorter side) will be interesting cases. I have no idea what SwiftUI actually draws for those, but if it is a continous curve, that is not what eg figma_squircle and other in Flutter space does. ⬇️

A RoundedSuperEllipse has landed in #Flutter master #issuecomment-2708417645" target="_blank" rel="nofollow noopener">github.com/flutter/flutte…. Looking forward to adding it to my #FlutterDev Squircle study once there is a ShapeBorder for it that we can use #flutter-squircle-status-march-8-2025" target="_blank" rel="nofollow noopener">github.com/rydmike/squirc… The test app for Squircle study is here rydmike.com/squircle/lates…

@luke_pighetti @mahersafadii @RydMike During my research I indeed used screenshots of SwiftUI's shapes as reference and derived the formula by pixel comparison. The theoretical result is pretty good (see attached). The PR, though, focus on the practical side, i.e. how it runs in real apps and can be used by users :)

@mahersafadii @RydMike i don't like the methodology of comparing two dialogs. someone should do a 256px single corner radius, screenshot, and overlay

@HarrySild @RydMike I’m still unsure where the bottleneck is in the Figma Bezier implementation. But yes performance was probably a reason.

@RydMike Man finally. It only took how many years after one "mysteriously" closed PR that was supposed to add them. 90% sure the undisclosed mystery had to do with performance cost.

@RydMike @HarrySild I did! :)

@HarrySild Thanks 🙏🙂 Not sure anybody reads it, but just in case 🙂

@luckythehusky 台湾的标准不可靠了，他们的规定本来就跟大陆有差别，他们的字典是真的把“和”读作hàn的

@DKWmt 甚至能找到一些台湾的资料, 也是这样规定的. 骑个拔个.

其实这是普通话里面应该有的变调, 现在却成了东北特色, 这也是很神奇,

@ll12142_A 祝贺！！

@DKWmt 是啊，莫名其妙就找到了，虽然是在小镇

居然真的有公司肯为我这种技术力低下社恐口吃的阴湿死宅付钱耶！.jpg 太奇怪了，太奇怪了

@elct9620 @DeltonDing Weekly Review meeting骂的声音其实挺大的，而且我很难想象怎么scale

@DeltonDing 目前是推 Peer Review，然後安排 Weekly 的 Review 活動帶大家看（敏捷的 Temperature Reading） 最近新加入的 Junior 有跟我反應不知道怎麼 Review，所以這樣安排讓成員熟悉要注意的地方，還有團隊偏好的做法

Code Review 机制到后面，很快我就当起了 BDFL (Benevolent Dictator For Life, 终身仁慈独裁者)... 所以怎样才能让项目管理走向共和啊...