Difference between revisions of "Sugar Labs DC/Online Activity Sharing and Publishing"
m (Removed several unnecessary links.) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 7: | Line 7: | ||
[[Image:Physics_Activity_Menu.png|400px|thumb|Example of the "Publish" option appearing in the Activity Palette]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease. | [[Image:Physics_Activity_Menu.png|400px|thumb|Example of the "Publish" option appearing in the Activity Palette]] In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease. | ||
| − | Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to | + | Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to Scratch's would only work to expand and support the project as a whole. |
Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share. | Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an [http://docs.google.com/View?id=dgv2st82_193cmmv8xgw IRC chat] with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share. | ||
| − | Sugar needs a website comparable to | + | Sugar needs a website comparable to Scratch's with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than Scratch's, as Scratch's website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.). |
Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online. | Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online. | ||
| Line 17: | Line 17: | ||
The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content. | The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content. | ||
| − | Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage) | + | Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage). They could find their uploads as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom with a web interface that would be deeply intertwined with Sugar and all of its activities, which would connect an entire generation and unite them in the spirit of learning. |
| − | |||
Latest revision as of 17:34, 28 July 2009
The Next Wave of Activity Sharing
Sugar Labs DC is interested in bringing the best elements of the Scratch interface to Sugar.
Scratch is a programming and animation suite directed at younger children that teaches the basics of programming with a friendly, colorful interface. One of the most important features of this software is its "Share" utility, which allows the user to upload their project to the Scratch website for all to see and comment on, promoting shared learning and communication. When the Scratch file is received on the website, it is then recompiled into a Java applet and is thus usable from the browser.
In addition to the above features, users are then able to take their exploration one step further: by downloading the files for themselves. This allows them to read each other's code and remix each other's projects. This website/client relationship is really the foremost element of the Scratch project, as it provides the users with an integrated, positive environment in which they can share and present. Further, its accessibility over the web allows for what could easily become trans-national, or even global communication, crossing geographical and linguistic barriers with ease.
Sugar Labs DC seeks to implement this kind of technology by embedding it in the Sugar interface. Many of Sugar's most prominent activities lend themselves toward sharing and collaboration between children. As such, giving them an integrated collaboration system comparable to Scratch's would only work to expand and support the project as a whole.
Since Sugar 0.84, the user has been asked directly at the end of each session to name and describe each activity they've opened, in order to better organize and save their explorations in the Journal. In an IRC chat with several developers, it was suggested that the "Name this entry" dialogue box be put to a higher use in setting metadata for works that would be published online, making it even easier for kids to share.
Sugar needs a website comparable to Scratch's with which to host Sugar users' projects. This would be the fastest, most reliable method of connecting users and promoting collaboration. The scope of the OLPC web resource would need to be much greater than Scratch's, as Scratch's website only needs to accept and display Scratch files (.sb's). The Sugar site would be able to accept Sugar media of all sorts: "Write" activities, "Paint" drawings, "Physics" projects, and presumably games as well. These different types of media would first be categorized by filetype and then hopefully indexed by content or topic (Music, History, Science, etc.).
Further, user interaction would have to be both manageable as well as open. For example, students would be able to join Class groups, based on their actual schools and classes. They would thus be able to receive updates about the activities of their group members and collaborate easily as a class. This would be a sort of "Priority" grouping, as the entirety of the user's activities would not be limited to sharing with just their class, except in the case of configurable Privacy concerns. In addition to this, users would be able to create groups, invite users, and engage in much of the collaborative networking currently available online.
The homepage of this website could show featured projects of various types, as well as category links, which would lead to content based on filetype (documents, pictures, etc.) or content, as described above. This content would be searchable, in order to connect the most users to the most relevant content.
Ideally, the user would be able to upload files from their main menu, open the Browse activity, and navigate to the Sugar page (which could, in theory, become their homepage). They could find their uploads as well as those of thousands of other users, from all over the world. Students would be able to learn beyond their own classroom with a web interface that would be deeply intertwined with Sugar and all of its activities, which would connect an entire generation and unite them in the spirit of learning.