273
edits
Changes
Jump to navigation
Jump to search
Line 52:
Line 52: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 76:
Line 112: + + + + + + + + + + + + + + + + + + + + + + + + Line 90:
Line 150: − ==== JavaScript-Python Communication ==== − JavaScript Python Communication through the following strategies: PyXPCom, hulahop, and xulrunner. Ideally, develop a demo activity which could be used as a template for sugarizing javascript activities. Line 109:
Line 167: − − ==== Titanium Sugar ==== − − * Integrate Titanium-made apps to Sugar. − * Do a titanium activity to develop html/javascript/css appilcations inside Sugar.
Development Team/Project Ideas (view source)
Revision as of 18:56, 8 March 2009
, 18:56, 8 March 2009no edit summary
:I am highly interested in working on this project. Would the project leader mind contacting me at bmw.stx@gmail.com?
:I am highly interested in working on this project. Would the project leader mind contacting me at bmw.stx@gmail.com?
=== Toolkits / Frameworks (for activity developers) ===
=== Toolkits / Frameworks (for activity developers) ===
==== AJAX Sugar ====
* Integrate some style of AJAX applications (for instance, Titanium-made apps) into Sugar. JavaScript Python Communication through the following strategies: PyXPCom, hulahop, and xulrunner.
* Ideally, develop a demo activity which could be used as a template for sugarizing AJAX activities.
*Priority for Sugar: Very High ("never bet against the browser")
*Difficulty (as a GSoC project): hard
*Skills needed: Javascript/Python integration (PyXPCom, hulahop)
==== SWF Sugar ====
* Integrate SWF (Flash/Gnash) applications into Sugar.
* Ideally, develop a demo activity which could be used as a template for sugarizing Flash/Gnash activities.
*Priority for Sugar: Very High ("never bet against the browser")
*Difficulty (as a GSoC project): hard
*Skills needed: SWF/Python integration
==== Improve Develop activity ====
There are several improvements that would make the Develop activity a more attractive IDE. Any ONE of these would be a good GSoC project.
* Make a WYSIWIG GUI editor, like Glade. Note that GTK natively supports loading Glade-format interface definitions, although there would be some work involved making the Sugar interface elements available through this method.
* Integrate Sugarbot and auto-testing facilities.
* Integrate a debugger, based on pdb or other.
*Priority for Sugar: Medium-High
*Difficulty: Medium - Hard
*Skills needed: Good python skills.
=== Stand-alone activities ===
=== Stand-alone activities ===
*Skills needed: C/C++, GTK.
*Skills needed: C/C++, GTK.
==== Educational Toolkit ====
Either based on the existing educational toolkit, or starting from scratch, enable XO use in classroom scenarios. Such scenarios could include
* Teacher shows slides, reproduced on child's screens
* Teacher asks questions - either pre-prepared or on-the-fly
* Students give answers via collaboration
* Teacher or student chooses - explicitly or randomly - an answer for further discussion
* Students split in groups and go from their individual answers to a collaborative answer
* Teacher can review all answers later
* Teacher gives individual or group feedback (offline) which will be shared with appropriate students when they come online
* Teacher checks what's on a child's screen - (experience on other platforms shows this "look over shoulder" ability reduces goofing off even though it is rarely used.)
The low-hanging fruit on [http://wiki.laptop.org/go/Educational_toolkit Educational Toolkit] is the following:
* Enable collaboration scenarios
* Work on the GUI to provide support for multiple types of questions.
* Add API to make it easy to add new question types.
*Priority for Sugar: High
*Difficulty (as a GSoC project): medium-hard
*Skills needed: Probably Python; experience with real-world communications, where message transmission sometimes fails.
== Brainstorm / unexplained ideas ==
== Brainstorm / unexplained ideas ==
==== Graphical toolkit ====
==== Graphical toolkit ====
* WinForm compatibility,
* WinForm compatibility,
* MonoDevelop integration.
* MonoDevelop integration.
=== Activities ===
=== Activities ===