Changes

Jump to navigation Jump to search
Obsolete
Line 1: Line 1:  +
{{Obsolete}}
 +
 
{{TOCright}}
 
{{TOCright}}
 
==Question Support API==
 
==Question Support API==
 +
{{:Math4Team/RIT/Projects/Question_Support_API/status}}
 
===Project Information===
 
===Project Information===
 
{{Definition_table
 
{{Definition_table
Line 33: Line 36:  
====Dependencies====
 
====Dependencies====
 
<!-- Development for Linux / Python / Sugar Newbies! -->
 
<!-- Development for Linux / Python / Sugar Newbies! -->
* The following are required by the Question Support API.
+
;The following are required by the Question Support API.
        python-setuptools
+
:python-setuptools
        pyparsing
+
:pyparsing
        peak-rules
+
:peak-rules
        sqlalchemy
+
:sqlalchemy
   −
* You can install these via a linux terminal in this manner:
+
;You can install these via a linux terminal in this manner:
 
         sudo apt-get install python-setuptools
 
         sudo apt-get install python-setuptools
 
         sudo easy_install pyparsing
 
         sudo easy_install pyparsing
 
         sudo easy_install peak-rules
 
         sudo easy_install peak-rules
 
         sudo easy_install sqlalchemy
 
         sudo easy_install sqlalchemy
 +
 +
;Exception: When developing on a Fedora based distro, you'll need to install python-setuptools-devel for easy_install
    
===Motivation===
 
===Motivation===
Line 121: Line 126:  
===="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).
+
* The API is written in Python and has a set of [[#Dependencies|dependencies]], documented above.
* 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]] or [[User:Jfinney|Jameson]], 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.
    
===Education Standards===
 
===Education Standards===
Line 155: Line 160:  
|Fun Towers| No API need or usage.
 
|Fun Towers| No API need or usage.
 
|Reporting Team| Simple export format documented at [[{{PAGENAMEE}}/API_Design|API Design]].  Futher integration work would be nice, but there is more work than could be done in a year along these lines (and neither team is prepared to embark on it).
 
|Reporting Team| Simple export format documented at [[{{PAGENAMEE}}/API_Design|API Design]].  Futher integration work would be nice, but there is more work than could be done in a year along these lines (and neither team is prepared to embark on it).
|Muthris| No contact from? Probably no API need or usage.
+
|Muthris| No API need or usage.
 
}}
 
}}
 +
 
===See Also===
 
===See Also===
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}
 
{{Special:PrefixIndex/{{PAGENAMEE}}/}}

Navigation menu