Features/Introduction Tutorial: Difference between revisions

Line 24:

== 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~~.''

The proposal consists in providing a default interactive tutorial for Sugar that will give an overview of the particularities of the Sugar interface. As discussed with Gerald Ardito, picking up Activities seems to work well for most students. However, getting used to the specific idioms of Sugar requires more efforts.

The proposal aims at giving an overview of the Frame, the different Views, the Journal, Browse and Write in a single tutorial.

The tutorial should be stored in the user home directory, alongside any activity data, as an XML file representing the execution states of the tutorial.

Line 31:

Line 33:

The tutorial should be independent of the screen resolution.

On top of that, the tutorial should be designed to be robust against unscripted actions made by the user. It means that if the user clicks on any button while the tutorial is showing the different elements of the interface, the tutorial should never become out-of-sync with the state of the interface in a way that cannot be resolved by the user. The examples given previously simply rely on the user pressing the next button when she is ready to move on, therefore issues about the exact state of the interface should be avoided.

For the 0.90 release, the tutorial won't be user modifiable other than by modifying the XML format by hand, which won't be recommended.

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

This feature should lower the barrier of entry to Sugar by making it easier to learn the platform by having to resort less to external documentation.

~~''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.''

This tutorial should be accessible from the first login screen, right after the color selection, and from the option menu:

http://tutorius.org/blog/wp-content/uploads/2010/03/login1-300x226.png

http://tutorius.org/blog/wp-content/uploads/2010/03/options-300x225.png

The tutorial will provide an overview of the Desktop, the Group and the Neighborhood Views as well as the Frame, the Journal, the Write and the Browse activity. Here are screenshots of what it might look like for some of them.

http://tutorius.org/blog/wp-content/uploads/2010/03/desktop-300x214.png

http://tutorius.org/blog/wp-content/uploads/2010/03/neighborhood-300x214.png

http://tutorius.org/blog/wp-content/uploads/2010/03/journal-300x216.png

http://tutorius.org/blog/wp-content/uploads/2010/03/write-300x216.png

The information presented to the user will be essentially composed of bubble messages pointing at screen elements. Progress through the tutorial will be accomplished by the user clicking a next button at the bottom of the screen. Once the tutorial is over, the user will be brought back to the Desktop screen where she will be able to resume interacting with the system normally. At any time during the tutorial, the user can press the Stop button to interrupt the current tutorial an return to the original place where she was at first.

== How To Test ==

@@ Line 24: / Line 24: @@
 == 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.''
+The proposal consists in providing a default interactive tutorial for Sugar that will give an overview of the particularities of the Sugar interface. As discussed with Gerald Ardito, picking up Activities seems to work well for most students. However, getting used to the specific idioms of Sugar requires more efforts.
+The proposal aims at giving an overview of the Frame, the different Views, the Journal, Browse and Write in a single tutorial.
 The tutorial should be stored in the user home directory, alongside any activity data, as an XML file representing the execution states of the tutorial.
@@ Line 31: / Line 33: @@
 The tutorial should be independent of the screen resolution.
-On top of that, the tutorial should be designed to be robust against unscripted actions made by the user. It means that if the user clicks on any button while the tutorial is showing the different elements of the interface, the tutorial should never become out-of-sync with the state of the interface in a way that cannot be resolved by the user. The examples given previously simply rely on the user pressing the next button when she is ready to move on, therefore issues about the exact state of the interface should be avoided.
 For the 0.90 release, the tutorial won't be user modifiable other than by modifying the XML format by hand, which won't be recommended.
 == 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?''
+This feature should lower the barrier of entry to Sugar by making it easier to learn the platform by having to resort less to external documentation.
-''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.''
+This tutorial should be accessible from the first login screen, right after the color selection, and from the option menu:
+http://tutorius.org/blog/wp-content/uploads/2010/03/login1-300x226.png
+http://tutorius.org/blog/wp-content/uploads/2010/03/options-300x225.png
+The tutorial will provide an overview of the Desktop, the Group and the Neighborhood  Views as well as the Frame, the Journal, the Write and the Browse activity. Here are screenshots of what it might look like for some of them.
+http://tutorius.org/blog/wp-content/uploads/2010/03/desktop-300x214.png
+http://tutorius.org/blog/wp-content/uploads/2010/03/neighborhood-300x214.png
+http://tutorius.org/blog/wp-content/uploads/2010/03/journal-300x216.png
+http://tutorius.org/blog/wp-content/uploads/2010/03/write-300x216.png
+The information presented to the user will be essentially composed of bubble messages pointing at screen elements. Progress through the tutorial will be accomplished by the user clicking a next button at the bottom of the screen. Once the tutorial is over, the user will be brought back to the Desktop screen where she will be able to resume interacting with the system normally. At any time during the tutorial, the user can press the Stop button to interrupt the current tutorial an return to the original place where she was at first.
 == How To Test ==