628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + − + + − 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 == − ''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.'' − ''This should link to your home wiki page so we know who you are''+ − + − − ''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'' − − + − + − + Line 53:
Line 45: − ''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.''+ Line 64:
Line 56: − − [[Category:Feature Page Incomplete]] − [[Category:Feature]]
Features/Avoid surplus Activity launching (view source)
Revision as of 15:17, 5 November 2013
, 15:17, 5 November 2013no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}
[[Category:Feature Page Incomplete]]
</noinclude>
'''Comments and Explanations:'''
== Summary ==
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.
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 ==
* Name: [[User:ChristophD| Christoph Derndorfer]]
* Name: [[User:AcountName| Your Name]]
* Email: christoph AT olpcnews DOT com
* 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 ==
== Contingency Plan ==
== Contingency Plan ==
Defer to 0.88
== Documentation ==
== Documentation ==
* 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 -->
----
----
''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]]''