scrolling very slow on ubuntu-touch
Bug #1177945 reported by
Bill Filler
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Friends |
Fix Released
|
High
|
Robert Bruce Park | ||
friends (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
friends-app (Ubuntu) |
Fix Released
|
High
|
Ken VanDine |
Bug Description
friends app 0.90.0bzr13.
on ubuntu-touch image 118 on Galaxy Nexus
Once I configure twitter and run friends-app, the scrolling is really slow and can't keep up with swipe gestures. This should be improved as scrolling through the list should be fast.
Related branches
lp:~robru/friends/avatar-cache
- PS Jenkins bot (community): Approve (continuous-integration)
- Ken VanDine: Approve
-
Diff: 554 lines (+56/-137)15 files modifiedfriends/protocols/facebook.py (+4/-6)
friends/protocols/flickr.py (+4/-7)
friends/protocols/foursquare.py (+1/-3)
friends/protocols/twitter.py (+1/-3)
friends/service/dispatcher.py (+0/-9)
friends/service/mock_service.py (+0/-4)
friends/tests/test_avatars.py (+0/-29)
friends/tests/test_facebook.py (+5/-10)
friends/tests/test_flickr.py (+2/-6)
friends/tests/test_foursquare.py (+3/-4)
friends/tests/test_notify.py (+19/-0)
friends/tests/test_twitter.py (+10/-15)
friends/utils/avatar.py (+4/-24)
friends/utils/notify.py (+3/-1)
service/src/service.vala (+0/-16)
lp:~ken-vandine/friends-app/fix_avatar
- Robert Bruce Park: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 60 lines (+17/-9)3 files modifieddebian/changelog (+13/-0)
debian/control (+3/-2)
qml/StatusUpdateTile.qml (+1/-7)
Changed in friends-app (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in friends: | |
status: | Confirmed → Fix Committed |
Changed in friends-app (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in friends: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've determined this is caused by file access from QML in the avatar cache . It's actually significantly faster using remote URLs for the avatars. Using the remote URLs also means QML will handle local caching of the avatars for us, so we don't need to manage the avatar cache in the backend at all. The only remaining need for a cached version of the avatar is the notify-osd integration, which doesn't support a url to a remote image.
For now we'll drop the avatar caching logic from the friends dispatcher and start storing the URLs in the model. However, the dispatcher will need to cache an avatar long enough for the notification. Perhaps cache in /tmp which will get purged on restart?