71
edits
Changes
Jump to navigation
Jump to search
Line 114:
Line 114: − + − + − +
Math4Team/RIT/Projects/Question Support API (view source)
Revision as of 15:16, 18 May 2009
, 15:16, 18 May 2009→"How to Play/Use" for end user
do_question(q)
do_question(q)
===="How to Play/Use" for end user====
===="How to Play/Use" for end user====
This is a requirement of the RIT OLPC seminar. The question is a bit different for the API team, a more applicable solution would be “How development of the API is done?” and “How do activity developers include / extend our API?”.
This is a requirement of the RIT OLPC seminar. The question doesn't exactly pertain to the API team's project, a more applicable question might be “How development of the API is done?” and “How do activity developers include / extend our API?”.
* The API is written in Python, has a set of dependencies (which are documented on the Question Support API wiki above)
* The API is written in Python, has a set of dependencies (which are documented on this wiki page).
* For activity developers to include our API into an activity, we're hoping to have the Sugar development team include our libraries into Sugar's main packages. [[User:Enimihil|Greg Stevens]]'s has a bit more knowledge on this than [[User:bbl5660|Brian]] , but Brian believes both of us will be looking into how to simply package our API, and how it can be accessed by other Activities. The issue with this later concept, is that Activities running on Sugar's platform is designed specifically to limit each activity to it's own space inside of the Sugar environment. This means that we'll either need to hack something together to make other activities include our API, or we'll need to speak to people at Sugar and figure out the best practice to include our API.
* For activity developers to include our API into an activity, we're hoping to have the Sugar development team include our libraries into Sugar's main packages. [[User:Enimihil|Greg Stevens]]'s has a bit more knowledge on this than [[User:bbl5660|Brian]] , but Brian believes both of us will be looking into how to package our API, and how it can be accessed by other Activities. The issue with this later concept, is that Activities running on Sugar's platform are intentionally meant to limit each activity to it's own space inside of the Sugar environment. This means that we'll either need to hack something together to make other activities include our API, or we'll need to speak to people at Sugar and figure out the best practice to include our API.
===Education Standards===
===Education Standards===