98
edits
Changes
Jump to navigation
Jump to search
Line 253:
Line 253: + + + + + + + + Line 278:
Line 286: −
→You and the community
-Me
-Me
I see the benefits as follows:
# '''''A framework to stay ahead of the curve''''' It is important to experiment with and implement newer ways of interacting with Sugar. This framework lays the foundation for not only core Sugar itself, but also it has the potential to expose a new method of interaction for Activities, benefiting the entire Activity developer community.
# '''''Cool demo-ability''''' This can be a very cool demo-able feature, if not anything else. During conferences, trade-shows, etc, it is essential to have ways to grab attention of random (but interested) individuals within a very short period of time. This kind of feature tends to attract attention immediately.
# '''''Potential accessibility support component''''' We (as a community) need to think about Sugar a11y (accessibility) seriously. We have had numerous queries in the past about using Sugar for children with various disabilities. While speech is only a part of the puzzle (and speech recognition is a subset of the entire speech problem - synthesis being the other one), this project lays one of the fundamental cornerstone of a11y support, which in the end, should increase the appeal of Sugar for a significantly large set of use cases. I'm not sure how many "educational software" care about accessibility, but I don't think the number is very large. Sugar will have a distinct competitive advantage if we manage to pull of a11y properly.
[[User:SayaminduDasgupta|SayaminduDasgupta]] 22:28, 29 March 2009 (UTC)
----
----
----
----
===Miscellaneous===
===Miscellaneous===