Features/Resource monitoring - Revision history

FGrose at 16:30, 21 February 2011

2011-02-21T16:30:38Z

← Older revision		Revision as of 12:30, 21 February 2011
Line 3:		Line 3:
	[[Category:Feature\|Resource monitoring]]		[[Category:Feature\|Resource monitoring]]
	</noinclude>		</noinclude>
			{{Stub}}
	~~'''Comments and Explanations:'''~~

	There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy\|Feature Policy Page]] for a more detailed explanation of the new-feature process.		There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy\|Feature Policy Page]] for a more detailed explanation of the new-feature process.

Line 12:		Line 10:

	<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->		<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->
	~~{{Stub}}~~
	== Summary ==		== Summary ==
	~~Simulate~~ computer resource learning by providing progressive feedback on system resources.		Stimulate computer resource learning by providing progressive feedback on system resources.

	== Owner ==		== Owner ==

FGrose at 06:09, 21 February 2011

2011-02-21T06:09:40Z

← Older revision		Revision as of 02:09, 21 February 2011
Line 55:		Line 55:
	* The Happy vs <s>Sad</s> metaphor has been replaced with 'Strained'		* The Happy vs <s>Sad</s> metaphor has been replaced with 'Strained'
	[[File:Strained.svg]]		[[File:Strained.svg]]
	*: Other metaphors are possible, see [[{{TALKPAGENAME}}#Inappropriate ~~metaphore~~\|this discussion]].		*: Other metaphors are possible, see [[{{TALKPAGENAME}}#Inappropriate metaphor\|this discussion]].
	== How To Test ==		== How To Test ==
	{{:{{PAGENAME}}/Testing}}		{{:{{PAGENAME}}/Testing}}

FGrose at 05:54, 21 February 2011

2011-02-21T05:54:01Z

← Older revision		Revision as of 01:54, 21 February 2011
Line 38:		Line 38:

	The curious should also have the opportunity to delve more deeply into this computer behavior and see more background information about the state of the computer. Hover panels should reveal some graphic information about the subsystems, and a 'Resource monitor' Activity should be opened if more information is requested by a primary click. This Activity would graphically and textually deliver more layers of information, staged in an instructive progression.		The curious should also have the opportunity to delve more deeply into this computer behavior and see more background information about the state of the computer. Hover panels should reveal some graphic information about the subsystems, and a 'Resource monitor' Activity should be opened if more information is requested by a primary click. This Activity would graphically and textually deliver more layers of information, staged in an instructive progression.
			[[File:Dextrose_resource_monitoring.png\|800px]]<br /all>
			(The sad face has been superseded by a ''strained'' face. See the UI section.)

	A proposal to reveal system memory consumption on the upper Frame bar complements this feature.		A proposal to reveal system memory consumption on the upper Frame bar complements this feature.
Line 43:		Line 45:

	== Benefit to Sugar ==		== Benefit to Sugar ==
	[[File:Dextrose-mascotte-120x96.png]] This feature is considered so important in Paraguay, that they chose the happy computer as their mascot.		[[File:Dextrose-mascotte-120x96.png\|link=Dextrose]] This feature is considered so important in Paraguay, that they chose the happy computer as their mascot.

	== Scope ==		== Scope ==
Line 49:		Line 51:

	==UI Design==		==UI Design==
	Be sure to look at [[{{TALKPAGENAME}}]].		* Be sure to look at [[{{TALKPAGENAME}}]].

			* The Happy vs <s>Sad</s> metaphor has been replaced with 'Strained'
			[[File:Strained.svg]]
			*: Other metaphors are possible, see [[{{TALKPAGENAME}}#Inappropriate metaphore\|this discussion]].
	== How To Test ==		== How To Test ==
	{{:{{PAGENAME}}/Testing}}		{{:{{PAGENAME}}/Testing}}

FGrose at 05:13, 21 February 2011

2011-02-21T05:13:14Z

← Older revision		Revision as of 01:13, 21 February 2011
Line 12:		Line 12:

	<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->		<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->
			{{Stub}}
	== Summary ==		== Summary ==
	Simulate computer resource learning by providing progressive feedback on system resources.		Simulate computer resource learning by providing progressive feedback on system resources.

FGrose at 05:10, 21 February 2011

2011-02-21T05:10:20Z

← Older revision		Revision as of 01:10, 21 February 2011
Line 6:		Line 6:
	'''Comments and Explanations:'''		'''Comments and Explanations:'''

	There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy\|Feature Policy Page]] for a more detailed explanation of the new-feature process. ~~'''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''~~		There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy\|Feature Policy Page]] for a more detailed explanation of the new-feature process.

	<!-- All fields on this form are required to be accepted.		<!-- All fields on this form are required to be accepted.
Line 14:		Line 14:

	== Summary ==		== Summary ==
	~~''A sentence or two summarizing what this feature is and what it will do~~. ~~This information is used for the overall feature summary page for each release.''~~		Simulate computer resource learning by providing progressive feedback on system resources.

	== Owner ==		== Owner ==
Line 31:		Line 31:
	''How does one learn to effectively use a new tool?'' One must use the tool and experiment with it. If your father introduced you to a pocketknife, and it had a dull blade, you would have a bad first impression and not learn too well. My father gave me a knife with a sharp blade and a dull blade, asked me to discover the difference, and proceeded to show me how to sharpen the blade.		''How does one learn to effectively use a new tool?'' One must use the tool and experiment with it. If your father introduced you to a pocketknife, and it had a dull blade, you would have a bad first impression and not learn too well. My father gave me a knife with a sharp blade and a dull blade, asked me to discover the difference, and proceeded to show me how to sharpen the blade.

	People who are new to computers will not know their limitations. They must learn by discovery. Unfortunately, the consequence of some computer requests will not be easily associated with their causes. (Witness all those whose computers crash or lose documents because the user could not see the scores of windows or redundant documents that were open under the full screen.) Some explicit feedback greatly aids in discovery. I remember how quickly I learned ~~effective~~ database ~~querying when~~ the database server was moved a few feet ~~away~~ from me and I could hear the disc drives churning when I submitted a more complex form of a query.		People who are new to computers will not know their limitations. They must learn by discovery. Unfortunately, the consequence of some computer requests will not be easily associated with their causes. (Witness all those whose computers crash or lose documents because the user could not see the scores of windows or redundant documents that were open under the full screen.) Some explicit feedback greatly aids in discovery. I remember how quickly I learned to effectively query a database, after the database server was moved a few feet from me and I could hear the disc drives churning when I submitted a more complex form of a query.

	So with Sugar, which will most often be ~~tried~~ on a computer with limited resources, the new learner is greatly aided by having some signals that report on the status of the tool. The child may see that certain actions have progressive consequences, and may learn how to quickly 'sharpen the blade that has become dull' by overuse.		So with Sugar, which will most often be run on a computer with limited resources, the new learner is greatly aided by having some signals that report on the status of the tool. The child may see that certain actions have progressive consequences, and may learn how to quickly 'sharpen the blade that has become dull' by overuse.

	A progressive scale of computer 'strain' made visible by notable icons would aid in learning with Sugar. The progressive iconic feedback, itself, may be sufficient. Critical or dangerous resource conditions deserve additional alert mechanisms, such as those proposed for the alert system.		A progressive scale of computer 'strain' made visible by notable icons would aid in learning with Sugar. The progressive iconic feedback, itself, may be sufficient. Critical or dangerous resource conditions deserve additional alert mechanisms, such as those proposed for the alert system.

	The curious should also have the opportunity to delve more deeply into this computer behavior and see more background information about the state of the computer. Hover panels should reveal some graphic information about the subsystems, and a 'Resource monitor' Activity should be opened if more information is requested by a primary click. This Activity would graphically and textually deliver more layers of information, staged in an instructive progression.		The curious should also have the opportunity to delve more deeply into this computer behavior and see more background information about the state of the computer. Hover panels should reveal some graphic information about the subsystems, and a 'Resource monitor' Activity should be opened if more information is requested by a primary click. This Activity would graphically and textually deliver more layers of information, staged in an instructive progression.

			A proposal to reveal system memory consumption on the upper Frame bar complements this feature.
			[[Design_Team/Proposals/Home_View/Toolbar\|Home View Framebar]]

	== Benefit to Sugar ==		== Benefit to Sugar ==
	[[File:Dextrose-mascotte-120x96.png]] This feature is considered so important in Paraguay, that they chose the happy computer as their mascot.		[[File:Dextrose-mascotte-120x96.png]] This feature is considered so important in Paraguay, that they chose the happy computer as their mascot.
Line 45:		Line 49:

	==UI Design==		==UI Design==
	~~''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions~~.''		Be sure to look at [[{{TALKPAGENAME}}]].

	== How To Test ==		== How To Test ==
	{{:{{PAGENAME}}/Testing}}		{{:{{PAGENAME}}/Testing}}

FGrose at 04:47, 21 February 2011

2011-02-21T04:47:46Z

← Older revision		Revision as of 00:47, 21 February 2011
Line 29:		Line 29:

	== Detailed Description ==		== Detailed Description ==
	''~~Expand on~~ the ~~summary~~, ~~if appropriate~~. ~~A couple of sentences suffices~~ to ~~explain~~ the ~~goal~~, ~~but the more details you can provide~~ the ~~better~~.''		''How does one learn to effectively use a new tool?'' One must use the tool and experiment with it. If your father introduced you to a pocketknife, and it had a dull blade, you would have a bad first impression and not learn too well. My father gave me a knife with a sharp blade and a dull blade, asked me to discover the difference, and proceeded to show me how to sharpen the blade.

			People who are new to computers will not know their limitations. They must learn by discovery. Unfortunately, the consequence of some computer requests will not be easily associated with their causes. (Witness all those whose computers crash or lose documents because the user could not see the scores of windows or redundant documents that were open under the full screen.) Some explicit feedback greatly aids in discovery. I remember how quickly I learned effective database querying when the database server was moved a few feet away from me and I could hear the disc drives churning when I submitted a more complex form of a query.

			So with Sugar, which will most often be tried on a computer with limited resources, the new learner is greatly aided by having some signals that report on the status of the tool. The child may see that certain actions have progressive consequences, and may learn how to quickly 'sharpen the blade that has become dull' by overuse.

			A progressive scale of computer 'strain' made visible by notable icons would aid in learning with Sugar. The progressive iconic feedback, itself, may be sufficient. Critical or dangerous resource conditions deserve additional alert mechanisms, such as those proposed for the alert system.

			The curious should also have the opportunity to delve more deeply into this computer behavior and see more background information about the state of the computer. Hover panels should reveal some graphic information about the subsystems, and a 'Resource monitor' Activity should be opened if more information is requested by a primary click. This Activity would graphically and textually deliver more layers of information, staged in an instructive progression.
	== Benefit to Sugar ==		== Benefit to Sugar ==
	~~''What~~ is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''		[[File:Dextrose-mascotte-120x96.png]] This feature is considered so important in Paraguay, that they chose the happy computer as their mascot.

	~~''Make sure to note here~~ as ~~well if this feature has been requested by a specific deployment, or if it has emerged from a bug report~~.''

	== Scope ==		== Scope ==

FGrose: Created page with " Category:Feature Page Incomplete Resource monitoring '''Comments and Explanations:''' There are comments (in italic) providing..."

2011-02-21T03:16:40Z

Created page with "<noinclude> Category:Feature Page Incomplete Resource monitoring </noinclude> '''Comments and Explanations:''' There are comments (in italic) providing..."

New page

<noinclude>
[[Category:Feature Page Incomplete]]
[[Category:Feature|Resource monitoring]]
</noinclude>

'''Comments and Explanations:'''

There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes! DO NOT EDIT THIS TEMPLATE.'''





== Summary ==
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''

== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:AcountName| Your Name]]

''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
* Email: <your email address so we can contact you, invite you to meetings, etc.>

== Current status ==
* Targeted release: (SUGAR_VERSION)
* Last updated: (DATE)
* Percentage of completion: XX%

== Detailed Description ==
''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''

== Benefit to Sugar ==
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

==UI Design==
''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''

== How To Test ==
{{:{{PAGENAME}}/Testing}}
== 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 ==
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?''

== Contingency Plan ==
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''

== 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 ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]