5,705
edits
Changes
Sugar Network/Declaration of purpose (view source)
Revision as of 11:25, 17 January 2012
, 11:25, 17 January 2012no edit summary
## In comparing to (1.5). For sure, educational support exists. But due to very simple Sugar desktop environment functionality, it is too basic, i.e., download {{Code|.xol}} bundle or open the Browse to get access to the content in the network.
## In comparing to (1.5). For sure, educational support exists. But due to very simple Sugar desktop environment functionality, it is too basic, i.e., download {{Code|.xol}} bundle or open the Browse to get access to the content in the network.
# ''What's new in your approach and why do you think it will be successful?''
# ''What's new in your approach and why do you think it will be successful?''
## To solve (2.1) and accomplish (1.1). Sugar Network is not intended to replace all existing (2.1) resources, but rather get singular and unified access point to the same resources from the Sugar Network Browser application that is well integrated to the Sugar desktop environment. It should be friendly to students, i.e., instead of going to [http://bugs.sugarlabs.org bugs.sugarlabs.org], creating an account there, create new ticket with possibility to set bunch of technical fields (like targeting release, OS, etc), a student needs to open Sugar Network Browser, find the targeting activity and type the problem (just the text). Or, to launch Sugar Activity, a student should not browse [[Activity Library]], school server, or Wikis, just click it in Sugar Network Browser.
## To solve (2.2) and accomplish (1.2). On all network accessibility levels (online, school, offline), people use the same Sugar Network Browser (3.1). The only differences are: being online, people see the full picture; being connected to school network, people see the picture that is a snapshot of the full picture (that is being updated from time to time); being offline, e.g., switching from online of from school network, people see only resources they marked as persistent manually.
## To solve (2.3) and accomplish (1.3). Still, it is the same Sugar Network Browser (3.1). On all network accessibility (3.2) levels, people can ask question, share idea, concern about problem, etc. for all accessible resources in their Browser. After increasing network accessibility level, e.g., connecting to the school server after being offline, all new changes will be merged to the new level.
## To solve (2.4) and accomplish (1.4). Still, it is the same Sugar Network Browser (3.1). After clicking the Sugar Activity and getting its fail, the error dialog might show the button "Share the report", then, nothing else from user's point of view. Activity developer will get this repost immediately (depending on network accessibility level). Besides, people can ask questions, share ideas, complain about problems, all this information is accessible for developers.
## To solve (2.5) and accomplish (1.5). Still, it is the same Sugar Network Browser (3.1). This part is the most non-trivial and not technical. But, it should be possible to support different educational related workflows withing the Browser, e.g., during the class time, students migth see only resources that are related to the current subject (when teacher has more powerful view in his Browser).
# ''Who cares?''
# ''Who cares?''
# ''If you're successful, what difference will it make?''
# ''If you're successful, what difference will it make?''