-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DON"T REVIEW]TW-459: reduce frames in chat list #466
Conversation
@@ -79,6 +78,8 @@ class ChatListController extends State<ChatList> | |||
|
|||
String? activeSpaceId; | |||
|
|||
final chatListIndexes = <String, int>{}; |
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.
what is it
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.
It's a method for optimizing the number of rebuild of the chat list when the chat list is reordered
Your PR is very very hard for me. Plss help me easy for understand more about your PR |
describe your problem |
ADR + video demo |
@@ -31,224 +28,200 @@ class ChatListViewBody extends StatelessWidget { | |||
final userSearchResult = controller.userSearchResult; | |||
final client = Matrix.of(context).client; | |||
|
|||
return PageTransitionSwitcher( |
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.
Why did you delete it? It's better about performance right?
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.
Why it's better for performance ?. I think currently we don't use the animation, so just remove it for now
Profile mode: run on iphone X
Before refactoring:
RPReplay_Final1692177389.mp4
After refactoring:
RPReplay_Final1692177940.mp4
Conclusion:
The average and max ms/frame before refactoring is lower than after refactoring, so the performance before is better