| Line 25: |
Line 25: |
| | *The network backend will be kept as modular as possible to interface with other tools in the future. | | *The network backend will be kept as modular as possible to interface with other tools in the future. |
| | *Question: will this tool be used for actual testing, or less formal evaluation? | | *Question: will this tool be used for actual testing, or less formal evaluation? |
| − |
| |
| − | ==Prototype==
| |
| − | If you are a teacher and want to evaluate my project, please either click
| |
| − | [http://people.rit.edu/acj3840/ForDisplayOnly/PythonPrototype_v0.5.swf here] or look just below to run the prototype. It will launch in the same window, so when you're done hit the back button to get back to this page. Please read the prototype notes as it explains what each screen is for. Once you're done running it, please go [http://wiki.sugarlabs.org/go/Talk:Teacher%27s_Tools here] to discuss it (or once again look below). The latest version is where you would add your input. If you need any help or would just prefer to individually contact me feel free to send me an email at acj3840@rit.edu
| |
| − | Discuss the prototype [http://wiki.sugarlabs.org/go/Talk:Pop_Quiz here]<br \>
| |
| − | For a directory of the old versions look [http://people.rit.edu/acj3840/ForDisplayOnly/ here]
| |
| − |
| |
| − | ===Notes===
| |
| − | A few things about my prototype. The final program will be in Python; the prototype is in flash because I know Actionscript and I'm able to quickly make a prototype with it. It's designed to get across the ideas of possible functionality, not actually be a fully working completely accurate prototype. I've hard coded a lot of stuff which won't be in the actual program. Please evaluate it based on what it implies it would/could do, rather than what it actually does (example: numbers for percentage are wrong, but implies that they would be displayed and displayed correctly). Things to note about it are as follows: <br \>
| |
| − | - The first screen is what the teacher would see, and have the opportunity to input a question, input up to 4 answers, as well as select the correct answer. They would then click on answer to send the question out to the students. <br \>
| |
| − | - The second screen is what the student would see after the teacher submits a question. The teacher's question is displayed as well as a timer and all of the possible answers submitted by the teacher. It currently only supports 4 but I'd like to allow the teacher to determine how many possible choices there are. When the timer runs out, an answer is submitted regardless, otherwise the student can just input an answer and send/submit it. Currently I have the problem of the correct answer still being selected, I cannot figure out how to fix it in flash right now, but that won't be the case in the final version of the activity.<br \>
| |
| − | - The 3rd and 4th screens are both for the teacher. The 3rd screen is the general statistics of the class: Percent that got it correct, the number of students that selected each answer, the average time it took them to answer. The 4th screen is a representation of the class room organized by the name of the XO per student. The teacher can hover over the XO symbol to see the XO's name immediately, and if they continue to hover over it (like in the XO user interface) more information about that particular XO will be displayed such as what answer was selected, and the exact time it took them to answer. <br \>
| |
| − | Please see the related pictured below as well<br \>
| |
| | | | |
| | ==Pictures/Concept Art== | | ==Pictures/Concept Art== |
| | http://people.rit.edu/acj3840/ForDisplayOnly/Class%20Screen.png <br \> | | http://people.rit.edu/acj3840/ForDisplayOnly/Class%20Screen.png <br \> |
| − | ^^This is a concept for the final screen in the prototype. It will have the XO names right below the symbol, and the symbols will be highlighted red or green based on whether or not they answered correctly. Hovering over the XOs for a little bit will then show additional information like the last screen in the prototype. There should be back buttons added to go back to the previous screen as well as a 'ask another question' button and a 'end questioning' button.
| + | This is a concept for the final screen in the prototype. It will have the XO names right below the symbol, and the symbols will be highlighted red or green based on whether or not they answered correctly. Hovering over the XOs for a little bit will then show additional information like the last screen in the prototype. There should be back buttons added to go back to the previous screen as well as a 'ask another question' button and a 'end questioning' button. |
| | | | |
| | <br> | | <br> |
| Line 47: |
Line 34: |
| | http://www.cs.rit.edu/~bml4633/olpc/student_client.png <br \> | | http://www.cs.rit.edu/~bml4633/olpc/student_client.png <br \> |
| | The current interface for students is minimal but functional. | | The current interface for students is minimal but functional. |
| − |
| |
| − | ==Milestones==
| |
| − | <strike> 1) Learn Python/Get GroupMembers
| |
| − | Need
| |
| − | - Know python and have dev environment set up
| |
| − | - Get group members
| |
| − | Date
| |
| − | - To be done by end of RIT's winter break (1/4/2010)
| |
| − | </strike>
| |
| − |
| |
| − | 2) Create Student User Interface
| |
| − | Need
| |
| − | <strike>- Able to accept input from user </strike>
| |
| − | - Transition from screen to screen smoothly
| |
| − | <strike>- Gathers all of the desired information easily </strike>
| |
| − | Date
| |
| − | - Concurrent development with Teacher UI (2/14/10)
| |
| − |
| |
| − | 3) Create Teacher User Interface
| |
| − | Need
| |
| − | - Able to accept input from user
| |
| − | - Transitions from screen to screen smoothly
| |
| − | - Stores all the information in a format easily sent over networks
| |
| − | - Able to display all of the class information regardless of number of students (up to 15)
| |
| − | Date
| |
| − | - Concurrent development with Student UI (2/14/10)
| |
| − |
| |
| − | 4) Get Networking working
| |
| − | Need
| |
| − | - Teacher is able to create and share activity
| |
| − | - Students are able to join activity
| |
| − | - Information is able to be passed from student XO to teacher XO
| |
| − | Date
| |
| − | - To be as done as possible by end of class (Week of 2/14/2010)
| |
| − | 5) Test
| |
| − | Need
| |
| − | - Multiple tests in many different situations
| |
| − | - Feedback from community on usefulness and what else is desired
| |
| − | Date
| |
| − | - As long as there is support for the project
| |
| − | 6) Add features
| |
| − | Need
| |
| − | - Features to be added will determine needs
| |
| − | Date
| |
| − | - Needs will determine dates
| |
| | | | |
| | ==Future goals== | | ==Future goals== |