Activities/Thumbs View in Journal
Summary
Add thumbs view to Journal.
Owner
- Name: Aleksey Lim
- Email: send an email
Current status
- Targeted release: 0.86
- Last updated: Sat Aug 22 12:37:36 UTC 2009
- Percentage of completion: 75%
Detailed Description
Implement thumbs view mockup.
Benefit to Sugar
In process..
Scope
- shell code
Implementation
- sugar cloned repo
Memory usage with thumbs
Scroll and requery thumbs view during 10 min.
| sugar-session | sugar-presence-service | datastore-service | len(gc.objects()) |
|---|---|---|---|
| 311m 42m | 121m 14m | 113m 12m | 47017 |
| 330m 58m | 121m 14m | 132m 31m | 54184 |
| 330m 58m | 121m 14m | 146m 45m | 55595 |
| 333m 61m | 121m 14m | 160m 59m | 56798 |
| 336m 64m | 121m 14m | 173m 72m | 57619 |
| 335m 63m | 121m 14m | 191m 90m | 58722 |
| 346m 75m | 121m 14m | 204m 103m | 60885 |
| 347m 75m | 121m 14m | 215m 114m | 62155 |
| 349m 77m | 121m 14m | 226m 125m | 63911 |
| 349m 77m | 121m 14m | 243m 142m | 64719 |
| 341m 69m | 121m 14m | 256m 154m | 65227 |
| 344m 72m | 121m 14m | 269m 168m | 66589 |
Memory usage without thumbs
Scroll and requery list view during 5 min.
| sugar-session | sugar-presence-service | datastore-service | len(gc.objects()) |
|---|---|---|---|
| 252m 25m | 33751 | ||
| 315m 44m | 121m 14m | 113m 12m | 50154 |
| 315m 44m | 121m 14m | 114m 13m | 50909 |
| 315m 45m | 121m 14m | 114m 13m | 51530 |
| 315m 45m | 121m 14m | 115m 14m | 53274 |
| 315m 45m | 121m 14m | 115m 14m | 55197 |
| 315m 45m | 121m 14m | 116m 15m | 56177 |
| 316m 47m | 121m 14m | 117m 16m | 59655 |
| 317m 47m | 121m 14m | 117m 16m | 60759 |
| 318m 48m | 121m 14m | 117m 16m | 62797 |
| 320m 50m | 121m 14m | 118m 16m | 64793 |
How To Test
This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
A good "how to test" should answer these four questions:
- What special hardware / data / etc. is needed (if any)?
- How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
- What specific actions do I perform to check that the feature is working like it's supposed to?
- What are the expected results of those actions?
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
Just regular glucose dependencies.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.