Sugar Labs

0.84/Reliability: Difference between revisions

← Older edit
Tomeu (talk | contribs)
647 edits
Godiard (talk | contribs)
628 edits
No edit summary
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>[[Category:FeatureLanded]]
== Datastore rework ==
== Datastore rework ==


Line 36: Line 37:
=== Actions ===
=== Actions ===


* The Sugar clipboard supports multiple clippings at once, which is fantastically useful, assuming you can tell them apart. Right now, you cannot. A primary goal of the next major update to the clipboard is to expose the identities of clippings, including support for activity supplied titles, colors, icons, and previews. The first order goal is to define an API to make this possible.
* Allow activities to supply a title along a clipping. '''(tomeu)'''
* In some cases, clippings won't have titles at all (or activities won't cooperate to supply them).  We need to improve the default behaviors for generating titles, colors, and previews so that the clipboard is still usable.
* Allow activities to supply an icon along a clipping. '''(tomeu)'''
* Display a preview of the clipping in the palette. '''(tomeu)'''
* Display the colors of the activity that provided the clipping. '''(tomeu)'''
* Calculate good fallbacks for activities that fail to provide any of the above items. '''(tomeu)'''
* We really need to support a direct "paste" action on clipping items, which poses an implementation challenge.  It's important, however, to make this action work in our "object oriented" environment.
* We really need to support a direct "paste" action on clipping items, which poses an implementation challenge.  It's important, however, to make this action work in our "object oriented" environment.
* We should have secondary option for paste-and-remove (option-ctrl-v) on the paste button.
* We should have secondary option for paste-and-remove (option-ctrl-v) on the paste button.
* We should have secondary option for copy-and-erase (ctrl-x) on the copy button, to handle the action usually known as "cut".
* We should have secondary option for copy-and-erase (ctrl-x) on the copy button, to handle the action usually known as "cut".
* The clipboard should support drag'n'drop reordering of clippings, both to make a series of paste-and-removes occur in a desired order, and to allow one to move clippings back to the top, so they don't fall off the bottom as more are made.
* The clipboard should support drag'n'drop reordering of clippings, both to make a series of paste-and-removes occur in a desired order, and to allow one to move clippings back to the top, so they don't fall off the bottom as more are made. '''(tomeu)'''


=== Tickets ===
=== Tickets ===
Line 56: Line 60:
*{{Trac|5755|Clipboard should support drag'n'drop reordering (instead of duplicating clippings)}}
*{{Trac|5755|Clipboard should support drag'n'drop reordering (instead of duplicating clippings)}}


=== Status ===
=== Done ===


* Eben is working to refine the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]
* Eben is working to refine the [http://wiki.laptop.org/go/Specifications/Clipboard clipboard specification]
Line 72: Line 76:


=== Actions ===
=== Actions ===
* Improve base memory usage of the sugar shell and related services. '''(tomeu)'''


* Improve base memory usage of the Activity class. '''(marco)'''
* Improve base memory usage of the Activity class. '''(marco)'''
Line 87: Line 89:
* We need some way to constantly monitor memory usage.
* We need some way to constantly monitor memory usage.


=== Status ===
=== Done ===


* Several heavy shell dependency has been dropped.
* Improve base memory usage of the sugar shell and related services. '''(tomeu)'''
* Merge of the journal and of the shell service into the shell is in progress.


== Quality assurance ==
== Quality assurance ==
Line 105: Line 106:
=== Ideas ===
=== Ideas ===


* Get a buildbot running on at least Fedora and Ubuntu.
* Pylint the core codebase, check regressions in the buildbot, make it a requirement to be pylint clean to submit patches.
* Add basic checks on the buildbot about shell and activity startup.
* Integrate sugarbot into sugar-jhbuild and buildbot. Write tests for it and encourage the activity authors to do so too.
* Integrate sugarbot into sugar-jhbuild and buildbot. Write tests for it and encourage the activity authors to do so too.
* Start writing unit tests and use nose to run them into the buildbot. We will have to figure out how to unit test UI code.
* Start writing unit tests and use nose to run them into the buildbot. We will have to figure out how to unit test UI code.
Line 113: Line 111:
* Developers should start using Sugar daily, either on the XO or on a normal laptop.
* Developers should start using Sugar daily, either on the XO or on a normal laptop.


=== Status ===
=== Done ===


* Defined the general goals.
* Get a buildbot running on at least Fedora and Ubuntu. '''(marco)'''
* Work on the buildbot is in progress, but it's already useful.
* Pylint the core codebase, check regressions in the buildbot, make it a requirement to be pylint clean to submit patches. '''(marco)'''
* Zach working on sugarbot integration.
* Add basic checks on the buildbot about shell and activity startup. '''(marco)'''
* sugar shell and module are pylint clean and checked by the buildbot.
Retrieved from "https://wiki.sugarlabs.org/go/0.84/Reliability"