0.84/Reliability - Revision history

Godiard at 19:23, 5 November 2013

2013-11-05T19:23:13Z

← Older revision		Revision as of 15:23, 5 November 2013
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>[[Category:~~Feature~~]]		<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>[[Category:FeatureLanded]]
	== Datastore rework ==		== Datastore rework ==

FGrose at 06:43, 3 July 2009

2009-07-03T06:43:41Z

← Older revision		Revision as of 02:43, 3 July 2009
Line 1:		Line 1:
			<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>[[Category:Feature]]
	== Datastore rework ==		== Datastore rework ==

FGrose: moved Development Team/0.84/Reliability to 0.84/Reliability: restructure

2009-07-03T06:42:45Z

moved Development Team/0.84/Reliability to 0.84/Reliability: restructure

← Older revision	Revision as of 02:42, 3 July 2009
(No difference)

FGrose: DevelopmentTeam/0.84/Reliability moved to Development Team/0.84/Reliability: deCamel casing

2009-03-17T20:44:56Z

DevelopmentTeam/0.84/Reliability moved to Development Team/0.84/Reliability: deCamel casing

← Older revision	Revision as of 16:44, 17 March 2009
(No difference)

Marcopg: /* Quality assurance */

2008-11-07T18:49:59Z

Quality assurance

← Older revision		Revision as of 14:49, 7 November 2008
Line 105:		Line 105:
	=== 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 115:		Line 112:
	=== Done ===		=== 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~~.

Marcopg: /* Memory bloat */

2008-11-07T18:48:05Z

Memory bloat

← Older revision		Revision as of 14:48, 7 November 2008
Line 75:		Line 75:

	=== 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 92:		Line 90:
	=== Done ===		=== 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~~

	== Quality assurance ==		== Quality assurance ==

Erikos: /* Done */

2008-10-31T15:44:12Z

Done

← Older revision		Revision as of 11:44, 31 October 2008
Line 93:		Line 93:

	* Several heavy shell dependency has been dropped.		* Several heavy shell dependency has been dropped.
	* Merge of the journal and of the shell service into the shell ~~is in progress.~~		* Merge of the journal and of the shell service into the shell

	== Quality assurance ==		== Quality assurance ==

Tomeu: /* Solid clipboard */

2008-10-31T14:58:13Z

Solid clipboard

← Older revision		Revision as of 10:58, 31 October 2008
Line 36:		Line 36:
	=== 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 ===

Erikos at 14:05, 31 October 2008

2008-10-31T14:05:06Z

← Older revision		Revision as of 10:05, 31 October 2008
Line 56:		Line 56:
	*{{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 87:		Line 87:
	* 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.		* Several heavy shell dependency has been dropped.
Line 113:		Line 113:
	* 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.		* Defined the general goals.

Tomeu: /* Datastore rework */

2008-10-31T14:01:38Z

Datastore rework

← Older revision		Revision as of 10:01, 31 October 2008
Line 11:		Line 11:
	=== Actions ===		=== Actions ===

	* ~~The datastore code needs to be rewritten, to simplify and improve maintainability. As a first step the API will not be changed at all (other than removing~~ removable devices ~~support, see next goal), so that the new implementation can be swapped in without changes to activities and Sugar~~. '''(~~tomeu~~)'''		* Design alternative UI for managing removable devices. '''(eben)'''
	* ~~Drop for now the management of~~ removable devices ~~inside the DS. Removable devices support in Sugar should happen without intervention from~~ the DS~~. This will require that Sugar grows some kind of simple file manager that access the file system directly. '''(tomeu)'''~~		* Implement managing removable devices out of the DS. '''(tomeu)'''
	* [http://dev.laptop.org/ticket/8155 #8155] The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND. '''(tomeu)'''
	* When an existing entry is modified, keep the old version and reference them with a version number. Compress versions with deltas. The journal needs to add a possibility to launch different versions of an activity from within the detail view. '''(tomeu)'''		* When an existing entry is modified, keep the old version and reference them with a version number. Compress versions with deltas. The journal needs to add a possibility to launch different versions of an activity from within the detail view. '''(tomeu)'''
	* Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem. '''(tomeu)''' [http://dev.laptop.org/ticket/6269 #6269]
	* Support arbitrary metadata properties that activities wish to add [http://dev.laptop.org/ticket/4662 #4662]. '''(tomeu)'''

	=== ~~Status~~ ===		=== Done ===

	* ~~Tomeu is working on~~ a ~~prototype of~~ the ~~[[DevelopmentTeam/DatastoreRewrite\|datastore rewrite]]~~.		* The datastore code needs to be rewritten, to simplify and improve maintainability. As a first step the API will not be changed at all (other than removing removable devices support), so that the new implementation can be swapped in without changes to activities and Sugar. '''(tomeu)'''
	* ~~If the journal is not going to display~~ the ~~contents~~ of removable devices, we (~~Eben~~) ~~need~~ to ~~design an alternative UI~~.		* Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS. '''(tomeu)'''
	* ~~More work needed to define~~ the ~~goals~~.		* [http://dev.laptop.org/ticket/8155 #8155] The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND. '''(tomeu)'''
			* Support arbitrary metadata properties that activities wish to add [http://dev.laptop.org/ticket/4662 #4662]. '''(tomeu)'''
			* Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem. '''(tomeu)''' [http://dev.laptop.org/ticket/6269 #6269]

	== Solid clipboard ==		== Solid clipboard ==