Features/Avoid surplus Activity launching - Revision history

Godiard at 19:17, 5 November 2013

2013-11-05T19:17:27Z

← Older revision		Revision as of 15:17, 5 November 2013
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}		<noinclude>{{GoogleTrans-en}}{{TOCright}}
	[[Category:Feature Page Incomplete]]		[[Category:Feature Page Incomplete]]
	~~[[Category:Feature\|Avoid surplus Activity launching]]~~</noinclude>		</noinclude>

	== Summary ==		== Summary ==

FGrose at 05:02, 18 October 2009

2009-10-18T05:02:59Z

← Older revision		Revision as of 01:02, 18 October 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}
			[[Category:Feature Page Incomplete]]
			[[Category:Feature\|Avoid surplus Activity launching]]</noinclude>

	== Summary ==		== Summary ==
	Don't let the user keep opening activities until the machine crashes or is		Don't let the user keep opening activities until the machine crashes or is driven to its knees. Make it less likely that a user who is impatient will end up opening multiple copies of an activity.
	> driven to its knees. Make it less likely that a user who is impatient will
	> end up opening multiple copies of an activity.

	At the same time, the user should still be able to create multiple instances if they wish. Part of the idea of empowering users is that they have agency, they can use the software in whatever way they want, including "driving the system to its knees" if that is what they really want		At the same time, the user should still be able to create multiple instances if they wish. Part of the idea of empowering users is that they have agency, they can use the software in whatever way they want, including "driving the system to its knees" if that is what they really want to do.

	== Owner ==		== Owner ==
Line 56:		Line 56:
	* See [[{{TALKPAGENAME}}\|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->		* See [[{{TALKPAGENAME}}\|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->


	~~[[Category:Feature Page Incomplete]]~~
	~~[[Category:Feature]]~~
	----		----
	''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''		''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''

Tonyforster: /* Summary */

2009-07-16T10:04:40Z

Summary

← Older revision		Revision as of 06:04, 16 July 2009
Line 5:		Line 5:
	> driven to its knees. Make it less likely that a user who is impatient will		> driven to its knees. Make it less likely that a user who is impatient will
	> end up opening multiple copies of an activity.		> end up opening multiple copies of an activity.

			At the same time, the user should still be able to create multiple instances if they wish. Part of the idea of empowering users is that they have agency, they can use the software in whatever way they want, including "driving the system to its knees" if that is what they really want

	== Owner ==		== Owner ==

ChristophD at 08:13, 16 July 2009

2009-07-16T08:13:11Z

← Older revision		Revision as of 04:13, 16 July 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

	~~'''Comments and Explanations:'''~~

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

	~~<!-- All fields on this form are required to be accepted.~~
	~~We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->~~

	~~<!-- The actual name of your feature page should look something like: Features/Your Feature Name. This keeps all features in the same namespace -->~~

	== 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.''~~		Don't let the user keep opening activities until the machine crashes or is
			> driven to its knees. Make it less likely that a user who is impatient will
			> end up opening multiple copies of an activity.

	== Owner ==		== Owner ==
	~~''This should link to your home wiki page so we know who you are''~~		* Name: [[User:ChristophD\| Christoph Derndorfer]]
	* Name: [[User:~~AcountName~~\| ~~Your Name~~]]		* Email: christoph AT olpcnews DOT com

	~~''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 ==		== Current status ==
	* Targeted release: ~~(SUGAR_VERSION)~~		* Targeted release: 0.86
	* Last updated: ~~(DATE)~~		* Last updated: 16.07.2009
	* Percentage of completion: XX%		* Percentage of completion: 0%

	== Detailed Description ==		== Detailed Description ==
Line 53:		Line 43:

	== Contingency Plan ==		== 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 you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''~~		Defer to 0.88

	== Documentation ==		== Documentation ==

ChristophD: Created page with '{{GoogleTrans-en}}{{TOCright}} '''Comments and Explanations:''' There are comments (in italic) providing guidance to fill out each section, see also [[Fe…'

2009-07-16T08:08:21Z

Created page with '<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> '''Comments and Explanations:''' There are comments (in italic) providing guidance to fill out each section, see also [[Fe…'

New page

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

'''Comments and Explanations:'''

There are comments (in italic) providing guidance to fill out each section, see also [[Features/Policy]]. '''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 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?''

== 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?''

== 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 ==
''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, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? 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 you 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? 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]] 

[[Category:Feature Page Incomplete]]
[[Category:Feature]]
----
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''