Changes

===="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 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?”.

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 this wiki page http://wiki.sugarlabs.org/go/Math4Team/RIT/Projects/Question_Support_API#Dependencies] ).

* The API is written in Python, has a set of dependencies ([[which are documented on this wiki page | http://wiki.sugarlabs.org/go/Math4Team/RIT/Projects/Question_Support_API#Dependencies]] ).

* For activity developers to include our API into an activity, we're hoping to have the Sugar development team create a mechanism for developer's to install or include components.  [[User:Enimihil|Greg Stevens]]'s has a bit more knowledge on this than  [[User:bbl5660|Brian]], but we 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 be restricted to their 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 collaborate with 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 create a mechanism for developer's to install or include components.  [[User:Enimihil|Greg Stevens]]'s has a bit more knowledge on this than  [[User:bbl5660|Brian]], but we 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 be restricted to their 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 collaborate with people at Sugar and figure out the best practice to include our API.