Activities/Thumbs View in Journal

From Sugar Labs
Jump to navigation Jump to search


Summary

Add thumbs view to Journal.

Owner

Current status

  • Targeted release: 0.86
  • Last updated: Sat Aug 29 13:38:41 UTC 2009
  • Percentage of completion: 90%

Detailed Description

Implement thumbs view mockup.

Thumbs.png

Benefit to Sugar

In process..

Scope

  • shell code

Implementation

  • sugar cloned repo
  • sugar cloned repo with non-ds objects added

Memory usage with thumbs for ds and non-ds objects

Scroll and requery thumbs and list view during 5 min.

sugar-session sugar-presence-service datastore-service len(gc.objects())
252m 25m 33761
400m 50m 120m 14m 113m 12m 53423
402m 52m 120m 14m 113m 12m 54939
403m 53m 120m 14m 113m 12m 56071
402m 52m 120m 14m 113m 12m 57104
410m 52m 120m 14m 113m 12m 57991
411m 53m 120m 14m 113m 12m 59458

Memory usage with thumbs for ds objects

Scroll and requery thumbs and list view during 5 min.

sugar-session sugar-presence-service datastore-service len(gc.objects())
252m 25m 33757
319m 47m 120m 14m 113m 12m 53210
319m 47m 120m 14m 113m 12m 54942
319m 47m 120m 14m 113m 12m 56154
319m 48m 120m 14m 113m 12m 58475
320m 48m 120m 14m 113m 12m 62065
321m 49m 120m 14m 113m 12m 63102

Memory usage without thumbs

Scroll and requery list view(from trunk) during 5 min.

sugar-session sugar-presence-service datastore-service len(gc.objects())
251m 24m 33751
314m 44m 121m 14m 114m 13m 51101
315m 44m 121m 14m 115m 14m 53334
315m 45m 121m 14m 116m 15m 56375
315m 45m 121m 14m 116m 15m 59084
318m 48m 121m 14m 117m 16m 63172
320m 50m 121m 14m 118m 17m 67776

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.

Comments and Discussion