Candy: Difference between revisions

From OLPC
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Olpcboxtop|toptext=[[{{PAGENAME}}|Candy]]}}
{{Olpcboxtop|toptext=[[{{PAGENAME}}|Candy]]}}
{{ OBX activity ||extra<!--|{{{text}}}--> }}
{{ OBX activity | [[Image:activity-candy.svg|40px]]|extra}}
{{ OBX source dev|activities/candy}}
{{ OBX source dev|activities/candy}}
{{ OBX devtickets|candy-activity}}
{{ OBX devtickets|candy-activity}}
{{ OBX team | [[User:Anthony.taranto|Anthony Taranto]] }}
{{Olpcboxbottom}}
{{Olpcboxbottom}}


Line 10: Line 11:


==News==
==News==

===April 12, 2008===
* Implemented a rough UI and partial framework for fixing lines of code that cause build time exceptions.


===January 29, 2008===
===January 29, 2008===
Line 18: Line 22:
===January 24, 2008===
===January 24, 2008===
* Source is [http://dev.laptop.org/git?p=activities/candy hosted].
* Source is [http://dev.laptop.org/git?p=activities/candy hosted].

==Getting Candy==

===[[git]]===
git clone git://dev.laptop.org/activities/candy


==Editor==
==Editor==

[[Image:Candy_replacement.png|thumb|right|350px|Candy suggesting a possible replacement to fix an IndentionError exception]]


The Candy editor will attempt to provide real time assistance as code is written.
The Candy editor will attempt to provide real time assistance as code is written.
Line 35: Line 46:
* [http://hacketyhack.net/ Hackety Hack]. Excellent collaboration model and code publishing ability.
* [http://hacketyhack.net/ Hackety Hack]. Excellent collaboration model and code publishing ability.
* [http://tryruby.hobix.com/ Try Ruby].
* [http://tryruby.hobix.com/ Try Ruby].
* [http://fishsoup.net/software/reinteract/ Reinteract]
* [http://scratch.mit.edu/ Scratch]
* [http://www.javabat.com/ JavaBat]


==Contact==
==Contact==
Line 41: Line 55:
[[category:software]]
[[category:software]]
[[category:Activities]]
[[category:Activities]]
{{Activity page
|icon=Image:activity-candy.svg
|genre=Programming
|short description=An automated python tutor.
|contact person=User:Anthony.taranto
|activity source=http://dev.laptop.org/git?p=activities/candy
}}

Latest revision as of 16:29, 14 October 2009

Activity-candy.svg
Trac print.png Tickets all - active - new
The Candy Activity

Candy is an automated python tutor.

News

April 12, 2008

  • Implemented a rough UI and partial framework for fixing lines of code that cause build time exceptions.

January 29, 2008

  • New screenshot.
  • Course file format. Groups assignments together.
  • Move to the next assignment in the sequence once current assignment is completed.

January 24, 2008

Getting Candy

git

git clone git://dev.laptop.org/activities/candy

Editor

Candy suggesting a possible replacement to fix an IndentionError exception

The Candy editor will attempt to provide real time assistance as code is written.

Analysis

Assignments will be presented as a set of individual steps that the user must complete. Assignment completion will be based on a flexible system of code analysis. This system is currently implemented using python's abstract syntax tree functionality.

Localization

Eventually, Candy will explore possibilities for localizing the code writing and analysis.

Similar Projects

Contact

anthony.taranto@gmail.com

Activity Summary

Icon: Sugar icon::Image:activity-candy.svg
Genre: Activity genre::Programming
Activity group: ,|x|Activity group::x}}
Short description: Short description::An automated python tutor.
Description:
Maintainers: ,|x|Contact person::x}}
Repository URL: Source code::http://dev.laptop.org/git?p=activities/candy
Available languages: ,|x|Available languages::x}}
Available languages (codes): ,|x|Language code::x}}
Pootle URL:
Related projects: Related projects,|x|Related projects::x}}
Contributors: ,|x|Team member::x}}
URL from which to download the latest .xo bundle Activity bundle::
Last tested version number:
The releases with which this version of the activity has been tested. ,|x|Software release::x}}
Development status:
Ready for testing (development has progressed to the point where testers should try it out): ,|x|Ready for testing::x}}
smoke tested :
test plan available :
test plan executed :
developer response to testing :